castomAPI

Step 1: ask your Salesforce admin to install the castomAPI package in your org. Step 2: click Connect below.

You'll be asked to choose a HubSpot account and approve permissions. Optional permissions can be declined — endpoints needing them will answer 403.

You'll be asked to grant scopes across Sheets, Docs, Drive, Slides, Calendar and Gmail sending (send-only -- it cannot read your mailbox). Google's granular consent lets you decline any of them -- endpoints needing a declined scope will answer 403.

Covers sign-in, your profile, reading and sending Outlook mail, full calendar access, and reading and writing your OneDrive files. If you connected before file support was added, reconnect to grant the new permissions -- existing connections may keep their old, narrower access until you do.

This grants access to the files and folders in your Dropbox. File listing, upload, download and sharing endpoints arrive in a later update -- for now the connection covers your account profile only.

This grants access to your monday.com boards, workspaces, updates and docs. Board and item endpoints arrive in a later update -- for now the connection covers your profile and account details only.

This grants access to your Typeform forms, responses, workspaces, themes and webhooks. Response and form-editing endpoints arrive in a later update -- for now the connection covers listing your forms and reading your account details.

Netlify issues a single, full-account authorization -- it has no per-permission choices. Its consent screen mentions only your projects, but the access token also covers your team's environment variables, billing payment methods and audit log. castomAPI does not expose endpoints for any of those. Listing your sites is available now; further endpoints arrive in a later update. You can disconnect at any time, and castomAPI will ask Netlify to revoke the token when you do.

This connects your personal LinkedIn member account -- it covers your own profile and posting as yourself: publishing posts with an image, video or document, editing them, and deleting them. LinkedIn does not let this application READ your posts back, so there is no feed or post-history endpoint, and there will not be one on this connection. It also does NOT cover your Company Pages: LinkedIn keeps organization access on a separate application, and castomAPI's request for it is still under review, so Company Page posting, comments, reactions and analytics are not available yet. The connection refreshes itself for about a year, after which you will be asked to reconnect. You can disconnect at any time, and castomAPI will ask LinkedIn to revoke the token when you do.

Connect using your own X Developer App credentials (API Key, API Secret, Access Token, and Access Token Secret). Using your own credentials keeps rate limits and write costs ($0.15/post on X's Pay-Per-Use model) on your own developer console, while castomAPI bills standard tokens per request.

The permissions are fixed on the castomAPI application itself, not chosen at connect time — Calendly's authorization page takes no permission list, and it is a single Approve or Cancel rather than a set of checkboxes. Connecting grants read access to your user profile, event types, scheduled events, availability, locations, routing forms, contacts, organization and webhook subscriptions. It also grants write access: castomAPI can create event types on your account — including single-use "one-off" types — cancel your scheduled events, mark or unmark an invitee as a no-show, and create both customised and uncustomised single-use scheduling links from your existing event types. Nothing else on your account can be changed. Calendly's own screen does not mention the webhook permission, so it is listed here. Event types created this way cannot be deleted through Calendly's API once made — only deactivated. You can disconnect at any time, and castomAPI will ask Calendly to revoke the token when you do — which it really does.

Connecting grants read and write access to your Cal.com user profile, event types, availability schedules, bookings, attendees, and connected calendars. castomAPI can create, cancel, reschedule, confirm, or decline bookings, mark attendance or no-shows, create private single-use booking links, and manage your event types and schedules. Disconnecting removes the account from castomAPI immediately.

Select your Zoho datacenter region (default EU) and click Connect.

Enter your store address and castomAPI will send you to that store's own approval screen, where WordPress asks you to sign in and approve the connection. The key is then delivered straight from your store to castomAPI — it never passes through your clipboard or ours. You need to be an administrator (or shop manager) on the store, and the store needs pretty permalinks turned on: with permalinks set to "Plain", WooCommerce cannot authenticate an API key at all. You can disconnect here at any time, but WooCommerce provides no way for an app to revoke its own key, so to remove it fully go to WooCommerce → Settings → Advanced → REST API and press Revoke.

Connect your Etsy seller account via OAuth 2.0 to access shop listings, inventory management, order receipts, and shipping profiles.

Connect your eBay account via OAuth 2.0 to access Sell APIs (inventory management, order fulfillment, shipping tracking, payment policies, and transaction finances).

Connect your Allegro seller account via OAuth 2.0 to access REST APIs (profile & me proof, offers & listings lifecycle, marketplace categories, order fulfillment & tracking, and billing queries).

Enter your store address and the 32-character Webservice key created in your PrestaShop back office (Advanced Parameters → Webservice). The key is held AES-256-GCM encrypted and verified against the store before saving.

Enter your store address plus dedicated administrator credentials (create a dedicated admin user in store admin with API access — never the owner account).

Enter your store address (e.g. https://client1234.idosell.com) and the Admin API key (X-API-KEY) created in the IdoSell merchant panel.

Enter your BigCommerce store hash (e.g. abc12345) and the store-level API account access token created in the BigCommerce control panel (Settings → API accounts).

Enter your Magento store base URL (e.g. https://shop.example.com) and the Integration Access Token or Admin Access Token generated in Magento Admin (System → Integrations).

Enter your Wix Site ID (or instance UUID) and API key (or OAuth access token) generated in the Wix Developers Center.

Enter your InPost Organization ID and API Bearer Token from the InPost ShipX manager panel.

Enter your DPD Master FID (Customer ID), API login, and password from your DPD contract.

Connect your Furgonetka.pl account via OAuth 2.0 to access multi-carrier shipping services, rate calculation, and parcel tracking across all supported carriers.

Obtain your API key from the DHL Developer Portal. Keys are encrypted at rest with AES-256-GCM.

Enter your EasyPost API Key (Production or Test key from easypost.com/account/api-keys). Keys are encrypted at rest with AES-256-GCM.

Enter your Sendcloud Public Key (API Key) and Secret Key (API Secret) from your Sendcloud Settings > Integrations panel. Credentials are encrypted at rest with AES-256-GCM.

Enter your e-Nadawca WebAPI login and password from your Poczta Polska business agreement. Credentials are encrypted at rest with AES-256-GCM.

Select your provider and enter your API credentials. Secrets are stored encrypted with AES-256-GCM.

Store your payment processor keys securely with AES-256-GCM encryption. Use the test generator below to verify checkout links.

Enter your Fakturownia account subdomain ({subdomain}.fakturownia.pl) and API Token from Account Settings > Integration > API.

Enter your company Tax Identification Number (NIP) and KSeF Authorization Token. Test challenge negotiation and live session initialization without risking production state.