Sandbox Accounts
This directory provides guidance for obtaining sandbox accounts for integrations supported by Unified.to. These accounts can be used for testing your app with live data.
Note: These sandbox accounts are different from Unified.to's synthetic data sandbox environment. While our sandbox environment generates synthetic data for trying out he Unified API, these sandbox accounts are for testing with real integration endpoints in production.
| Integration | Self-Serve | Notes |
|---|---|---|
| 15Five (link) | No | No public sandbox or free trial is documented; an Account Admin of an existing 15Five account enables the Public API under Settings > Integrations and creates a key.
|
| 1Password (Events) (link) | No | Access to Events API requires a business account; create test accounts via trials. |
| 1upHealth (link) | No | Create a client with the Unified redirect URI in the 1up Dev Portal, then email payer-patient-access@1up.health to have it synced to the demo environment. Connect with the demo health plan authorize URL https://auth.1uphealthdemo.com/oauth2/authorize/test and the synthetic test member listed at https://docs.1up.health/docs/patient-access/dev-implementation. |
| 24SevenOffice (link) | No | Enable the Developer Admin Panel on your 24SevenOffice account, register an OAuth2 application, connect it to your organization, and use the client credentials plus Organization ID with the client-credentials token endpoint documented at rest-api.developer.24sevenoffice.com. |
| 2Chat (link) | Yes | Create a 2Chat account and generate an API key from the Developer Portal. |
| 360Learning (link) | No | API credentials (Client ID and Client Secret) are created by a platform owner or admin from the 360Learning platform. |
| 3CX (link) | Yes | Self-hosted PBX. Deploy 3CX (free/trial edition) and create an API Service Principal under Integrations > API to obtain client credentials. |
| 3CX (CRM / call journaling) (link) | Yes | Self-hosted or hosted 3CX PRO (or higher). Upload the Unified CRM XML template. No Configuration API / Enterprise license is required for this journaling integration. |
| 46elks (link) | Yes | Sign up for a 46elks account; the API username and password are shown in the dashboard. New accounts include trial credit. |
| 6sense (link) | No | API access requires a 6sense account with Enrichment API credits. API tokens are generated in the 6sense Platform under Settings > API Token management. |
| 7shifts (link) | Yes | Any 7shifts customer can create an admin Access Token (Company Settings → Developers). Partner OAuth apps require approval from 7shifts. |
| 7Targets (link) | No | API credentials (client ID and client secret) are issued by 7Targets support on request: support@7targets.com. |
| a3ERP (link) | No | a3ERP is licensed, self-hosted software (no public multi-tenant sandbox). A real a3ERP v14+ instance with the JNCAPI dictionary and A3APIRest.exe service installed is required for testing; contact Wolters Kluwer / an a3ERP reseller for a licensed test instance. |
| Ableteams (contact for access) | No | Contact support@ableteams.com to get API access and credentials, plus access to the test environment. |
| Abowire (link) | No | Abowire API access requires a subscription management account and API credentials from the Abowire dashboard. |
| Absorb (link) | No | Absorb Integration API access (private key) is a paid add-on and typically provisioned by the Absorb account team. |
| Accelo (link) | Yes | Start a free Accelo trial, then register an API application under Configuration → API → Register Application. |
| Access PaySuite (link) | No | Contact sales@accesspaysuite.com for playpen (sandbox) credentials and API keys. |
| Accounting Seed (link) | No | Accounting Seed runs as a managed package on Salesforce. Use a Salesforce Developer Edition or sandbox org with Financial Suite installed. There is no standalone Accounting Seed REST host. |
| AccountsIQ (link) | No | No open sandbox. API access requires an AccountsIQ account with an Integrations Application; the linked developer is invited to the Developer Portal to obtain Client ID/Secret. Contact integration@accountsiq.com. |
| AccuLynx (link) | No | AccuLynx API keys require an active AccuLynx account with administrator access to create keys. |
| AccuQuote AgentCloud (contact for access) | No | AccuQuote issues separate credentials for its Training and QA environments on request. |
| Accurate (link) | Yes | Sign up at the Accurate Developer Portal to get sandbox Client ID and Client Secret immediately. Production credentials are issued when the account goes live. |
| Acerta (link) | No | APIs available via request; contact Acerta to obtain a test environment and credentials. |
| Achievers (link) | No | Achievers provides a per-program UAT environment (https://<program>.uat.achievers.com). There is no public self-serve sandbox: a program administrator must issue client_id / client_secret with the API OAuth Keys tool in the Client Admin Panel. |
| Act-On (link) | Yes | Request a free developer/sandbox account via the Act-On developer portal, then generate API credentials in the account settings.
|
| Act! (link) | Yes | Sign up for a free Act! Premium trial to obtain a Web API URL, database, user name and password. The Act! Premium Web API is included with Act! Premium; native webhooks require a self-hosted install. |
| Actionstep (link) | No | Actionstep support provisions a sandbox (staging) environment and API credentials on request. |
| ActiveCampaign (link) | No | Sign up for a developer sandbox, |
| ActiveTrail (link) | No | Sign up for an ActiveTrail account and create an API access token under Settings → API apps. The public API reference supports live calls against your production account data. |
| ActivTrak (link) | No | API keys are created by an ActivTrak administrator in the app under API & Integrations > API Keys. No sandbox is documented.
|
| Acumatica (link) | No | Acumatica is instance-hosted. Provision an Acumatica ERP instance (or use a partner/developer instance), register a Connected Application under System > Integration > Connected Applications to get OAuth client credentials (the client id has the form {guid}@{tenant}), and authorize with an ERP user to test the contract-based REST API. |
| Adalo (link) | Yes | Sign up for a free Adalo account, create an app and copy its API key from Settings > App Access. |
| AdaptlyPost (link) | Yes | Sign up at adaptlypost.com and create an API token in the dashboard. Connect at least one social account in the dashboard before listing or updating posts. |
| AddEvent (link) | No | No sandbox or free trial is documented; sign up for AddEvent on a Small Business or higher plan, then copy the API key from the dashboard account settings.
|
| Adfin (link) | No | Email support@adfin.com with subject "Request for API credentials" to obtain OAuth client id/secret and staging access. Register the Unified.to OAuth redirect URI with Adfin when provisioning credentials. |
| Adform (link) | No | Adform must enable External API access and register an OAuth client (technical@adform.com). There is no public self-serve sandbox; use a provisioned agency account. |
| Admina by Money Forward (link) | No | Ask Money Forward for an Admina trial organization, then create an API key in Settings → API Keys. |
| Administrate (link) | No | The Administrate developer portal (developer.getadministrate.com/signup) is free to join and runs example queries against sample data. Calls against real data need an Administrate tenant, arranged with Administrate. |
| Adobe Commerce (Magento) (link) | Yes | Self-hosted: install Adobe Commerce / Magento Open Source (or use a demo instance), then create an integration under Admin → System → Extensions → Integrations with Catalog access and use its Access Token as a Bearer credential. |
| Adobe Experience Platform (link) | No | Requires an Adobe Experience Platform organization with a sandbox. Create an OAuth Server-to-Server credential in the Adobe Developer Console and add the Experience Platform API to obtain Client ID / Client Secret. |
| Adobe Sign (link) | Yes | Create a free Acrobat Sign developer account via Adobe Developer; region-specific endpoints (na1, eu1, etc.). |
| Adobe Workfront (link) | No | Workfront Sandbox/Preview environments are available to existing Workfront customers for API testing. |
| ADP Workforce Now (link) | No | |
| AdRoll (link) | Yes | Register a developer application at developers.nextroll.com. Create a separate app for testing with its own OAuth redirect URI. Default quota is 100 requests per service per day. |
| AdvancedMD (link) | No | Register a SMART on FHIR app on the AdvancedMD FHIR developer portal with the Unified redirect URI and request test patient credentials. |
| Adyen (link) | Yes | |
| Aero Workflow (link) | Yes | Start a free Aero Workflow trial, then use the account id and API key described on the Aero API page. |
| AeroLeads (link) | Yes | Sign up at aeroleads.com and copy your API key from Settings → API. Each successful API call consumes credits per your plan. |
| Aetna (link) | No | Register on the Aetna developer portal, create an application with Application Environment "Sandbox" and complete the questionnaire (Aetna reviews it in 2 to 4 business days), then subscribe the app to the sandbox-patientaccessapi-fhir products. Sandbox FHIR base: https://vteapif1.aetna.com/fhirdemo/v2/patientaccess (OAuth: https://vteapif1.aetna.com/fhirdemo/v1/fhirserver_auth/oauth2). Test members are listed in the sandbox API swagger in the API Library. |
| Affinity (link) | No | Affinity documents no sandbox. Use a paid Affinity account, then create an API key under Settings > Manage Apps > + New App > API Key (Admins, or users with the "Generate an API key" permission).
|
| Affirm (link) | Yes | Create an Affirm merchant sandbox account and use the sandbox public and private API keys with the Sandbox API URL. |
| Afterpay (link) | No | Sandbox merchant credentials are issued by Afterpay; use them with the Sandbox API URL. |
| AgencyZoom (link) | Yes | Start a 14-day free trial of AgencyZoom, then call POST /v1/api/auth/login with that account's username and password to get a JWT bearer token for the API.
|
| Agendrix (link) | Yes | Create an application at developers.agendrix.com. Sandbox does not require app approval. Use sandbox.agendrix.net OAuth hosts and api.sandbox.agendrix.net. Production apps must be approved. Plus plan is required for API access. |
| Agile CRM (link) | Yes | Sign up for an Agile CRM account, then copy your REST API key from Admin Settings → API & Analytics. Use your account email, API key, and subdomain to connect. |
| Agility CMS (link) | Yes | Create a free Agility CMS instance, then copy the instance GUID and the Fetch or Preview API key from Settings → API Keys. |
| Agora.io (link) | Yes | Create an Agora account, enable Conversational AI on a project, and copy the REST Customer ID, Customer Secret, and App ID from the Agora Console. |
| Aha! (link) | Yes | Start a free trial Aha! account and create a PAT for testing. |
| AhaSend (link) | Yes | Create a free AhaSend account. Messages sent with the API option `sandbox: true` are not delivered. |
| AI/ML API (link) | Yes | Sign up at aimlapi.com, create an API key in the dashboard, and call the OpenAI-compatible /v1 endpoints. |
| AI21 Studio (link) | Yes | Sign in to AI21 Studio, create a workspace API key, and call the Jamba chat completions API at https://api.ai21.com/studio/v1/chat/completions. |
| Aidbox (link) | Yes | Sign up on the Aidbox User Portal for a free development license and run Aidbox with Docker Compose. Then create a Client with grant_types [basic] and an AccessPolicy linked to it. |
| AimFox (link) | Yes | AimFox is self-serve; API keys are created in Workspace Settings → Integrations with no separate developer approval step. |
| Aimtell (link) | No | API access requires an Aimtell account; the API key is passed via the `X-Authorization-Api-Key` header. |
| Airship (link) | No | API access requires an Airship project; the App Key and Master Secret are in the dashboard under Settings → APIs & Integrations. |
| airSlate (link) | Yes | Sign up for the airSlate DevHub dashboard, add an application to get a client ID and client secret, and select the code grant. |
| Airtable (link) | Yes | Create a free workspace/base for testing; personal access tokens available for dev. |
| Airwallex (link) | No | |
| Akeneo (link) | No | Must be a partner |
| AlayaCare (link) | No | No public sandbox. API access must be part of the agency’s AlayaCare contract; a System Administrator then creates API keys under Settings > External Integrations > API Key Manager, optionally on the agency’s UAT or staging environment. |
| Alegra (link) | Yes | Sign up for a free Alegra account and generate an API token under Settings → API to test against your own company data. |
| Aleph Alpha (link) | No | PhariaInference access is provisioned through PhariaOS (self-hosted or Aleph Alpha cloud). Create an API token on a service account before connecting. |
| Alex (link) | Yes | Sign up for an Alex account and generate an API Key from the dashboard. The key is passed via the `X-API-Key` header. |
| Alibaba Cloud Model Studio (link) | Yes | Sign up for Alibaba Cloud Model Studio and create an API key in the Bailian console to call the OpenAI-compatible Qwen API. |
| Alibaba.com (link) | Yes | Register as a developer on the Alibaba.com Open Platform, create an application to obtain an App Key and App Secret, then guide a Global Golden Supplier seller through the OAuth authorization to obtain an access token. |
| Alipay (link) | Yes | Use the Alipay Open Platform sandbox: select the Sandbox API URL, then enter the sandbox App ID, application private key, and Alipay public key from the sandbox console. |
| Allegro (link) | Yes | Register a free sandbox account at allegro.pl.allegrosandbox.pl, then register an OAuth app at apps.developer.allegro.pl.allegrosandbox.pl to obtain client credentials. Two-factor authentication is not required in the sandbox. |
| Aloha (link) | Yes | Sign up at the NCR Voyix Developer Experience portal, use Test Drive to provision a sandbox organization, then generate a Shared Key / Secret Key pair. Staging API host is https://gateway-staging.ncrcloud.com (override connection API URL). HMAC AccessKey auth is required in production. |
| Altoviz (link) | Yes | Create a free Altoviz account for development (https://developer.altoviz.com/docs/api/guides/create-account), then generate an API key under Settings → API access. |
| Amazon Bedrock (link) | Yes | Create an AWS account, enable model access in the Amazon Bedrock console for the Region you want, then generate a long-term Bedrock API key under API keys. Keys are Region-scoped. |
| Amazon Bedrock AgentCore (link) | Yes | Create an AWS account, create an AgentCore Memory resource with at least one long-term memory strategy in a supported Region, and create an IAM user or role with the bedrock-agentcore Memory permissions listed in the connection instructions. |
| Amazon Connect (link) | Yes | Create an AWS account, deploy an Amazon Connect instance in your chosen Region, and create an IAM user or role with Connect read permissions for SearchContacts, DescribeContact, and ListUsers. |
| Amazon Pay (link) | Yes | Create a Seller Central account, enable Amazon Pay, and generate Sandbox API keys in Integration Central. Use the Sandbox API URL with SANDBOX- public key IDs. |
| Amazon Seller Central (link) | No | |
| Amazon Vendor Central (link) | No | Register a private vendor application in Vendor Central (Integration > API Integration), complete the SP-API developer profile, and self-authorize to obtain LWA refresh tokens. Sandbox endpoints are documented in the SP-API sandbox guide. |
| Amperity (link) | No | Requires an Amperity tenant. Create a DataGrid Operator API key under Settings > Security, then use "Get OAuth credentials" to obtain the Client ID / Client Secret for the client-credentials flow. |
| Amplitude (link) | Yes | Sign up for a free Amplitude account (no credit card required) and create a project; its API Key and Secret Key are used for API access.
|
| Anrok (link) | No | Every Anrok seller account has access to a sandbox account that works like production (https://apidocs.anrok.com/tutorials). Email support@anrok.com for a new sandbox, then create an API key in it. |
| Anthropic Claude Agents (link) | Yes | API keys are self-serve from the Anthropic Console. Managed Agents is in beta; an agent and an environment must be created once before any session can run. |
| Anvil (link) | Yes | Sign up for a free Anvil account and generate an API key. Test-mode packets (isTest) are watermarked, use red signatures, and are exempt from quota. |
| AnyDB (link) | Yes | Sign up at app.anydb.com and create an API key under Profile → Integration. |
| Apaleo (link) | No | Apaleo offers a free trial account; use the same OAuth client to authorize Swagger or your app against the trial property. API host is api.apaleo.com for production and trial. |
| APIpie AI (link) | Yes | Sign up at APIpie.ai, create an API key in the dashboard, and call the OpenAI-compatible /v1 endpoints. |
| Apple Ads (link) | No | Requires an Apple Ads account with API access. Generate an EC P-256 key, upload the public key in Ads Account Settings > API, then connect with Client ID, Team ID, Key ID, and the private key. |
| Apple App Store Connect (link) | No | Requires an Apple Developer Program membership with App Store Connect access. An Account Holder or Admin creates a team API key (Issuer ID, Key ID, .p8 private key) under Users and Access > Integrations. |
| Apple Search Ads (link) | Yes | Create an API user in Apple Ads Account Settings, generate an EC P-256 key pair, upload the public key, and use the issued Client ID / Team ID / Key ID with the private key. |
| Appointo (link) | No | Appointo API access requires a paid plan; generate an API token under Plans & Settings → API access. |
| ApptiveGrid (link) | Yes | Sign up for ApptiveGrid and create API access credentials from the developer portal. |
| Aquila CMS (link) | No | Aquila CMS is self-hosted. Use your store origin as the API URL (no path). Official API docs: https://www.aquila-cms.com/api-docs |
| Arcoro (link) | No | Arcoro BDAPI access is not self-serve: contact Arcoro to have an API Key issued and to authorize an API user (username/password). The API method reference is published at https://api.birddoghr.com/help. |
| Asana (link) | No | Developer sandbox available through their request form.
|
| Ascora (link) | No | Ascora API access is enabled per account under Administration → API Settings. Contact Ascora support for a trial or sandbox account if you do not already have one. |
| AssessFirst (link) | No | No sandbox is documented. An AssessFirst Administrator with a Recruiter licence generates the API token in the Recruiter space under Integrations > AssessFirst API > Activate > Generate token.
|
| Asterisk (link) | Yes | Asterisk is self-hosted: install it yourself (FreePBX distribution, package manager or from source), then enable the HTTP server in http.conf and define an ARI user in ari.conf. |
| Asymbl (link) | No | Asymbl is a managed package on Salesforce; testing requires a Salesforce org (or sandbox) with the Asymbl ATS (Recruiter Suite) package installed and an Asymbl ATS permission set assigned to the connecting user. |
| Async Interview (link) | Yes | Sign up at asyncinterview.io, then create an API token in account settings to call the documented /api endpoints. |
| athenahealth (link) | Yes | Create an app on the athenahealth Developer Portal for Preview credentials. For FHIR R4, set the workspace API URL to https://api.preview.platform.athenahealth.com/fhir/r4. For athenaOne REST (departments, providers, booked appointments), use Preview API hosts with your practice ID. |
| Atlassian Jira (link) | No | Requires Jira Premium or Enterprise, Jira Service Management Premium or Enterprise, Confluence Premium or Enterprise. To create a sandbox, you must have organization admin permissions. |
| Atlassian Jira Data Center / Server (link) | No | Jira Data Center / Server is customer-hosted. Use a licensed test instance or Atlassian-provided trial media; create a PAT (8.14+) or use basic auth for older Server versions during manual testing. |
| Attio (link) | No | Need a developer account |
| Augure (link) | Yes | Sign up for Augure, open the developer dashboard, add a payment method, and generate an API key for the OpenAI-compatible API at https://api.augureai.ca/v1.
|
| Auth0 (link) | Yes | Sign up for a free Auth0 account to get a developer tenant (e.g. your-tenant.us.auth0.com). |
| Automata (link) | Yes | Market Intelligence API keys are issued at https://apis.byautomata.io. There is no webhook or updated-since filter in the API. |
| Aviato (link) | No | Aviato Data API keys are created in the dashboard (Teams → API Keys). Access is sales-gated. There is no native webhook subscribe API; search endpoints do not document an updated-since filter. |
| Avionté (contact for access) | No | Avionté provides developer credentials (API Key, OAuth Client ID/Secret, and Tenant code) on request to approved partners. |
| Avoma (link) | Yes | Start a free 14-day Avoma trial (Organization plan, no credit card), then as an org admin go to Settings > Organization > Developer and click Add API Key to create a scoped key.
|
| AWeber (link) | Yes | Create a developer app and use test accounts for OAuth flows. |
| awork (link) | Yes | Sign up for a free awork trial workspace and create an API key or an API client under Settings → Integrations. |
| AWS HealthLake (link) | Yes | With any AWS account, create a SigV4-authorized HealthLake FHIR R4 data store in the HealthLake console (optionally preloaded with Synthea sample data), then create an IAM user or role with HealthLake permissions on it and an access key. |
| AWS Lambda MicroVMs (link) | Yes | Create an AWS account, build a MicroVM image in a Region where Lambda MicroVMs is available, and create an IAM user or role with the lambda MicroVM permissions listed in the connection instructions. |
| Axonaut (link) | Yes | Sign up for an Axonaut trial account and generate an API key under Paramètres → API to test against your own company data. |
| Ayrshare (link) | Yes | Sign up at ayrshare.com for a free trial. API keys are issued from the dashboard under API Key. Link social accounts in the Social Accounts page before posting. |
| Azupay (link) | No | Submit a "Request access to UAT" ticket through the Azupay Help Centre service desk; once onboarded, generate keys in the dashboard under Settings > API Keys.
|
| Azure DevOps (link) | Yes | Free tier available with Azure DevOps Services. |
| Azure Health Data Services (link) | Yes | With any Azure subscription, create a Health Data Services workspace and a FHIR service (R4), register a Microsoft Entra application with a client secret, and assign it the FHIR Data Contributor role on the FHIR service. |
| Azure Virtual Machines (link) | Yes | Free Azure account includes limited VM credits for testing. |
| Bagisto (link) | Yes | Bagisto is self-hosted: install Bagisto 2.4 and the bagisto/bagisto-api package (composer require bagisto/bagisto-api, then php artisan bagisto-api-platform:install), then generate an Admin API Integration token under Settings → Integration. |
| Baidu AI Cloud (link) | Yes | Sign up for Baidu AI Cloud, activate the Qianfan (ModelBuilder) service, and create an API Key in the Qianfan console to call the OpenAI-compatible ERNIE API. |
| BambooHR (link) | No | Sandbox and Developer Portal access provided upon marketplace partner program acceptance.
|
| Banner (link) | No | Ethos API keys are issued by the institution (or Ellucian) in the Ethos Integration Hub. There is no public self-serve sandbox; a Banner/Ethos tenant is required. |
| Banqup (link) | Yes | Register on Banqup One and create an app on the Banqup Developer Portal to get a client ID (API key) and client secret. |
| Baremetrics (link) | Yes | In Baremetrics Settings → API Keys, create a Sandbox API key and connect with the Sandbox API URL (https://api-sandbox.baremetrics.com). The sandbox is for testing the Read/Write API without affecting live metrics. |
| Basecamp (link) | Yes | Register an OAuth app at launchpad.37signals.com/integrations (redirect URI required). Basecamp offers trials; API access uses OAuth 2 or personal access tokens with the same Bearer authorization flow. |
| BaseLinker (link) | Yes | Sign up for a BaseLinker account and generate an API token under Account & other → My account → API. API access is included with the subscription. |
| Baserow (link) | Yes | Free cloud account at baserow.io; self-hosted installs use a custom API URL on the connection. |
| Baseten (link) | Yes | Sign up for a Baseten account and create an API key to call the management API. |
| Basis Technologies (link) | No | Basis provides a sandbox at https://api-sandbox.basis.net/v1. Credentials are issued by a Basis representative; they are not self-serve. |
| Bazaarvoice (link) | No | Requires a Bazaarvoice Enterprise account. Contact Bazaarvoice Support to receive a passkey for the staging (stg.api.bazaarvoice.com) or production Conversations API. |
| Beamery (link) | No | Sandbox US is https://frontier.sandbox.beamery.com/v1. OAuth clients and the API user role are provisioned by Beamery Support / CSM. |
| Beds24 (link) | No | Beds24 has no sandbox or test environment ("There is no sandbox so test carefully before going live"); API V2 access is available on every Beds24 account. |
| Beehiiv (link) | Yes | Sign up for a beehiiv workspace, then create an API key under Workspace Settings → API. OAuth2 apps are available for integrations that need user consent. |
| Beeline (link) | No | API credentials (Client ID, Client Secret, Client Site ID) are provisioned by the Beeline Integrations team; there is no self-service developer signup. |
| Bentral (link) | No | Bentral documents no sandbox. API access needs a Bentral user account; contact Bentral to use the API on behalf of an existing user. |
| Berke Assessment (link) | No | The Berke API must be enabled per account by the HighMatch Customer Success Team (https://www.highmatch.com/support). API tokens are then managed under Settings | API:Security. A "Developer Mode" is available for rapid testing. |
| Better Contact (link) | Yes | Create a Better Contact account and generate an API key from the dashboard. Enrichment and profile lookups consume credits per the pricing shown in the API docs. |
| Better Proposals (link) | Yes | Sign up for a Better Proposals account and generate an API token under Settings; the same token is used against the production API host. |
| bexio (link) | Yes | Sign up for a bexio trial account (https://www.bexio.com), then log in to the developer portal (https://developer.bexio.com) and create an app with an allowed redirect URL to obtain a client id and secret. |
| Big Cartel (link) | Yes | Create a free Big Cartel store to test against. OAuth2 public-app credentials (client id/secret) must be requested from Big Cartel; single-store personal projects can also use HTTP Basic auth with the store subdomain. |
| BigCommerce (link) | Yes | Free trial allows for sandbox |
| BigMailer (link) | Yes | BigMailer offers a free trial. Create an API key in the console and use a brand ID from brand settings for API calls. |
| Bika.ai (link) | Yes | Free Bika.ai account; create an API token from user settings for OpenAPI access. |
| Bill4Time (link) | No | Bill4Time offers a trial account. API keys are created in the product under Settings → API. |
| Billberry (link) | No | Register an account at dev.billberry.ee and email hello@billberry.ee to get test organizations attached to the account. |
| Billit (link) | No | Email support@billit.eu to request OAuth2 sandbox Client ID/Secret; sandbox environment is my.sandbox.billit.be / api.sandbox.billit.be. |
| Billomat (link) | Yes | Self-serve: sign up for a free Billomat trial, then activate API access under Settings → Employees to generate a personal API key. The account subdomain (mycompany.billomat.net) is the Billomat ID passed alongside the key. |
| Billsby (link) | Yes | Create a Billsby account, then generate an API key under Settings > Configuration > API keys and webhooks. |
| Bing Webmaster Tools (link) | Yes | Sign up free with a Microsoft, Google, or Facebook account, add and verify a site, then create an API key or OAuth client under Settings → API Access. |
| Bird (link) | Yes | Self-serve signup with an emailed sign-in code (dashboard, or `bird auth signup` in the CLI), then create a workspace API key under Platform tools > API keys and enable an SMS destination country to send test messages. |
| Bitwarden (link) | Yes | Create a free Bitwarden organization (Teams/Enterprise trial) and retrieve the organization API key (Client ID / Client Secret) from Settings > Organization info > View API Key. The Public API uses OAuth2 client credentials with the api.organization scope. |
| Blackbaud Raiser's Edge NXT (link) | Yes | A free SKY Developer account includes access to a Raiser's Edge NXT sandbox environment and a subscription key. |
| Blackboard Learn (link) | No | Register a REST application on the Blackboard/Anthology Developer Portal. A Blackboard Learn instance (or the free developer test instance) is required, and an administrator must register and entitle the application. |
| Bland AI (link) | Yes | Sign up for a Bland AI account at app.bland.ai and create an API key in the dashboard. |
| Blink Payment (link) | Yes | Request a sandbox account at blinkpayment.co.uk/developer-signup, then enable the API on a Blink page to get sandbox API credentials. |
| Blogger (link) | Yes | Any Google account can create a Blogger blog for free; register a Google OAuth app and enable the Blogger API in Google Cloud Console. |
| Blooio (link) | Yes | Sign up at blooio.com, create an API key in the dashboard, and use the v4 API against https://api.blooio.com/v4. |
| Bloomreach (link) | No | Bloomreach Discovery accounts (account_id, auth_key, domain_key) are provisioned by a Bloomreach representative during onboarding. |
| Bloomreach Discovery (link) | No | Bloomreach Discovery accounts (account_id, auth_key, domain_key) are provisioned by a Bloomreach representative during onboarding. |
| Bloomreach Engagement (Exponea) (link) | No | Create a Private API group (API Key ID + Secret) in a Bloomreach Engagement project and use its Project Token. |
| BlueConic (link) | No | Register an OAuth application (Client Credentials) in a BlueConic tenant under Settings > Access management > Applications. |
| Blueink (link) | Yes | Blueink API trial accounts can test the API at no cost and without a time limit, but are limited to sending Bundles in test mode (is_test). |
| Blueshift (link) | No | Blueshift API access requires a Blueshift account; User API keys are created in the Blueshift dashboard. |
| Bokio (link) | Yes | Register a public integration in the Bokio developer portal, then authorize against a Bokio testing company. OAuth uses https://api.bokio.se/v1/authorize and https://api.bokio.se/v1/token with HTTP Basic auth (client_id:client_secret) on the token exchange. |
| bol.com (link) | Yes | bol.com provides a demo environment (base path /retailer-demo) that returns static demo data for exploring the Retailer API. Production API access requires a bol.com seller account and API client credentials generated in the seller portal. |
| BoldSign (link) | Yes | Sign up for a free BoldSign trial and generate an API key under Settings → API. OAuth apps are registered in the same API settings. |
| Boleto Cloud (link) | Yes | Create a free Boleto Cloud sandbox account to get a sandbox API Key. The sandbox is a separate environment from production. |
| BoloForms (link) | Yes | Create a BoloForms account and generate an API key from Settings → API Key to call the Signature API. |
| BookStack (link) | Yes | BookStack is self-hosted; install an instance (or use a hosted provider), then create an API token under your profile. |
| Boomerangme (link) | No | No sandbox is documented. Copy the API key from the Integrations tab under Settings in a Boomerangme account.
|
| BoondManager (link) | No | |
| Booqable (link) | Yes | Sign up for a Booqable trial account to obtain a company subdomain and create an API access token from account settings. |
| Botdog (link) | Yes | Botdog offers a 7-day free trial. API and webhook access require Professional+ and may need beta access — request access via Settings → Integrations. |
| Botify (link) | No | Botify has no self-serve trial. Request a demo from Botify to get access to a project and an API token. |
| BounceWatch (link) | Yes | Create a BounceWatch account and generate an API key in the API Panel. Enriching a domain spends credits; a domain enriched within the last 24 hours is returned free. Store an https webhook URL in the API Panel so new enrichments can be queued. |
| Box (link) | No | Currently, a Box enterprise admin or enterprise co-admin can create or delete a developer sandbox through the Admin Console. |
| Braze (link) | No | API access requires a Braze account; REST API keys are created in the dashboard under Settings > APIs and Identifiers. |
| BreatheHR (link) | Yes | Free account signup provides sandbox-specific API key. |
| Breeze (link) | Yes | Sign up for a Breeze account and copy the API token from your profile settings. |
| Brevo (link) | Yes | Create a Brevo account, then generate an API key under SMTP & API → API keys. |
| Brex (contact for access) | No | Sandbox is only available to select customers. If you'd like Early Access features, please reach out ot your Brex representation for more information. |
| Bridge (link) | Yes | Free self-serve sandbox. Create an account at https://dashboard.bridgeapi.io/signup to get a sandbox Client ID and Client Secret, create a user via POST /v3/aggregation/users to obtain a User UUID, then use Bridge Connect (or the sandbox banks) to link accounts. Production access is requested from the Bridge dashboard. |
| Brightflag (link) | No | Brightflag API credentials are issued by Brightflag Support; use the regional developer portal to explore the external OpenAPI. |
| BrightMove (link) | No | BrightMove issues Company and User API keys to existing customers/partners; contact your BrightMove account manager for API access. |
| BroadWorks XSI (link) | No | BroadWorks XSI access is provisioned by your service provider or Cisco partner. Obtain an XSP hostname and a BroadWorks user with XSI-Actions permissions (Enhanced Call Logs may require an additional service assignment). |
| Browserbase (link) | Yes | Browserbase API keys are created from the project settings page. |
| BTCPay Server (link) | Yes | Run BTCPay Server locally or use the public testnet demo instance for Greenfield API development. |
| Bubble (link) | Yes | Sign up for a free Bubble account, create an app and enable the Data API under Settings → API. |
| Buckaroo (link) | Yes | Buckaroo provides a test gateway at https://testcheckout.buckaroo.nl using a test website configured in Buckaroo Plaza; choose the Test API URL on the connection. |
| BuddyPT (link) | No | API access is listed only on the Enterprise plan, so contact BuddyPT sales to request it; the free Starter plan has no listed API access.
|
| Buffer (link) | Yes | Sign up for a Buffer account, then create an API key or OAuth app under Settings → API. |
| Buk (link) | No | API access uses a tenant API Key from Configuración → Acceso API. Official Swagger is served at https://{tenant}.buk.{tld}/apidocs. A public demo contract is at https://demo.buk.cl/apidocs. |
| Bukku (link) | No | Email dev@bukku.my to request a test account on the staging server (API at https://api.staging.bukku.dev) with your login email, staging URL and a 3 or 6 month duration. |
| BulkGate (link) | Yes | Register a BulkGate portal account, then create an API application under Modules & APIs to get the application ID and token. |
| BulkPublish (link) | Yes | BulkPublish offers a free plan with API access. Connect channels in the dashboard, then create an API key under Settings → Developer. |
| BulkSMS (link) | Yes | Register a BulkSMS account (free trial credits are included), then create an API token under Settings → Developer Settings → API Tokens. |
| Bullhorn (contact for access) | No | Contact your Bullhorn account representative to start the sandbox account creation process. |
| busybusy (link) | No | busybusy does not document a public sandbox; testing needs a busybusy organization and an API key issued by busybusy. |
| Buttondown (link) | Yes | Sign up for a Buttondown newsletter, then copy the API key from Settings → Programming → API. |
| Buy Me a Coffee (link) | Yes | Buy Me a Coffee exposes a REST API to creators. Create an account and generate a personal access token in the developer settings. |
| BytePlus ModelArk (link) | Yes | Sign up for BytePlus, enable ModelArk, and create an API key in the console to call the OpenAI-compatible Chat Completions, Embeddings, and Models APIs and the Managed Agents memory stores API. |
| Callingly (link) | Yes | Sign up for a Callingly account and create an API key under Settings → API Keys. Agency partners can pass account_id on API requests for client accounts. |
| CallPage (link) | No | Sign up for CallPage and create an API token in the dashboard to call the REST API. |
| CallRail (link) | No | A CallRail account with an API key (Account ▸ Settings ▸ Integrations ▸ API Keys) is required. API keys are scoped to the creating user. |
| CallTools (link) | No | A CallTools customer account is required to issue an API key. Contact CallTools developer support if you need a developer account without an existing customer. |
| CallTrackingMetrics (link) | Yes | Enable API access under Account Settings → Data & API Integration to obtain an Access Key and Secret Key. Agency keys can access sub-accounts via GET /accounts.json. |
| Cambio (link) | No | Sign up on the COS developer portal and subscribe to the Cambio Open Services product. After Cambio approves the subscription you get a client ID and secret by email, and the subscription key is in your portal profile. The sandbox has five synthetic test patients (see https://developer.openservices.cambio.se/test-data). |
| Campaign Monitor (link) | Yes | Sign up for a free Campaign Monitor account to obtain an API key; OAuth2 apps are registered via the developer documentation. |
| Campayn (link) | Yes | Campayn offers a free tier (500 contacts / 20,000 emails per month). Sign up and generate an API key from account settings. |
| Campfire (link) | No | Campfire is an AI-native ERP; API tokens are created by customers in the app under Settings → Developer. There is no public self-serve sandbox. |
| Canarics (link) | Yes | Sign up for a Canarics account, then have a team manager create a read-only API key in the dashboard Team tab. |
| Candis (link) | No | Candis has no public sandbox signup. A Candis organization is required; generate a Client ID and Client Secret under Settings → Candis API → Credentials (a redirect URL is required). |
| canhelpto (link) | Yes | Create a canhelpto workspace and copy its Service key from the dashboard settings. |
| Canny (link) | Yes | Sign up for a Canny workspace at canny.io; API keys are available under Settings → API on paid plans. |
| Canvas Medical (link) | No | Canvas provisions a development instance with OAuth client credentials; use the instance subdomain as the connection instance name and request tokens from https://{instance}.canvasmedical.com/auth/token/. |
| Captivated (link) | No | Captivated documents no sandbox; use a Captivated account and create an API key under My Profile → Password and Credentials. |
| Captorra (link) | No | Lead-posting API for intake; credentials are provisioned per Captorra client organization.
|
| Careem (link) | No | Careem issues POS API client credentials to onboarded partners. Use the staging gateway for integration testing. |
| Carerix (link) | No | Carerix documents no sandbox; API access requires an existing Carerix application where an administrator creates a confidential client under Identity Access > Clients.
|
| Carta (link) | No | Register on the Carta developer portal, create a playground app, and add the OAuth callback URL for your Unified workspace. |
| Cartesia (link) | Yes | Sign up at play.cartesia.ai and create an API key. Agents are created from the Cartesia CLI or playground. |
| CASEpeer (link) | No | CASEpeer has no self-serve sandbox. API client credentials are issued by CASEpeer support, who also activate the application. |
| Cashfree Payments (link) | Yes | Sign up for a Cashfree merchant account and switch the dashboard to Test mode to get sandbox Payment Gateway API keys. |
| Caspio (link) | Yes | Start a free Caspio trial, then create a Web Services API profile (Account > Web Services API) to obtain a Client ID and Client Secret. |
| Cdiscount (link) | No | Octopia provides API credentials (Client ID / Client Secret) after contract signature; the seller must also declare itself as an API user in the Cdiscount back-office to obtain the Seller ID. |
| Cegid Loop (link) | No | API keys (Standard, free) are generated by an accounting-firm administrator on the CegidLife portal; a subscription key is provided by your Cegid representative. |
| Cegid Retail (link) | No | Cegid Retail Y2 API access requires a Cegid customer/partner tenant: a dedicated Y2 service user (username/password), the tenant Service URL hosting the WCF services, and the target Database ID. Provisioned by Cegid; there is no self-service developer sandbox. |
| Cegid Revo Retail (link) | No | API access is granted after requesting it via the Revo API Request Form (https://api.revo.works/). Revo validates the request and provides integration/sandbox access and account tokens. |
| Cegid Revo Xef (link) | No | API access is granted after requesting it via the Revo API Request Form (https://api.revo.works/). Revo validates the request and provides integration/sandbox access, account tokens, and the integrator client-token. |
| Ceipal (link) | No | Ceipal provides API access (email, API password, and API Key) to existing customers via the ATS Admin Panel; a developer/sandbox account is arranged with Ceipal. |
| Centene (link) | No | Register on the Centene Partner Portal (https://partners.centene.com), create a project and request a subscription to the "FHIR - Patient Access" API; once Centene approves it, generate the sandbox client ID and secret. Choose the Sandbox region when connecting; the "Getting Started" guide on the API page lists the sandbox test members to sign in with. |
| Centerbase (link) | No | Centerbase API credentials are issued per firm; contact Centerbase for developer access to a sandbox tenant. |
| Cerebras (link) | Yes | Sign up at cloud.cerebras.ai, create an API key in the Cloud Console, and call the OpenAI-compatible /v1 endpoints. |
| Ceridian Dayforce (link) | No | |
| Certn (link) | No | |
| CertSeal (link) | Yes | Sign up for CertSeal and create a workspace API key under Settings → API keys. |
| Cezanne HR (link) | No | Cezanne HR API access is enabled per customer tenant by generating a Client ID and Secret in Administration > Security Settings > Authorised Applications. |
| Channex (link) | Yes | Channex offers a self-serve staging environment at staging.channex.io where you can register an account and generate an API key. |
| Chargebee (link) | Yes | Free trial allows for sandbox |
| Chargefy (link) | Yes | Create a Chargefy account and a ch_test_ API key from Settings → Chaves de API. Sandbox API: https://sandbox-api.chargefy.io |
| CharmHealth (link) | No | Request a CharmHealth Certified API developer account (client ID and secret) via the API Access Request form, then connect against the FHIR base URL https://ehr2.charmtracker.com/api/ehr/v2/fhir. |
| ChartHop (link) | No | ChartHop API access requires a ChartHop account. Generate an API token under Settings → Apps (Owner access), or register an app for the OAuth2 flow. |
| Chatbase (link) | Yes | Sign up for a Chatbase account and create an API key under the account settings. |
| Chatwoot (link) | Yes | Sign up for a free Chatwoot Cloud account (or self-host the open-source edition) and copy the access token from Profile Settings. |
| Chatwork (link) | Yes | Free Chatwork accounts can create API tokens from Service Administration → API Token. |
| Check (link) | No | Check provides a separate sandbox environment (https://sandbox.checkhq.com) with its own API key. API keys are issued to Check partners by the Check account team. |
| Checkfront (link) | No | Checkfront API access is not available on trial accounts; a paid Checkfront account is needed to create an API key / secret or an OAuth2 application under Manage > Developer. |
| Checkout.com (link) | Yes | Self-serve: sign up for a Checkout.com sandbox account and create a secret API key (sk_sbox_...) under Developers → Keys. |
| Checkr (link) | No | |
| Checkvist (link) | Yes | Sign up for a free Checkvist account; the Remote API key is on the profile settings page. |
| Cherry (link) | Yes | Sign up at trycherry.ai and create an API key in Settings → API keys. |
| ChurnZero (link) | No | The REST API is a paid add-on that your ChurnZero Customer Success Manager must enable. Then give a user the Developer Tools permission and create a key under Admin > API Keys.
|
| CiiRUS (link) | No | CiiRUS issues API credentials and test account details after partner registration; requests must come from IP addresses whitelisted by CiiRUS Support. |
| Circle.so (link) | Yes | Start a free 14-day Circle trial (no credit card), then create an Admin v2 API token under Settings > Developers > Tokens in the community.
|
| Cisco Finesse (contact for access) | No | Cisco Finesse runs on customer Unified CCE or Unified CCX infrastructure. Use lab Finesse credentials from your Cisco contact center administrator. |
| ClarifyGo (link) | No | A Super User enables Native Focus REST API in Admin → Account → Integrations and generates an API key, clientId, and integration username. Choose the regional base URL (uk, eu, us, or ca) that matches the tenant. |
| ClassMarker (link) | Yes | Create a ClassMarker account to generate API keys and webhooks under My Account → Webhooks / API Keys. Official API documentation includes example credentials for signature verification. |
| Clay (link) | Yes | Clay offers a free tier with limited search API results. Generate an API key from Settings → Account after signing up; search quotas depend on your plan (see Clay Public API docs). |
| Clear Books (link) | No | The Clear Books REST API is available to developers on request. Contact Clear Books to register a confidential OAuth2 client (authorization code grant) and obtain access to a developer sandbox. |
| Clever (link) | Yes | Creating a Clever developer account and an application automatically provisions a sandbox district with synthetic data. Its bearer token is under Data Sources > Sandbox District in the Clever App Dashboard. |
| CleverReach (link) | Yes | Sign up for a free CleverReach account, then create an OAuth app under Account → Extras → REST API with the Recipients scope. |
| CleverTap (link) | No | API access needs a CleverTap account (Account ID + passcode); CleverTap offers demos and trials through its sales team. |
| ClickFunnels (link) | Yes | Start a ClickFunnels free trial, then create a platform application under Team Settings → Developer Portal to get an API access token. |
| ClickHelp (link) | Yes | Start a ClickHelp trial portal, then generate an API key in your user profile and connect with your login, the API key and the portal host. |
| ClickHouse (link) | Yes | Create a ClickHouse Cloud trial or use the public playground at play.clickhouse.com (user <code>explorer</code>, empty password, URL <code>https://play.clickhouse.com</code>). |
| ClickSend (link) | Yes | Sign up for a ClickSend account, then create an API key under Developers → API Credentials. Use the test inbound SMS endpoint to verify webhooks without sending live traffic. |
| Clicksign (link) | Yes | Create a free Clicksign sandbox account at sandbox.clicksign.com, generate an access token, and use the Sandbox API URL. |
| Clientary (link) | Yes | Start a free Clientary trial, then generate an API token from your user profile. |
| Clientify (link) | No | Request API access from Clientify per their developer documentation. |
| Cliniko (link) | Yes | Sign up for a free Cliniko trial, then create an API key from "My Info" > "Manage API keys". Cliniko support can extend the trial on request (https://docs.api.cliniko.com/#authentication). |
| Clio (link) | Yes | Create a Clio developer application in the same region as the Manage account, then authorize with OAuth2. |
| Clockify (link) | Yes | Clockify offers a free plan with API access. Sign up and generate an API key from Profile Settings. |
| Clockodo (link) | Yes | Start a free Clockodo trial, then copy the API key from your personal data page. |
| Clockwork Recruiting (link) | No | API access is available to all firms; developer documentation and credentials are provided by the Clockwork Integrations team on request. |
| Cloudbeds (link) | No | Cloudbeds provisions OAuth2 client credentials for approved technology partners; a free property-level API key is also self-serve for testing against a real property. |
| CloudCart (link) | Yes | Sign up for a CloudCart store trial, then create an API key under Settings → API keys in the store admin. |
| Cloudflare Workers AI (link) | Yes | Sign up for a Cloudflare account, then create a Workers AI API token and copy the Account ID from AI > Workers AI > Use REST API. |
| Cloudinary (link) | Yes | Sign up for a free Cloudinary account; the API key, API secret and cloud name are under Settings → API Keys in the Console. |
| Cloudonix (link) | Yes | Create a Cloudonix account from the developer portal and issue an API key in Settings → API Keys. |
| Cloudtalk.io (link) | Yes | Start a free 14-day CloudTalk trial (no credit card), then an admin creates an API key under Settings > API Keys in the dashboard.
|
| Clover (link) | No | |
| Cloze (link) | Yes | Start a Cloze trial account, then create an API key (https://help.cloze.com/article/2176-api-key). OAuth 2.0 client credentials come from support@cloze.com. |
| CMiC (link) | No | CMiC Cloud test tenants (Atlas Test / Nova Test) require a CMiC-issued API service account. Register for developer documentation at developers.cmicglobal.com and provision credentials through your CMiC administrator. |
| CMS Blue Button 2.0 (link) | Yes | Create a free account at https://sandbox.bluebutton.cms.gov, add an application with the Unified redirect URI (confidential client), and sign in during authorization as a synthetic Medicare beneficiary (for example BBUser00000). Sandbox credentials do not work in production; production access requires a separate CMS review. |
| Coassemble (link) | No | Coassemble API access requires a paid plan with API entitlements enabled. Generate workspace credentials in Coassemble Developer settings. |
| Cobot (link) | Yes | Sign up a space on Cobot, register an OAuth app at https://dev.cobot.me/oauth2_clients for a client ID and secret, or create an access token at https://dev.cobot.me/oauth2_tokens. |
| Coda (link) | Yes | Sign up for a free Coda account, then generate an API token from My account (coda.io/account). The API is free in both free and paid workspaces.
|
| Codebase (link) | Yes | Start a 15 day Codebase free trial (no credit card needed), then copy the API username and API key from Settings → My Profile. |
| Codegen (link) | Yes | API token and organization ID are self-serve from the Codegen developer settings page. |
| Cohere (link) | Yes | Sign up for a Cohere account and create a free trial API key on the API keys page of the Cohere dashboard.
|
| Comeet (link) | No | The Careers API documentation provides public sandbox credentials (Company UID E5.007). Recruiting API access requires becoming an approved partner to receive a secret. |
| CometAPI (link) | Yes | Sign up for a CometAPI account, claim free credits if offered, and create an API key in the console. |
| CommCare (link) | No | Sign up for a CommCare HQ project (Standard plan or above required for API access). |
| Commerce Layer (link) | Yes | Sign up for a free Commerce Layer account and create an organization. Integration API credentials (client ID and secret) are created in the dashboard under API credentials. |
| commercetools (link) | Yes | Free 60-day trial projects available after signing up at commercetools.com; API Clients are created in the Merchant Center under Settings > Developer settings. |
| CompanyCam (link) | Yes | Sign up for a free CompanyCam developer account, then create a Personal Access Token (or request OAuth credentials for a partner app). |
| ComplyAdvantage (link) | No | Sandbox accounts are provided by ComplyAdvantage (limited to 300 API calls per minute); API keys are generated in the web platform. |
| CompXL (link) | No | CompAnalyst API credentials are issued by Salary.com Customer Success for existing CompAnalyst Plus or Enterprise accounts. DaaS partners can email partnerships@salary.com for test access to the separate DaaS APIs (not used by this connector). |
| concludis (link) | No | concludis API access is not self-serve: a customer account with an API-enabled user must be provisioned by concludis. Contact concludis to obtain API credentials and (for on-prem/tenant installs) the API base URL. |
| Conekta (link) | Yes | Conekta test mode: sign up at conekta.com and use the test-mode private API key from the Panel; test mode processes no real payments. |
| Conga Sign (link) | No | Conga Sign API access requires a Conga Advantage Platform account; create an Integration User / API Connection to obtain client credentials. |
| Connecteam (link) | No | API access requires an Expert-plan (or higher) Connecteam hub. Generate an API key under Settings → API Keys. |
| Conta (link) | No | Register a free account at app.conta-sandbox.no, then email Conta customer support to receive the email-verification link that enables sandbox access. Create an API key in the sandbox under User → Data & Access. |
| Contacts+ (link) | Yes | Create a free Contacts+ account, register an OAuth app at https://ui.contactsplus.com/apps, and use the Unified redirect URI when configuring the app. |
| Contentstack (link) | Yes | Sign up for a free Contentstack Explorer account, create a stack, then create a management token under Settings → Tokens. |
| ContentStudio (link) | Yes | Sign up for ContentStudio and generate an API key from the API module in the app sidebar. |
| Contractbook (link) | Yes | Contractbook provides a staging API at api-staging.contractbook.com; create a separate staging API key in your workspace settings. |
| Convolo AI (link) | Yes | Sign up for a Convolo / Brightcall account, create a Speed To Lead widget, and copy the account API key plus the widget key and widget API key from the dashboard. |
| Convoso (link) | No | Convoso is a sales engagement platform; API access and sandbox tenants are provisioned through Convoso customer success or the partner program. |
| Cornerstone (link) | No | |
| Cornerstone Saba (link) | No | Requires a Cornerstone Saba Cloud tenant and a user permitted to call REST APIs. There is no public self-serve developer signup; access is arranged with Cornerstone / the customer tenant. |
| Cornerstone TalentLink (link) | No | TalentLink API access — API key, username, password and endpoint URLs — is provisioned per client through Cornerstone / TalentLink activation (not self-serve). |
| Coupa (link) | No | Coupa test/sandbox instances are provisioned to customers and partners; there is no self-service developer signup. An integrations-enabled admin creates an OIDC client (grant type Client Credentials) and grants the required scopes. |
| Coupang (link) | Yes | Coupang has no separate sandbox: a live seller account in Coupang WING issues the OPEN API Access/Secret keys and Vendor ID used to authenticate. Register/manage keys under WING → My Office → Issue OPEN API Key. |
| Courier (link) | Yes | Create a free Courier account; the workspace has a separate test environment with its own API keys. |
| Coveto (link) | No | coveto provides a public sandbox at demo.coveto.de with interactive Swagger UI and an OpenAPI spec at https://demo.coveto.de/openapi-coveto-rest.yaml. Production access requires a coveto account and an API key created under Settings » REST-API. |
| Creatio (link) | Yes | Creatio is instance-hosted. Request a free trial instance at creatio.com/trial, then register an OAuth 2.0 application (client_credentials grant) under System Designer > OAuth 2.0 access to obtain the client id/secret. The Identity Service URL is configured in the "Authorization server Url for OAuth 2.0 integrations" system setting. |
| Creem (link) | Yes | Toggle Test Mode in the Creem dashboard and use https://test-api.creem.io/v1 with a test API key. Test card 4111 1111 1111 1111 succeeds. |
| Crelate (link) | Yes | Start a free trial of Crelate (no sales contact needed), then generate an API key under Settings | My Settings & Preferences.
|
| Crezco (link) | Yes | Request access to sandbox account through email signup.
|
| Crisp (link) | Yes | Sign up for a free Crisp workspace and generate a Website Token from Settings → Workspace Settings → Advanced configuration. |
| Criteo (link) | No | Create a Criteo partner app and client credentials in the Partner Portal. There is no public self-serve sandbox; advertiser consent is granted per portfolio in Management Center. |
| CrossKnowledge (link) | No | A CKLS instance and an administrator account are required; there is no public self-serve developer signup. Access is arranged directly with CrossKnowledge (see the CrossKnowledge - Sandbox / Developer Account Access prerequisite ticket). |
| CrowdStrike Falcon (link) | No | API access requires a Falcon subscription. Create an API client under Support & resources > API clients and keys and grant it the User Management and Alerts scopes. |
| Culture Amp (link) | No |
|
| Curated (link) | Yes | Create a Curated account and copy the Account API Key from your account settings to use the API. |
| Cursor (link) | Yes | Cloud Agents API keys are self-serve from the Cursor dashboard; running agents requires a paid Cursor plan. |
| Customer.io (link) | No | To create, edit, or delete a workspace, you must be an Account Admin. |
| CVViZ (link) | No | CVViZ API access requires a CVViZ plan with API access enabled and an authorized administrator to generate a credential under Settings -> Developers (no separate public sandbox is documented). |
| Cyclance MDM (link) | No | Create an API application under Settings > Integrations in a Cylance tenant. There is no public self-serve sandbox; a tenant administrator must issue Application ID, secret, and Tenant ID. |
| d.vinci (link) | No | A d.vinci test/customer system is required. An administrator creates an API user (login + token) in the d.vinci web UI; the customer subdomain forms the API base URL ({subdomain}.dvinci.de/restApi). |
| Dalux (link) | No | Dalux issues customer-specific API keys after enabling the API on your company profile. Use the X-API-KEY header against your assigned API base URL (the public Field node is https://node1.field.dalux.com/service/api). |
| DANA (link) | Yes | Register a sandbox merchant in the DANA dashboard, upload your public key, and use the Sandbox API URL with sandbox credentials. |
| Dandelion (link) | Yes | Create a free Dandelion account, create or join an organisation, then generate an API key from the profile edit page. Zapier/MCP access is read-only. |
| Darwinbox (link) | No | Darwinbox API access is granted on a request-only basis; contact integrationsteam@darwinbox.in to obtain credentials for a tenant.
|
| Databox (link) | Yes | Databox offers a free tier. Sign up at databox.com, then create an API key under Account Management → Profile → Password & Security (Admin role required). |
| Databricks (link) | Yes | Create a Databricks Free Edition workspace or trial, generate a personal access token, and create a SQL warehouse in the workspace. |
| DataCamp (link) | No | There is no self-serve sandbox. Access tokens are issued manually by the DataCamp Enterprise Integrations team or a CSM for a DataCamp for Business (Enterprise) group. |
| Datagma (link) | Yes | Sign up for a free Datagma account (no credit card) and use the API key from the app dashboard; the Free plan includes API access.
|
| DATEV (link) | No | DATEV partner/developer registration required; register an OAuth2 app and request the sandbox scopes. |
| DaySchedule (link) | Yes | Sign up for DaySchedule and create an API key under Settings → API keys to call the REST API. |
| Dealpath (link) | No | Dealpath has no public developer signup; request a demo from Dealpath to learn about and get access to its open API.
|
| Deel (link) | No | |
| DeepAI (link) | Yes | Sign up at DeepAI, create an API key in the dashboard, and call the documented image APIs at https://api.deepai.org/api. |
| Deepgram (link) | Yes | Sign up for Deepgram and create an API key in the console. Free credits are available for testing speech-to-text and text-to-speech. |
| DeepSearch (link) | Yes | Sign up at deepsearch.app/developers and create an API key. The documented test key dsk_test_deepsearch returns deterministic fixtures without billing. |
| Defguard (link) | Yes | Defguard is open source and self-hosted. Deploy an instance, then create an API token for an admin user. |
| Degreed (link) | No | A Degreed organization (production or betatest) with API client credentials is required. Sandbox/betatest access is provisioned by Degreed. |
| Delighted (link) | Yes | Sign up for a Delighted account and copy the API key from Integrations → API in the project settings. |
| Delivery Hero (link) | No | Request middleware credentials via the Delivery Hero developers page (PGP key required). Use staging middleware for integration testing with your local representative. |
| Demandbase (link) | No | No self-serve sandbox is documented. A Demandbase customer generates an API key set (client ID + secret) with B2B API access. |
| Demio (link) | Yes | Demio provides sandbox API keys in the account API settings for test events. |
| Dentally (link) | No | Dentally provides a sandbox API host (https://api.sandbox.dentally.co). Access is arranged with Dentally; generate a personal access token in the sandbox practice with the required OAuth scopes. |
| DentiMax (link) | No | No public self-serve developer sandbox was documented alongside the Communicator OpenAPI catalog entry. Request API credentials from DentiMax for integration testing. |
| Depop (link) | No | Depop issues separate staging and production credentials (API keys and OAuth test clients) on request via business@depop.com; the staging API is https://partnerapi-staging.depop.com and has a test-purchase endpoint. |
| Deputy (link) | No |
|
| Deskera Books (link) | No | Deskera OAuth 2.0 apps are provisioned manually: email care@deskera.com with your app name, purpose, company, email and HTTPS callback URL to receive a client_id and client_secret. Register the Unified.to OAuth callback URL as the app callback. A Deskera Books org (production or staging at booksplus.deskera.com / books-ui-staging.deskera.xyz) is required to connect. |
| DeskTime (link) | Yes | Sign up for a DeskTime account and generate an API key under Settings → API. |
| Detrack (link) | No | Request a Detrack account and API key from Detrack support or your account manager. |
| Detris (link) | Yes | Sign up at detris.ai, subscribe to a paid plan, then create an API key under Settings → API Keys. |
| DeutschlandGPT (link) | Yes | Sign up on the DeutschlandGPT platform, create an API key, and call the OpenAI-compatible API at https://api.deutschlandgpt.de/v1. |
| Devin (link) | Yes | Devin v3 credentials (an organization service user API key or a personal access token, both starting with cog_) are created under Settings > Devin API; API access requires a paid Devin plan. |
| Dex CRM (link) | Yes | |
| DialedIn (link) | No | DialedIn provisions tenant environments through sales and support. API tokens and HttpImport access are configured per tenant in the Management Portal. |
| Dialpad (link) | Yes | Use sandbox.dialpad.com API host and OAuth URLs. Create an API key from Admin Settings, or register an OAuth app via Dialpad. |
| Didit (link) | Yes | Sign up at business.didit.me, create a sandbox application, and issue an API key under API & Webhooks. |
| Digital Samba (link) | Yes | Sign up for a Digital Samba account and copy the Developer Key from the dashboard (Team -> Developers). No separate app registration is required for the REST API. |
| Dime.Scheduler (link) | No | Use the Sandbox API host (sandbox.api.dimescheduler.com) with a sandbox tenant API key. |
| DirectIQ (link) | No | Sign up for a DirectIQ account to obtain API credentials from the API Keys page. |
| Discourse (link) | Yes | Run a local Discourse instance with Docker or use a hosted trial; create an admin API key in the admin UI. |
| Divalto (link) | No | No public self-serve sandbox. OData access is provisioned per Divalto project: enable OData on the project, check "API Read" on the tables to expose, and obtain the OData login/password (CRM uses the CRM access code; ERP gets a dedicated OData code).
|
| Dixa (link) | No | Request a Dixa trial or developer workspace, then create an API token under Settings → Integrations → API. |
| Docebo (link) | No | Docebo trial / sandbox platforms are provisioned by Docebo. Once a platform exists, activate the API and SSO app (Admin menu > API and SSO) and register an OAuth2 app with the Unified redirect URI to obtain a client id/secret. |
| Docketwise (link) | No | Docketwise has no public sandbox; API access and OAuth client credentials are requested from dev@docketwise.com. |
| Docplanner (link) | No | No self-serve sandbox. API client credentials (client ID and secret) are issued by Docplanner to integration partners for a specific marketplace; request access through the Docplanner Integrations team. |
| Documenso (link) | Yes | Create a free Documenso account (or self-host), open a team, and mint an API token under Team Settings → API Tokens. Use the staging base URL for pre-production testing. |
| Document360 (link) | Yes | Start a Document360 trial, enable Customer API access on your plan, create a v3 API key, and note your project id plus workspace id from the API or portal. |
| Documo (link) | No | Documo runs a beta sandbox environment (app at https://app.sandbox.documo.com, API at https://api.sandbox.documo.com) that never sends real faxes. Create an API key in the sandbox app under Settings → API and pick the Sandbox URL on the connection. |
| Docurex (link) | No | Docurex is a tenant-hosted DMS. API credentials (customer name, username, and password) are issued by your Docurex administrator. OAuth2 staging endpoints exist in the vendor spec but production token login uses POST /auth. |
| DocuSeal (link) | Yes | DocuSeal offers a free tier and self-hosted open-source edition; create an API key from the cloud console or your on-premises instance. |
| DocuSign (link) | No | |
| Dolibarr (link) | Yes | Dolibarr offers public online demo instances (https://www.dolibarr.org/try-dolibarr-demo) that reset periodically, and the open-source app can be self-hosted for a private, persistent test instance. Enable the "API REST" module and generate an API key from a user account on the instance used for testing. |
| Donately (link) | Yes | Donately exposes a public REST API. Create an account and generate an API token from Integrations → Donately API to access your organization data. |
| Donorbox (link) | Yes | Donorbox exposes a REST API behind the paid API & Zapier add-on. Sign up, enable API access in Account settings, and create an API key to read campaigns, donors, donations, and recurring plans. |
| DonorSync (link) | Yes | DonorSync publishes a REST API for charities. Sign up for a charity account to receive API credentials, then use POST /me to verify the connection. |
| Doppler (link) | Yes | Create a Doppler account, then generate an API key under Advanced preferences in the control panel. |
| Dotpay (link) | No | Dotpay provides a test Seller panel and test payment gateway. Request sandbox access from Dotpay support or use the test_seller environment documented in the technical manual. |
| DoubleVerify (link) | No | DoubleVerify API credentials are provisioned per customer. Contact DoubleVerify for sandbox or production API access. |
| DPD (link) | No | Request DPD Label Print API credentials from your DPD account manager or support contact. |
| DrChrono (link) | Yes | Sign up for a DrChrono account (free trial), then register an API application under API Management to get a client ID and secret. Applications can be used in test mode; free-trial accounts cannot read some Level 2 endpoints such as vaccine records. |
| Drift (link) | No | Register a Drift developer app to obtain OAuth client credentials and request sandbox access from Drift. |
| Drip (link) | Yes | Sign up for a Drip account, then copy the personal API token from User Settings. OAuth2 apps are registered with Drip (tokens do not expire). |
| Dripcel (link) | Yes | Sign up for a Dripcel account and generate an API key from the API keys page to call the REST API. |
| Drips (link) | No | Drips API keys are issued per project by the Drips Client Success team. Contact Drips to request API access and a test project. |
| Dropbox (link) | Yes | Sign up for a free Dropbox account, create an app in the Developer Console, pick its scopes and access level, and use the generated app key and secret.
|
| Dropbox Sign (link) | Yes | Create a free Dropbox Sign API app in test mode. |
| DualEntry (link) | No | Ask your DualEntry administrator to generate an API key (there is no self-serve developer portal). Use it in the X-API-KEY header against https://api.dualentry.com; a development host (https://api-dev.dualentry.com) is also available. |
| Dub (link) | Yes | Sign up for a free Dub workspace and create an API key under Settings > API Keys to test customer requests. |
| Dubber (link) | Yes | Register a developer application at developer.dubber.net to obtain Mashery keys (activated by Dubber support), then use the Sandbox region with your Dubber Auth ID / Auth Token. |
| DuckDB (data api) (link) | Yes | Use the public Vercel playground, or clone https://github.com/senthilsweb/duckdb-data-api and run locally / deploy your own instance (set DUCKDB_DATABASE_URL to a DuckDB file or MotherDuck connection string). |
| e-Boekhouden.nl (link) | Yes | Self-serve: any e-Boekhouden.nl customer generates their own Access Token in Beheer > Instellingen > API-token; no separate developer/sandbox account is required. |
| E-goi (link) | Yes | Sign up for a free E-goi account, then copy the API key from the account settings. |
| eBay (link) | Yes | A free eBay Sandbox environment is available to all registered eBay Developer Program accounts. |
| EBP Compta (link) | Yes | Register for free on the EBP developer portal (developpeurs.ebp.com), subscribe to the "HUBBIX Comptabilité TPE" product, and wait for validation — EBP then emails Primary/Secondary API subscription keys. A preprod environment (api-developpeurs-preprod.ebp.com) is available alongside production. |
| EBP Gestion Commerciale Open Line (link) | Yes | Self-serve: register on the developer portal, subscribe to the "Gestion Commerciale SAAS" product, and request an OAuth2 Client ID/Secret. Subscription (API) keys are emailed once the request is validated. |
| ECI JobBOSS² (link) | No | No public self-serve sandbox. Request API activation and API-user credentials from your ECI account manager.
|
| Ecwid (Lightspeed) (link) | Yes | Create a free Ecwid account and register an application in the Developer area (my.ecwid.com → Developer/Apps) to obtain OAuth2 client credentials and test against your own store. |
| Eden AI (link) | Yes | Sign up for Eden AI and create an inference API key in the dashboard to call the v3 chat completions and models APIs (sandbox tokens are available for testing). |
| Egnyte (link) | Yes | Register a developer account at developers.egnyte.com to obtain an API key (requires domain-admin access on an eligible, non-trial Egnyte plan). OAuth2 bearer tokens are valid for 30 days and can be refreshed. |
| Elastic Email (link) | Yes | Sign up for Elastic Email and create an API key under Settings → Manage API. |
| Elation Health (link) | No | Elation provides a free, PHI-free sandbox (https://sandbox.elationemr.com) to current customers and prospective partners. Request it with the developer sandbox form; Elation emails the sandbox login, then a sandbox admin creates APIv2 credentials in Settings > API Access. |
| Elead (CDK) (link) | No | Join a Fortellis organization, register an app for OAuth client credentials, then have a dealer activate the Elead Vehicle Sales subscription. Access is partner-gated; there is no public self-serve production key. |
| Elevance Health (link) | Yes | Self-register for a Patient Access sandbox account (synthetic data) at https://sbx.totalview.healthos.elevancehealth.com/registration/sandbox/login and register the SMART client there. Point the connection at the sandbox FHIR base (https://sbx.totalview.healthos.elevancehealth.com/resources/registered/{brand}/api/v1/fhir). Production access needs the Patient Access API production request form on https://www.anthem.com/developers. |
| ElevenLabs (link) | Yes | Sign up for a free ElevenLabs account and create an API key under Settings > API Keys. |
| Elevio (link) | Yes | Sign up for an Elevio account, then generate an API key + JWT pair on the API Keys page of the dashboard. |
| Elite 3E (link) | No | Elite 3E API credentials are issued per customer via MS Entra ID app registration. Partners may request the Partner API Test Instance from partnerprogram@elite.com. |
| Elorus (link) | No | Elorus documents a demo-only header (X-Elorus-Demo) for safe development. Sign up for an Elorus account to generate an API key and organization ID. |
| EmailOctopus (link) | Yes | Create a free EmailOctopus account, then generate an API key under Developer → API keys. |
| Emelia (link) | Yes | Sign up at app.emelia.io; API keys are available from Settings → API after account creation. |
| EMIS (link) | No | No self-serve sandbox. Access to the EMIS test environment is granted after contacting partnerenquiries@emishealth.com, registering on the Interoperability Portal, an assurance request and integration call, and paying the test-environment invoice; development then runs for 6 weeks. Go-live requires a witness test plus a DPIA, current NHS DSPT submission, annual CREST/CHECK penetration test and DCB0129 clinical safety case. |
| Encharge (link) | Yes | Start an Encharge free trial, then copy the API key from Account → Info (https://app.encharge.io/account/info). |
| Endorsal (link) | Yes | Sign up at endorsal.io, create a property, then generate an API key under Profile → API. Use the Property ID from Property Settings when creating testimonials. |
| Enginemailer (link) | Yes | Sign up for Enginemailer and generate an API key under Account → User Profile. Campaign APIs require a paid plan. |
| Enrich Layer (link) | Yes | Sign up at enrichlayer.com and create an API key in the dashboard. Each successful enrichment call consumes credits per the endpoint pricing in the docs. |
| Enrich.so (link) | Yes | Sign up at enrich.so and create an API key from the dashboard. Credits apply per lookup (reverse email lookup and email finder are documented on the v3 API reference). |
| Envoy (link) | Yes | Start a free Envoy company trial, create an API user with the Global Admin role, then create an integration in the Dev Dashboard and copy its client ID and secret.
|
| Epic (link) | Yes | Create a free account at https://fhir.epic.com, register an app with the R4 APIs and the Unified redirect URI, and use its non-production client ID against the sandbox FHIR base URL https://fhir.epic.com/interconnect-fhir-oauth/api/FHIR/R4 with Epic's published test patients. |
| Epicor Kinetic (link) | No | No public hosted sandbox. Epicor Kinetic runs on the customer's own (or Epicor-hosted SaaS) instance; testing uses a partner/demo instance (e.g. the "EPIC06" education company) with a REST-enabled user and an API Key.
|
| Equativ (link) | No | Demand API access requires Equativ OAuth2 client credentials. There is no public self-serve sandbox. |
| eRecruiter (link) | No | eRecruiter API access is tenant-specific (API Key + Mandator ID + API host). There is no public self-serve sandbox; credentials come from the customer mandator. |
| ERPNext (link) | Yes | ERPNext offers hosted trials on Frappe Cloud and can be self-hosted. Create API keys on a User record (API Access) on the site used for testing. |
| Escapia (link) | No | Escapia has no self-serve developer sandbox. HSAPI credentials are issued to channel partners by Escapia / HomeAway Software, and each property management company must enable the partner. The portal documents a Mock End System used for its examples. |
| ESCO (link) | Yes | No account is needed to try the ESCO web service API; use the online API documentation to call it, or download the Local API (accept the privacy statement) to run your own copy. |
| Esendex (link) | Yes | Esendex offers a 30-day free trial with 100 SMS credits. During the trial, messages can only be sent to the phone number verified at sign-up. Generate an API password on the user profile after signing up. |
| eSignatures.io (link) | Yes | Create a free eSignatures.com account for testing. Set `test` to `yes` on contract API calls to mark demo contracts with no send fees. |
| EspoCRM (link) | Yes | EspoCRM offers an online demo and can be self-hosted for a private test instance. Create an API User (Administration → API Users) with API Key authentication and assign a role with CRM scopes. |
| eSputnik (link) | No | Request API access from eSputnik support or use an existing account; API keys are issued from the account settings. |
| eTermin (link) | Yes | Create an eTermin account to obtain API keys under Configuration → Integration → API. The public marketing site documents the REST API and webpush fields. |
| Eurécia (link) | No | Access requires an Eurécia account; generate an API token from the Administration tab of a user profile with sufficient rights. |
| Eventbrite (link) | Yes | Use your Eventbrite organizer account and API keys from the Eventbrite developer platform. |
| Eventzilla (link) | Yes | Sign in to Eventzilla, create an API key under Settings → Developers → API Credentials, and use it with API v2. |
| Everhour (link) | Yes | Sign up for an Everhour account and generate an API key from your profile settings to call the REST API. |
| Evernote (link) | Yes | Sign in with a paid Evernote account when authorizing the integration. MCP access is included on eligible personal, Business, and Teams plans. |
| Evoliz (link) | Yes | Create an Evoliz account, then generate API credentials under Applications → Available Connectors → Evoliz API. A company can be switched to non-production ("test") mode for safe testing. |
| eWay-CRM (link) | Yes | Free trial instances are self-provisioned at eway-crm.com/free-trial. Register an OAuth2 app under Administration Settings > API in the resulting eWay-CRM web app to obtain a client id/secret, using the Unified redirect URI. |
| Exact Online (link) | No | Register an app in the Exact Online App Center (apps.exactonline.com) to obtain OAuth client credentials. A trial/company account on the relevant regional host (e.g. start.exactonline.com) is required to test; access tokens live 10 minutes and refresh tokens 30 days. |
| ExakTime (link) | No | ExakTime API access uses Arcoro Customer API keys from https://my.arcoro.com/api/portal. Sign up for the developer portal at https://developer.arcoro.com/signup or contact Arcoro for a sandbox tenant. |
| Exotel (link) | Yes | Sign up for an Exotel trial account, then copy the API Key, API Token and Account SID from Settings → API Settings. |
| Explorium (link) | Yes | Create a free-trial account at explorium.ai and generate an API key in the admin console. Each match and enrichment call consumes credits per AgentSource pricing. |
| Extensiv (link) | No | REST API access is provisioned by Extensiv: the warehouse (3PL) using 3PL Warehouse Manager requests REST API keys (Client ID, Client Secret) from its Extensiv Customer Success Manager, and supplies the login ID of the user the integration acts as. |
| Facebook Messenger (link) | Yes | Create a Meta App in the Meta Developer Portal, add the Messenger product, and connect a Facebook Page. Page access tokens are derived from the connected user token.
|
| FactorialHR (link) | No | Contact account manager/executive to request sandbox and OAuth credentials.
|
| Faire (link) | No | OAuth partner apps are registered in the Faire Developer Portal (Application ID/Secret). Faire reviews and approves partner applications before production access is granted. |
| Fairing (contact for access) | No | Fairing merchant accounts include API access via dashboard API keys. OAuth partner credentials require onboarding with product@fairing.co. |
| Fal.ai (link) | Yes | Sign up for a fal account and create an API key to call hosted models and list endpoints from the Platform API. |
| FareHarbor (link) | No | FareHarbor issues API keys only to approved API partners; apply through developer.fareharbor.com. The API spec also lists a demo server (https://demo.fareharbor.com/api/external/v1), selectable as the Demo API URL. |
| FastBill (link) | Yes | Start the free 14-day FastBill Pro trial; API calls authenticate with the FastBill login email and the account API key.
|
| Fastmag (link) | No | Fastmag is customer-hosted (on-premise/per-tenant); there is no public self-serve sandbox. Access requires a Fastmag customer/demo environment and back-office API credentials from Fastmag support (contact@fastmag.fr). |
| FatTail AdBook (link) | No | AdBookConnect access is enabled per AdBook login by FatTail customer service; there is no self-serve developer sandbox. |
| Favro (link) | Yes | Start a free Favro trial organization, then create an API token from your user profile. |
| Feathery (link) | Yes | Sign up for a free Feathery account (no credit card needed), then copy a Test mode API key from the Developer tab in your settings.
|
| FeedBlitz (link) | No | No separate sandbox is documented. Use a FeedBlitz account and request an API key under My Account → API Keys. Newsflash mailings accept <testmode>1</testmode> to avoid sending. |
| Feefo (link) | No | No sandbox is documented. Using an existing Feefo merchant account, create an App Key in the Feefo Hub under Settings > Connectivity > App Keys, then open its Details to copy the Client ID and Secret. |
| Fellow (link) | Yes | No separate sandbox. Use a real Fellow workspace: an admin enables Developer API under Workspace settings → Security, then each user generates an API key under User settings → API & MCP connections. Subdomain is the host label before .fellow.app. |
| Fenerum (link) | Yes | Subscribe through Fenerum pricing (MRR-based plans; API and webhooks are included). Then in Fenerum go to Settings > Integrations and click Create API user to generate an API token.
|
| Fergus (link) | No | A Fergus account (Admin or Full User) can generate a Personal Access Token under Settings → Integrations → Fergus API. |
| Fibery (link) | Yes | Sign up for a Fibery workspace and create an API token from the workspace menu. OAuth apps are registered per workspace under Settings → OAuth Applications. |
| Field Assist (link) | No | Field Assist External API access is provisioned per customer tenant (custom api-*.fieldassist.io hosts). Request API credentials from Field Assist support (support@fieldassist.in). |
| FieldAware (link) | No | FieldAware has no self-serve developer sandbox: an account (or a business sandbox provisioned by FieldAware) and an API key are obtained through FieldAware sales or support. |
| Fiken (link) | Yes | Sign up for a free Fiken account (https://fiken.no) and register an OAuth2 application under Account settings → API to obtain a client id/secret and configure a redirect URI. Production API access costs 99 NOK/month per company; a personal API token can also be generated for single-account testing without the OAuth2 flow. |
| FileRun (link) | Yes | FileRun hosts a public demo installation (https://filerun.com/demo, admin / admin) for testing API clients; register an OAuth2 client under Control panel → API → Clients. |
| Files.com (link) | Yes | Sign up for a Files.com trial or developer sandbox at signup.files.com. API keys are created in the site admin UI under Settings → API Keys. |
| Filevine (link) | No | Filevine registers partner client credentials on request; a Filevine org is needed to create a Personal Access Token. |
| Fillout (link) | Yes | Sign up for a free Fillout account; as an organization admin, enable the API under Settings > Developer and copy the Forms API key. |
| Financial Cents (link) | No | Use a Financial Cents account and create a personal access token in Settings → API Settings. OAuth client credentials are issued by Financial Cents on request. |
| Findymail (link) | Yes | Create a Findymail account to obtain an API key. Finder credits are consumed when a verified email or profile match is returned. |
| Finmei (link) | Yes | Create a Finmei account at https://app.finmei.com and generate an API token under Settings → Integrations. The token authenticates REST requests to https://app.finmei.com/api. |
| Finmo (link) | Yes | Finmo uses one API base URL for sandbox and production; the API key pair determines the environment. Sign up for a Finmo account to generate sandbox keys in Developer Settings. |
| Fireberry (link) | Yes | Create a Fireberry account, then copy your API Access Token from Profile → Account Security → API Access Token. |
| Fireworks AI (link) | Yes | Sign up at Fireworks, create an API key in the dashboard, then call the Serverless inference API (OpenAI-compatible chat completions and models list). |
| Firmao (link) | No | Firmao API access is enabled per organization in Company → Settings → API. There is no public self-serve sandbox; use a Firmao trial or customer account with API enabled. |
| Fiserv (link) | Yes | Register on the Fiserv Developer Portal to obtain a sandbox API Key. Transactional Data sandbox records exist for merchant IDs 60001–60004. Production keys require an agreement with a Fiserv payment-processing partner. |
| FlexiSign (link) | Yes | Create a FlexiSign account and generate an API key for automated template sending. |
| Flexmail (link) | Yes | Create an account and generate a personal access token to test requests against the marketing API. |
| Flipdish (link) | Yes | Create a free Flipdish account at portal.flipdish.com/signup, then create an OAuth app under Developer tools → OAuth apps to get a Client ID and Secret Key. |
| Flipkart (link) | Yes | Create developer access from the Seller Dashboard (Manage Profile → Developer Access) to obtain an Application ID and Secret. |
| Float (link) | Yes | Any Float account can generate an API access token under Team Settings → Integrations → Float API; a free trial account can be used for testing. |
| Float Financial (link) | No | Float is a Canadian corporate spend-management platform. API keys are created by customers in-app under Settings → Developers; there is no public self-serve sandbox. |
| Flutterwave (link) | Yes | Create a Flutterwave account and copy test API keys from Settings → API Keys. Toggle test mode in the dashboard to use FLWSECK_TEST keys. |
| Folk (link) | Yes | Sign up for a Folk workspace at folk.app, then create an API key under Settings → API. |
| Folks HR (link) | No | API access requires a Folks HR account. Generate a V2 API key (Client ID / Client Secret) under Admin → API Keys Management, or request test access from Folks support. |
| Follow Up Boss (link) | Yes | Follow Up Boss offers a 14-day free trial that exposes the full v1 API. System registration for partner X-System / X-System-Key headers is at https://apps.followupboss.com/system-registration. |
| Formdesk (link) | Yes | Formdesk includes 100 free API credits to try the webservice. API keys are created in User Management; additional credits are purchased in the account. |
| Formsite (link) | No | Formsite API access requires a Professional plan. Use your production account API token and base URL from Form Settings → Integrations → Formsite API. |
| Fortnox (link) | Yes | Self-serve: register an integration in the Fortnox Developer Portal (apps.fortnox.se/developer) to obtain OAuth2 client credentials (Client ID / Client Secret). Authorize against a Fortnox company; the OAuth2 authorization-code flow issues an access token (valid 1 hour) and a refresh token (valid 45 days, rotated on each refresh). |
| Foundation Software (link) | No | Contact Foundation API Support at (800) 811-5926 for sandbox subscription keys, OAuth client registration, and CRM Client ID assignment. |
| Frame Payments (link) | Yes | Register for a Frame merchant account to obtain sandbox API keys (sk_sandbox_*). |
| FreeAgent (link) | Yes | Self-serve: register an app in the FreeAgent Developer Dashboard (https://dev.freeagent.com) to get OAuth client credentials, and use a sandbox account at api.sandbox.freeagent.com. |
| FreeWheel (link) | No | No public self-serve sandbox. FreeWheel issues OAuth2 client credentials per customer Streaming Hub account (production and a staging environment at api.stg.freewheel.tv share the same credential-issuance flow) — a Streaming Hub Admin creates them from the API Management section. |
| freshdesk (link) | No | |
| Freshservice (link) | Yes | Create a trial Freshservice account; an API key is available per-agent under Profile Settings for testing. |
| Freshteam (link) | No | |
| Front (link) | Yes | Start a trial workspace and use developer tokens for testing API calls. |
| Fulcrum (link) | Yes | Sign up for a Fulcrum account (free trial), then create an API token under Settings → API. |
| FullEnrich (link) | Yes | Sign up at fullenrich.com and create an API key in the dashboard. Enrichment and lookup calls consume API credits per the pricing in the docs. |
| Fulll (link) | No | OAuth2 client credentials (client_id/client_secret) are issued by Fulll on request; no public self-service developer sandbox signup is documented. |
| FullStory (link) | Yes | Sign up for a FullStory trial or demo account, then create an API key under Settings → Integrations → API Keys. Architect-level keys are needed for read APIs such as user lookup and session events. |
| FuseDesk (link) | No | FuseDesk API access requires an admin-created API key on your FuseDesk account. Use your application subdomain with the v1 REST API. |
| FusionAuth (link) | Yes | FusionAuth Community edition is free to self-host: run it with Docker, finish the setup wizard, then create an API key in Settings → API Keys. |
| Garmin (link) | No | Access to the Garmin Activity API requires joining the Garmin Connect Developer Program (https://developer.garmin.com/gc-developer-program/overview/). Create the client ID and secret in the Developer Portal APP tab (https://developerportal.garmin.com/developer-programs/connect-developer-api), then enable the Activities summary types in the Endpoint Configuration tool (https://apis.garmin.com/tools/endpoints). Starter Access covers up to 1,000 connected users with push-only delivery; Enterprise Access adds historical data and Ping/Pull. Contact connect-support@developer.garmin.com for onboarding. |
| Gelato (link) | Yes | Sign in to the Gelato dashboard and open the API Portal to generate an API key. Use the key in the X-API-KEY header against the documented Gelato API hosts (orders, product catalog, shipment, ecommerce). |
| Gem (contact for access) | No | |
| Genesys Cloud (link) | Yes | Create a free Genesys Cloud developer organization and register an OAuth client in Admin → Integrations → OAuth to obtain client credentials for your region. |
| Gentu (link) | No | After a marketplace agreement, sign up on the sandbox developer portal, create an app, enable the Healthcare / Bookings API products and email pmdeveloperpartnerssupport@magentus.com for approval. Magentus provisions two seeded test practices (https://sandbox.gentu.com.au), one already paired with the app.
|
| GetAccept (link) | Yes | Sign up for a free GetAccept trial account, then register an OAuth2 app under Settings → Integrations → API. |
| GetResponse (link) | Yes | Sign up for a GetResponse account and create an API key under Integrations & API. JSON webhooks are configured in Tools → Webhooks. |
| Ghost (link) | Yes | Set up a Ghost(Pro) site or a self-hosted Ghost install (Ghost-CLI), then create a Custom Integration under Settings → Integrations for an Admin API key. |
| Gigasheet (link) | No | Request API access from Gigasheet support or your account settings (Automation → API key). |
| Gitea (link) | Yes | Gitea is self-hosted; use gitea.com for a public instance or run your own server for testing. |
| Givebutter (link) | Yes | Givebutter offers a public REST API. Create a free account and generate an API key from Settings → Developers → API to call the sandbox or production organization data for that key. |
| Gladly (link) | No | |
| Gleap (link) | Yes | Create a Gleap project (EU or US region), enable the REST API under Project Settings → Security, and use that project’s API key and Project ID. |
| GLPI (link) | Yes | Install GLPI 11 (free, open source; an official Docker image is available) or start a GLPI Network Cloud trial, enable the API under Setup → General → API, and add an OAuth client with the Password grant and the api scope under Setup → OAuth clients. |
| Gmelius (link) | No | Sign in to the Gmelius dashboard as an admin or manager and open the account API page to get a client_id and client_secret. No sandbox is documented; request a trial from success@gmelius.com.
|
| GoCardless (link) | Yes | Create sandbox account through signup form. |
| GoDial (link) | No | GoDial manager account with External API access (Dashboard → Integration → External API). |
| Gong (link) | No | Sign up for a demo account |
| GonnaOrder (link) | Yes | Staging Admin API at https://admin.wannaorder.net. Generate a store API token from My profile. |
| Goodbits (link) | Yes | Sign up for Goodbits and create a newsletter to obtain an API token from newsletter settings. |
| Google AdMob (link) | Yes | Sign up for a free AdMob account, enable the AdMob API in a Google Cloud project and create OAuth 2.0 credentials. |
| Google AdSense (link) | Yes | Sign up for a free AdSense account, enable the AdSense Management API in a Google Cloud project and create OAuth 2.0 credentials. |
| Google App Engine (link) | Yes | Create a Google Cloud project, enable the App Engine Admin API and create an App Engine application, then create a service account with the App Engine Viewer role and download its JSON key. |
| Google BigQuery (link) | Yes | Create a Google Cloud project and enable the BigQuery API in the Google Cloud Console. The BigQuery sandbox offers free usage without a credit card. |
| Google Business Profile (link) | No | Requires a Google Business Profile with a verified location and Business Profile API access approved via the Google API console request form. |
| Google Chat (link) | Yes | Use a Google Workspace test domain and enable the Google Chat API in Google Cloud Console. |
| Google Classroom (link) | No | |
| Google Cloud Functions (link) | Yes | Create a Google Cloud project, enable the Cloud Functions API, then create a service account with the Cloud Functions Viewer role and download its JSON key. |
| Google Cloud Healthcare API (link) | Yes | Create a Google Cloud project, enable the Cloud Healthcare API, create a dataset and an R4 FHIR store, then create a service account with the Healthcare FHIR Resource Editor role and download its JSON key. |
| Google Cloud Run (link) | Yes | Create a Google Cloud project, enable the Cloud Run Admin API, then create a service account with the Cloud Run Viewer role and download its JSON key. |
| Google Cloud Talent Solution (link) | Yes | Create a Google Cloud project, enable the Cloud Talent Solution API, create a tenant, then create a service account that can manage Cloud Talent Solution companies and jobs and download its JSON key. |
| Google Cloud Text-to-Speech (link) | Yes | Create a Google Cloud project, enable the Cloud Text-to-Speech API and create OAuth 2.0 credentials. |
| Google Cloud TPU (link) | Yes | Create a Google Cloud project, enable the Cloud TPU API, then create a service account with the TPU Viewer role and download its JSON key. |
| Google Compute Engine (link) | Yes | Create a Google Cloud project, enable the Compute Engine API, then create a service account with the Compute Viewer role and download its JSON key. |
| Google Contact Center AI Insights (link) | Yes | Create a Google Cloud project, enable the Contact Center AI Insights API, then create a service account with the Contact Center Insights Viewer role and download its JSON key. |
| Google Gemini (link) | Yes | Sign in to Google AI Studio with a Google account, accept the Terms of Service, and create a Gemini API key from the API Keys page; the Free tier covers getting started.
|
| Google Jules (link) | Yes | Jules API keys are self-serve from the Jules settings page; the repository must first be connected to Jules via its GitHub app. |
| Google Kubernetes Engine (link) | Yes | Create a Google Cloud project, enable the Kubernetes Engine API, then create a service account with the Kubernetes Engine Viewer role and download its JSON key. |
| Google Manufacturer Center (link) | No | Requires a Manufacturer Center account (brand-owner verification) and the Manufacturer Center API enabled in a Google Cloud project. |
| Google Merchant Center (link) | Yes | Create a free Merchant Center account, enable the Merchant API in a Google Cloud project and register it as a developer. |
| Google Places API (link) | Yes | Create a Google Cloud project, enable Places API, and generate an API key for testing. |
| Google Play Console (link) | No | Requires a Google Play developer account with an app listed in the Play Console and the Google Play Android Developer API enabled in a Google Cloud project. |
| Google Search Ads 360 (link) | No | Search Ads 360 is a paid product: contact Google sales ("Talk to Sales") to subscribe, then have a manager-level user grant your Google Account access. API access uses a Google Cloud project with the Search Ads 360 Reporting API enabled and an OAuth client.
|
| Google Vertex AI (link) | Yes | Create a Google Cloud project, enable the Vertex AI API, then create a service account with the Vertex AI User role and download its JSON key. |
| GorillaDesk (link) | No | API keys are created in-product (Add-ons → API) on a GorillaDesk Pro account. There is no separate public sandbox tenant documented for API testing. |
| GoSquared (link) | Yes | GoSquared offers a free trial. Create a test project in your account before sending production traffic; the public API docs include a read-only demo api_key for examples. |
| GR8 People (link) | No | GR8 People can provision development/final-test API credentials on request via your implementation contact; there is no self-serve sandbox. |
| Grafana (link) | Yes | Use Grafana Cloud free tier to get an instance and API token for testing. |
| Granola (link) | No | Granola has no sandbox. On a Business or Enterprise plan, create an API key in the desktop app under Settings > Connectors > API keys.
|
| Greenhouse (link) | No | To use the sandbox, open a separate browser window from the one running your production Greenhouse environment.
|
| Greenhouse (Ingest) (link) | No | To use the sandbox, open a separate browser window from the one running your production Greenhouse environment.
|
| Greenhouse Assessment (link) | No | To use the sandbox, open a separate browser window from the one running your production Greenhouse environment.
|
| Greenshades (link) | No | Contact Greenshades to receive a client ID, client secret and scopes.
|
| Greenway Health (link) | Yes | Register on the Greenway Developer Platform, create a SMART on FHIR app with the Unified redirect URI, and test against the staging FHIR server (https://fhir-api.fhirstaging.aws.greenwayhealth.com/fhir/R4/{tenant}, set as the workspace API URL). |
| Grist (link) | Yes | Free Grist account on getgrist.com; API keys available under Profile settings for development. |
| GRM (link) | No | API keys are issued from a VisualVault/GRM admin account. A demo host (demo.visualvault.com) exists for VisualVault; GRM customer vaults are provisioned by GRM. There is no self-serve developer signup for the HTTP APIs. |
| Guesty (link) | No | Guesty has no self-serve developer sandbox. Open API keys (client ID + client secret) are created inside a Guesty account; a trial or partner account is arranged with Guesty. |
| Gumroad (link) | Yes | Self-serve: create a Gumroad account and register an OAuth application (or generate an access token) under Settings → Advanced. |
| Gusto (link) | No | |
| HackerRank Work (link) | No | HackerRank for Work API tokens are created in-product under Settings → API. A trial or enterprise account is required; contact HackerRank sales or support for sandbox access. |
| HackMD (link) | Yes | Sign up for a HackMD account, then create an API token under Settings → API. |
| Halaxy (link) | No | Halaxy has no separate developer sandbox: API keys are created on a Halaxy practice account that has the paid Halaxy API add-on (https://developers.halaxy.com/docs/authentication). Requests are rate-limited to 500 per minute per OAuth client. |
| HappyFox (link) | Yes | Start a HappyFox trial, then enable Apps → Goodies → API to create an API key and auth code. |
| Harri (contact for access) | No | Harri’s developer portal is membership-gated. You’ll need API access + OAuth2 client credentials from Harri to test. |
| Harver (link) | No | Harver issues per-account API credentials (Client ID/Secret) for the Test and Production environments. |
| Harvest (link) | Yes | Sign up for a free Harvest trial, then generate a Personal Access Token and copy the Account ID at https://id.getharvest.com/developers. |
| HCSS (link) | No | HCSS API access requires a developer application registered in the HCSS Developer Portal. Sandbox or production credentials are issued by HCSS during onboarding. |
| Health Gorilla (link) | No | Request a sandbox tenant through https://healthgorilla.com/home/contact. Health Gorilla issues OAuth 2.0 client credentials per tenant and environment with the resource scopes your app needs; register the Unified redirect URI as the callback URL and connect with the Sandbox environment (https://sandbox.healthgorilla.com/fhir/R4). |
| Healthie (link) | No | Healthie provides a staging GraphQL endpoint (https://staging-api.gethealthie.com/graphql) with isolated data. Request sandbox API access through Healthie support or your account team. |
| Heartbeat (contact for access) | No | Heartbeat API access requires a Grow or Scale plan; create a developer community or use a customer sandbox account for testing. |
| Helcim (link) | No | Email Helcim support (tier2support@helcim.com) with your existing Helcim merchant ID to request a developer test account, then create an API Access Configuration under All Tools > Integrations to generate the API token.
|
| HelloAsso (link) | Yes | Create a test association on the HelloAsso sandbox (helloasso-sandbox.com), then use its API client with the Sandbox URL (api.helloasso-sandbox.com). |
| HelloLeads (link) | Yes | Create a HelloLeads account on helloleads.io, then enable API access under Settings → API integration. |
| HelpDesk (link) | Yes | Create a Personal Access Token in the Text Developer Console (HelpDesk / LiveChat accounts). Use HTTP Basic auth with your Account ID and token against https://api.helpdesk.com. |
| HelpJuice (link) | Yes | Sign up at helpjuice.com, then enable API access under Settings > API Credentials and copy the API key plus your account subdomain. |
| HelpSpot (contact for access) | No | HelpSpot offers hosted trials; generate a staff API token and enable the Private API in Admin → Settings → Web Services API. |
| Helpwise (link) | No | Request a Helpwise demo or trial workspace, then generate API credentials under Settings → API. |
| Heroku (link) | No | |
| Hetzner Cloud (link) | Yes | Register a Hetzner account, create a project in the Hetzner Console, then generate a Read or Read & Write API token under Security > API tokens.
|
| Hex (link) | Yes | Sign up for a Hex workspace, enable API access under workspace security settings, then create a personal or workspace API token from Account → API keys. |
| Hexnode (link) | No | Enable API access in Admin > API and retrieve your API key from the Hexnode MDM portal. |
| HeyReach (link) | Yes | HeyReach offers a free trial (no credit card required). Public API access and API-key management are available in the app under Settings → Integrations. |
| Heyy (link) | Yes | Sign up for Heyy and create an API key from the workspace API Keys settings page. |
| Hiboutik (link) | Yes | Open a free Hiboutik account from hiboutik.com, then use your user email and the API key shown under Settings > API in the back office as Basic Auth credentials. |
| HighLevel (link) | No | |
| Highperformr (link) | Yes | Generate an API key under Settings → API Keys in a Highperformr workspace. Credit-based enrichment and discovery APIs apply per workspace balance. |
| HighQ (link) | No | OAuth apps are registered per Collaborate instance by a system administrator (System administration → API application registration). Swagger is available on each instance at /showSwaggerUI.action. There is no public self-serve sandbox. |
| Hightouch (link) | No | Create a workspace API key in Hightouch to list sources, models, destinations, and syncs. |
| HitPay (link) | Yes | Sign up for a HitPay account and generate sandbox API keys from the dashboard. Use https://api.sandbox.hit-pay.com/v1 as the API base URL. |
| Hiveage (link) | Yes | Hiveage has a free plan: sign up, then copy the API key from Launchpad → Your Global Profile. |
| Homerun (link) | Yes | Start the 15-day free trial (no credit card needed), then generate an API key with scopes on the Integrations page in the Homerun app.
|
| HoneyBook (link) | No | HoneyBook registers OAuth clients manually (no self-service). Contact HoneyBook to have your application reviewed and registered; you receive a client_id, the issuer URL and granted scopes — no client secret is issued (private_key_jwt client authentication via a hosted JWKS URL). Redirect URIs are matched exactly (HTTPS, no wildcards). |
| Horus (link) | No | Email developer@horus-software.be with the subject "New Api Integration Request" (integration name, contact, purpose, redirect URLs) to get a client ID and secret; use a Horus Office test license or test folder for write calls.
|
| Hospitable (link) | No | No sandbox. OAuth vendor credentials require applying to become an approved vendor (Partner Portal access); a Hospitable account can test with its own Personal Access Token. |
| Host Tools (link) | No | Host Tools has no developer sandbox. A Host Tools account (including a free trial) provides the Auth Token used to call the API. |
| Hostaway (link) | No | Hostaway has no self-serve developer sandbox. API access (account ID + API key) comes from a Hostaway account dashboard; a trial or partner account is arranged with Hostaway. |
| Hostex (link) | No | Hostex has no self-serve developer sandbox. API access needs a Hostex account on the Pro plan; create the access token in the account. |
| Hostfully (link) | No | Hostfully API keys come from the Agency Settings page of a Hostfully account whose plan includes API access. Hostfully provides sandbox accounts (sandbox-api.hostfully.com) on request. |
| Hosthub (link) | No | Hosthub has no developer sandbox; an API key is created from the Settings page of a Hosthub account (the key may need to be requested from support). |
| HR Avatar (link) | No | API credentials and Organization ID are issued by HR Avatar (see https://www.hravatar.com/api). The JSON API host is https://test.hravatar.com; there is no self-serve developer signup. |
| HR Cloud (link) | No | Contact HR Cloud to enable API access; sandbox/testing details via support. |
| HR Partner (link) | Yes | Sign up for an HR Partner trial or paid account, enable API access under Setup → Configure → Integrations, and generate an API token. |
| HR WORKS (link) | No | Use sandbox credentials from HR WORKS demo environment at api.demo-hrworks.de. |
| Hub Planner (link) | Yes | Account owners can enable the API and generate keys under Settings → API; use a trial account for testing. |
| HubSpot (link) | Yes | Free developer accounts available with full functionality (except custom domains). Accounts never expire. |
| Humaans (link) | No | |
| Humana (link) | No | Register an organization and app on the Humana developer portal (https://developers.humana.com/user-registration). Sandbox/QA test members (eg. FHIRTest0001, FHIRTest0002) are issued after Humana completes IP whitelisting; the test password is sent by email. |
| Humanitix (link) | Yes | Sign in to Humanitix, generate a Public API key under Account → Advanced, and use it with the read-only Public API. |
| Hygraph (link) | Yes | Free Hygraph account with a self-serve project provides a Content API endpoint and Permanent Auth Tokens. |
| Hyperline (link) | Yes | Self-serve: create a Hyperline account, generate an API key from Settings > API, and use `test_`-prefixed keys against the sandbox base URL for testing without real money/banking operations. |
| Hyperswitch (link) | Yes | Sign up for a free Hyperswitch account, open the sandbox (test mode) dashboard and create an API key under Developers → API Keys. |
| Hyperwallet (link) | Yes | Self-register for a Hyperwallet Developer Sandbox in the Program Portal; the Credentials page shows the auto-generated REST API username, password and program token. Use the Sandbox API URL. |
| Iceberg Database (link) | Yes | Sign up for Iceberg Database, create an API key, and use the cloud API host or your self-hosted base URL. |
| iCIMS (link) | No | |
| Iconik (link) | No | Requires an Iconik tenant and an administrator to create a Service account application and token under Admin → Settings → Application Tokens. |
| iContact (link) | Yes | Register at icontact.com (trial or paid), then create a Custom API Integration under Settings and Billing to obtain an API-AppId and API password. Account ID and Client Folder ID are discovered automatically on connect. |
| Icypeas (link) | Yes | Create an Icypeas account and enable API access in the dashboard. Lookups consume credits per the pricing in the API docs. |
| iDenfy (link) | No | API key pairs are issued by iDenfy support or sales. In the development environment iDenfy can return predefined dummy results instead of running real checks. |
| IDmission (link) | No | Access to the IDentity Portal is granted by IDmission sales/customer success (customersuccess@idmission.com); once logged in, use "Generate Sandbox Testing Credentials" on the Downloads page. |
| IFS Applications (link) | No | IFS Applications is deployed per customer. Request a non-production IFS Cloud tenant or on-premise lab environment from IFS or your partner; API users and OAuth clients are configured in IFS Solution Manager / IFS Cloud admin. |
| IgniSign (link) | Yes | IgniSign offers a free development environment. Create an account, add an application, and generate a development API key (skv2_…) to test signature requests without production billing. |
| iiko (Syrve) (link) | No | Register an application in the iiko (or Syrve) Developer Portal to get an appId and clientSecret; the API key comes from an iikoWeb / Syrve App account with at least one organization. There is no public demo organization. |
| iManage (link) | No | Register via the iManage Universal API Developer portal; iManage provisions a developer tenant after approval. App registration in iManage Control Center yields client_id / client_secret. |
| InfluxDB Cloud (link) | Yes | Sign up for a free InfluxDB Cloud account, create an API token, and use your regional cluster URL from the organization homepage. |
| Infobip (link) | Yes | Sign up for a free Infobip trial account, then create an API key and copy your personal base URL from the API documentation hub. |
| Infor M3 (link) | No | No public self-serve sandbox. Testing needs an Infor partner or customer CloudSuite M3 tenant (for example a TST tenant) with a Backend Service .ionapi file linked to an M3 user.
|
| Innovorder (link) | No | No self-serve sandbox signup is documented; contact Innovorder to obtain a test brand and API credentials. |
| Inqom (link) | No | Inqom access is gated behind its Partner/Marketplace program (OAuth2 Authorization Code, client_id/client_secret + redirect URI issued after approval). A staging environment exists at api-staging.inqom.com / auth-staging.inqom.com. |
| Instamojo (link) | Yes | Sign up for a free sandbox account at test.instamojo.com (no onboarding documents needed); the Client ID and Client Secret are under https://test.instamojo.com/integrations/. |
| Instructure Canvas (link) | No | Any existing Canvas institution admin can self-serve a personal access token immediately from Account > Settings (no separate "sandbox" mode exists — the production API of an institution's own instance is used for testing). For a brand-new test instance, Instructure now requires going through a sales demo rather than self-service signup.
|
| INSZoom (link) | No | Zoom API access is enabled per firm after subscribing in INSZoom; INSZoom provides the encrypted authentication string and subscription keys. |
| IntakeQ (link) | Yes | Sign up for IntakeQ / PracticeQ, then enable the Developer API under More → Settings → Integrations and copy the API key from that page. |
| Intercom (link) | No | Only availble for Expert or Advanced Plan |
| Intuit Enterprise Suite (link) | Yes | Sandbox company automatically provided with developer account. Valid for 2 years.
|
| Invenias (link) | No | Contact your Invenias account manager to arrange for a sandbox environment. |
| Invoice Ninja (link) | Yes | Sign up for a free Invoice Ninja account (or self-host it), then create an API token under Settings → Account Management → API Tokens. |
| InvoiceXpress (link) | Yes | Sign up for a free 30-day InvoiceXpress trial (https://web.invoicexpress.com/signup). The API key and account name are listed under Account → API once the account exists. |
| IRIS CRM (link) | No | No public self-serve sandbox is documented. IRIS CRM is a live back-office CRM for payment ISOs/resellers; a per-user API token is generated from an existing account under Settings -> API Settings. |
| Iris HR (link) | No | Email hrapi@iris.co.uk to request a Client Key and Client Secret for a Partner Sandbox (or Practice) environment, naming the recipient and the environment needed; approval can take up to 5 working days.
|
| Iterable (link) | No | Iterable API access requires a project; create API keys in the Iterable dashboard. |
| ITM Platform (link) | Yes | Sign up for ITM Platform, then generate an API key under My Profile. Use your account slug as the account name. |
| iVvy (link) | No | iVvy has no self-serve sandbox: API keys are generated in an iVvy account and API access is a paid add-on (contact sales@ivvy.com). |
| iZooto (link) | No | API access needs an iZooto account with a website set up; the API key is requested from the iZooto panel (Settings → General → Keys) and must be approved by iZooto before it can be used. |
| Jamf (link) | No |
|
| Jane (link) | No | Jane Developer Platform partners are registered by Jane (contact the Jane Developer Platform Partnerships team) and receive a Partner Development environment, client credentials and a playground clinic. Authorize against the jane_partner_sandbox realm with the sandbox clinic URL. |
| JobAdder (link) | No | |
| JobAdder Assessment (link) | No | Requires a JobAdder developer account and partner approval (partner_ui_action scope). |
| JobAffinity (link) | No | JobAffinity does not offer self-serve sandbox access. Request API credentials (login and password) by emailing support@intuition-software.fr. |
| Jobcase (link) | No | API keys are issued on request: email partner-support@jobcase.com to get a key; the docs mention sandbox accounts but not how to obtain one, so ask in the same request.
|
| JobDiva (link) | No | |
| JobElephant (link) | No | JobElephant provides a sandbox API host (sand.api.jobelephant.com). API access is invite-only; contact JobElephant to obtain sandbox credentials and an API Key. |
| Joblogic (link) | No | Joblogic provides a UAT environment (https://uat.joblogic.com, API https://uatapi.joblogic.com/api/v1). API credentials and IP allowlisting are provisioned per customer by Joblogic Support. |
| JobNimbus (link) | No | JobNimbus API keys are created in-product (Settings → API). There is no separate public sandbox tenant; use a developer or trial account for testing. |
| JobScore (link) | No | |
| Jobsoid (link) | Yes | |
| Jobtrain (link) | No | Jobtrain enables the API for a client after a Partnership Agreement is signed; Jobtrain then installs it on the Test and Live systems and provides the Client ID and Client Secret. |
| Jobvite (link) | No | Partner Program provides access to sandbox account.
|
| Jobylon (link) | No | A staging environment is available at https://staging.jobylon.com (Partner API under /partner/v1). Contact Jobylon to obtain a partner API token. |
| JOIN (link) | Yes | Start the 14-day free trial of the Advanced plan, then generate an API token under Settings > Developer > Generate new Token.
|
| Journeyfront (link) | No | Journeyfront documents a sandbox host at https://sandbox.journeyfront.com. API keys are issued by Journeyfront. |
| journy.io (link) | Yes | Create a journy.io account and generate an API key in the connections screen to test the endpoints. |
| Jumpseller (link) | Yes | Start a free 7-day Jumpseller trial store, then copy the API login and auth token from Account → Preferences. For OAuth, register an app as described at https://jumpseller.com/support/apps/. |
| JustCall (link) | No | Must be a partner |
| Justworks (link) | No | |
| Kahoot! (link) | No | The Kahoot Reports API requires authorized access. Contact Kahoot to enable API access for your organisation and to obtain OAuth2 client credentials (client id/secret) and your organisation id. Availability depends on your Kahoot plan. |
| Kanban Tool (link) | Yes | Sign up for a Kanban Tool trial; enable API access under My profile to generate a personal token. |
| Kanbanize (link) | No | Request a Businessmap trial or demo account, then create an API key under My account → API in your workspace. |
| Kantata OX (link) | No | Registering an OAuth application requires a paid Kantata OX account and an account administrator. |
| Kapso (link) | Yes | Use the Kapso sandbox to test WhatsApp agents without production credentials. |
| Karbon HQ (link) | No | Contact Karbon to register for API access and receive credentials. |
| Kashoo (link) | No | Sign up for a free Kashoo trial to get a user and business, and ask Kashoo to put the business on a free subscription for development. Third-party OAuth2 apps need Kashoo to register them and issue a client ID and secret.
|
| Katana (link) | Yes | Start a Katana free trial, then create an API key in Settings → API. |
| Kaufland (link) | No | Seller API access requires a Kaufland Global Marketplace seller account; the Client Key / Secret Key pair is generated in the Seller Portal under Settings → API. A public API playground is available at https://sellerapi-playground.kaufland.com/. |
| Kayako (link) | Yes | Start a Kayako trial instance, then sign in with an agent or admin email and password that does not use two-factor authentication. |
| Keap (link) | No | |
| Keka (link) | No | Keka provides a kekademo sandbox environment. API access (client id/secret + API key) is created in Keka Global Settings > API Access Management; App Portal / marketplace partners activate a sandbox via the developer portal. |
| Kenjo (link) | No | Kenjo provides a sandbox host (https://sandbox-api.kenjo.io/api/v1). API access is enabled by Kenjo Customer Success; an admin then generates an API key under Settings > Integrations > API keys. |
| Kevel (link) | No | Kevel provisions a network and API key per customer; contact Kevel to obtain a test network and API key. |
| Keycloak (link) | Yes | Keycloak is free and open source. Run a local server for testing (e.g. `docker run quay.io/keycloak/keycloak start-dev`), then create a confidential client with a service account and the realm-management roles to obtain the Client ID / Secret. |
| Kimai (link) | Yes | Start a free Kimai Cloud trial or self-host Kimai (open source), then create an API token in your user profile under API Access. |
| Kimi (link) | Yes | Sign up for a Kimi developer account and create an API key in the console to call the chat completions and models APIs. |
| Kintone (link) | Yes | Free Kintone developer account (subdomain) for testing; register an OAuth client under Kintone System Administration. |
| Kissflow (link) | Yes | Start a free Kissflow trial, then create an access key under My settings → API authentication → Access keys and copy the Account ID from Account identifiers. |
| Kit (link) | Yes | Sign up for a free Kit account, then create a V4 API key or register an OAuth app under Account Settings → Developer settings. |
| Klaviyo (link) | No | |
| Klipfolio (link) | Yes | Sign up for a Klipfolio account and generate an API key from My profile. |
| Knack (link) | Yes | Knack trial apps include REST API access; create an app and generate API credentials under Settings → API & Code. |
| Knock (link) | Yes | Sign up for a free Knock account. Every account has a Development environment with its own secret key (sk_test_…). |
| KnowBe4 (link) | No | The Reporting API is available on Platinum, Diamond, SAT Foundations, and SAT Advanced subscriptions. Generate a Reporting API token in the KSAT console under Account Settings → API. |
| Kunas (HotelSync) (link) | No | HotelSync provides a staging environment (beta.hotelsync.com) with its own partner token; create one test property there.
|
| La Growth Machine (link) | No | API access (REST API, inbox webhooks, and outbound webhooks) is available on the Pro plan. Generate an API key from Settings → API in the LGM app. |
| Labcorp (link) | No | Labcorp provisions OAuth 2.0 client credentials per environment (Sandbox, Certification, Production) after a request through Contact Sales on https://developer.labcorp.com. Sandbox tokens come from https://auth-stage.dev.aperture.labcorp.com/oauth2/token and only work against the sandbox API hosts. |
| LabsMobile (link) | Yes | Create a LabsMobile account, generate an API token under API Settings, and use test=1 on send requests for simulated delivery without charging credits. |
| Laposta (link) | Yes | Sign up for Laposta and create an API key under account settings. The public API docs include a test API key for read-only exploration. |
| Lark (link) | Yes | Create a free custom app in the Lark Developer Console (open.larksuite.com/app), enable the required scopes, and configure an OAuth redirect URL.
|
| LastApp (link) | No | Per the API docs ("Development tools"): after registering as an integrator on the LastApp Developer Portal, use its Store section to create a dummy organization with one location (pre-seeded with a floorplan, catalog, schedules, etc.) for testing. No public self-serve signup URL for the Developer Portal itself was found in the docs. |
| Lattice (contact for access) | No |
|
| Lavu (link) | No | The Lavu API credentials (data name, key and token) are issued for a Lavu account; there is no self-serve sandbox. |
| Law Ruler (link) | No | Law Ruler does not publish a shared API sandbox. API keys and portal URLs are issued per firm under Setup → 3rd Party Integrations. |
| LawCruit (link) | No | LawCruit / Micron issues SOAP credentials (authorization token, admin username/password, and a job posting URL). The published WSDL is hosted on the beta web service. There is no self-service developer signup. |
| Lawcus (link) | No | Lawcus has no public sandbox. Lawcus offers a trial account (Start Trial on lawcus.com); OAuth2 client credentials (client ID and secret) are issued by the Lawcus team on request, while a long-life API token can be created by any user under Settings > API Tokens. |
| Lawmatics (link) | No | Lawmatics has no public sandbox. Developer apps are created from a Lawmatics account that has developer settings enabled (ask support@lawmatics.com). |
| LawVu (link) | No | LawVu provides a developer sandbox after registration (developer@lawvu.com). OAuth clients are created in the Integrations area; production clients require LawVu approval. |
| Lazada (link) | Yes | Register an app in the Lazada Open Platform console to obtain an app_key/app_secret and a test seller account. |
| Lead Docket (link) | No | API access requires a Lead Docket firm account; keys are issued per firm in Account Settings. |
| Leadfeeder (link) | Yes | Sign in to Leadfeeder, create an API key under Settings → Personal → API Keys, then connect with that key. Most API calls require an account_id (resolved automatically from GET /v1/accounts). |
| LeadFuze (link) | Yes | Register at console.leadfuze.com. An API key is created on signup (lfz_ prefix). Enrichment credits are consumed when a profile match is found. |
| LeadIQ (link) | No | LeadIQ API access requires a LeadIQ account with API credits. Request API access via https://leadiq.com/enrichment-apis or contact api@leadiq.com. |
| LeadMagic (link) | Yes | Create a free account at leadmagic.io and generate an API key under Settings → API Keys. Enrichment endpoints consume plan credits per successful lookup. |
| LEAP (link) | Yes | Register in the LEAP Developer Console; it issues a Sandbox API Key for development and testing (not for production use). |
| Learn365 (link) | No | Learn365 runs on a Microsoft 365 tenant. A global admin generates an API key under Learn365 Admin Center > All catalogs > Administration > API key management; the key authenticates as HTTP Basic with username "apikey". |
| LearnWorlds (link) | No | A free trial school can be created; API access must then be requested from the school settings. |
| Leiga (link) | Yes | OpenAPI credentials are created in your Leiga workspace under Settings → OpenAPI. |
| Lemon Squeezy (link) | Yes | Use Test mode in the Lemon Squeezy dashboard; API keys created in test mode only access test data. |
| Lever (link) | No | Must become partner first, then sign up for Sandbox OAuth. Lever support team provides OAuth credentials.
|
| Lexware Office (link) | Yes | Self-serve: create a Lexware Office account and generate a Public API key under Settings → Public API. There is no separate sandbox host. |
| Lightcast (link) | Yes | Free Open Skills API access; register for client credentials that use the emsi_open scope. |
| Lightfield (link) | Yes | Sign up at lightfield.app and generate an API key in workspace settings. |
| Lightspeed eCom (C-Series) (link) | Yes | API access requires a paid eCom shop (Advanced or Professional plan). Merchants self-serve an API key/secret from Settings → Advanced → API in the eCom back office. |
| Lightspeed POS (X-Series) (link) | No | Register a developer account and OAuth app at the Lightspeed Retail (X-Series) developer portal to obtain client credentials and test store access. |
| Lightspeed Restaurant (K-Series) (link) | No | Register an API client on the developer portal. Clients are bound to a single environment (trial or production). |
| Lightspeed Restaurant (O-Series) (link) | No | Create an add-on in Kounta by Lightspeed to get a client ID and secret; Basic access with those credentials reaches your own company for testing. |
| Lightspeed Retail R-Series (link) | No | Apply for developer access; register an OAuth client at https://cloud.lightspeedapp.com/oauth/register.php. Test stores are provided via the partner channel. |
| Lime CRM (link) | No | Lime Cloud and on-premise applications each expose REST at /api/v1. Create an API user in LISA and generate an API key. Example interactive docs: http://static.lime-crm.com/crm-api-docs/ |
| LINE (link) | Yes | Create a free LINE Developers account, add a Messaging API channel, and copy the channel access token and channel secret from the console. |
| LinkedIn Talent Hub (link) | No | Access is provisioned by LinkedIn to approved Talent Solutions partners. Complete the LinkedIn Talent Solutions Partner Request Form, sign the API agreement, and LinkedIn provisions a developer application plus a test organization/contract. There is no self-serve sandbox signup. |
| LiteLLM (link) | Yes | Self-host the open-source LiteLLM Proxy (pip or Docker), create a virtual key, and point the connection at the proxy host. |
| Litmos (link) | No | Litmos API access (API key) is enabled per account under Account & Settings > Integrations > Litmos API; a Litmos subscription/trial is required. |
| LivePepper (link) | No | API access is provided to LivePepper store operators. Requests authenticate with HTTP Basic (username/password) against https://posapi.livepepper.com/{store}, where {store} is the store short name. Contact support@livepepper.com for API credentials. |
| LiveSession (link) | Yes | Sign up at livesession.io for a trial account, then create a Personal Access Token under API Tokens with the scopes you need.
|
| LiveVox (link) | No | Request a SmartReach/LiveVox sandbox and API access token from Customer Care. Each tenant is hosted on a region-specific API hostname provided during onboarding — set it as the connection API URL when it differs from the default NA1 host. |
| Lodgify (contact for access) | No | Lodgify does not publish a separate sandbox host; use a trial or test property with a dedicated API key. |
| LogicMelon (link) | No | API credentials (API key, username, password) are issued from your LogicMelon account. Contact support@logicmelon.com for API access and rate-limit changes. |
| Looker Studio (link) | Yes | Looker Studio is free with a Google account. Enable the Looker Studio API in Google Cloud, configure OAuth with datastudio.readonly (or datastudio) scopes, and authorize a Workspace user.
|
| Loop (link) | No | API keys (format lk_live_…) are provisioned manually by a Loop contact; there is no self-serve sandbox signup. Validate a key with GET /v1/ping. |
| Loops (link) | Yes | Sign up for a Loops account, then create an API key under Settings → API in the Loops app. |
| Loox (link) | Yes | Sign up for Loox (free trial available on paid plans), then generate an API secret key under Settings > API Keys in the Loox admin.
|
| LoyaltyLion (link) | No | API keys are created inside a LoyaltyLion merchant account (Manage → API keys). Partners building multi-store apps register an OAuth app by emailing partnersupport@loyaltylion.com. |
| Loyverse (link) | Yes | Create a free Loyverse account and generate a personal access token in Back Office (Settings → Access Tokens), or register an OAuth app in the Loyverse developer portal. |
| Luma (link) | No | The API needs a Luma Plus subscription on the calendar. Create a calendar on luma.com, upgrade it to Luma Plus, then generate an API key. |
| Lumesse TalentLink (link) | No | TalentLink REST access is provisioned by Cegid/Lumesse for API partners. There is no self-serve public sandbox; use the live swagger Authorize flow once you have JWT + API key. |
| Lytics (link) | No | Generate an API access token in a Lytics account to read segments and user entities. |
| Macro (link) | Yes | Create a free Macro account, connect via OAuth when authorizing the integration (browser sign-in). MCP access is included on all plans. |
| Magnetic (link) | No | API access uses a per-user API token from Magnetic Personal Settings. A Magnetic subscription is required. |
| MailBluster (link) | Yes | Sign up for MailBluster, create a brand, then generate an API key under Brand Settings → API Keys. |
| Mailcoach (link) | Yes | Mailcoach Cloud offers hosted accounts at mailcoach.app; self-hosted Mailcoach is also available for private instances. Generate an API token from your account to call the REST API. |
| Maildroppa (link) | Yes | Sign up for a Maildroppa account and create an API key from your user profile. The public API is marked beta; use the hosted OpenAPI reference for supported endpoints. |
| Mailercloud (link) | Yes | Sign up for Mailercloud and create an API key under Account → API Integrations. |
| MailerLite (link) | Yes | Sign up for a MailerLite account and generate an API token under Integrations → MailerLite API. |
| MailerSend (link) | Yes | Sign up for MailerSend and create an API token under API tokens in the dashboard. |
| Mailgun (link) | Yes | Sign up for a Mailgun account to receive a sandbox domain and API key. Sandbox domains can send only to authorized recipients until a custom domain is verified. |
| Mailjet (link) | Yes | Sign up for a free Mailjet account; the API Key and Secret Key are under Account settings → API Key Management. |
| Mailsoftly (link) | Yes | Sign up for Mailsoftly and create an API key from Settings → API Keys to call the REST API. |
| MaintainX (link) | No | API keys are created in-product (Settings → Integrations → API Keys). There is no separate public sandbox host; use a trial or developer organization for testing. |
| Makesure (link) | No | Email makesure@makesure.com.au for API test credentials (Client Key and Client Secret). There is no self-serve developer signup. |
| Mambu (link) | No | Sandbox tenants (https://{tenant}.sandbox.mambu.com) are provisioned by Mambu for customers and partners; there is no self-serve developer signup. |
| ManageEngine MDM (link) | Yes | Cloud: register a Zoho API Console server-based app, use access_type=offline, and authorize MDMOnDemand scopes. On-premises: generate an API key under Admin → API Key Generation. |
| Manatal (link) | Yes | Start a 14-day free trial (no card required), then as an Admin open Administration > Features > Open API, click Generate new token and copy the key.
|
| ManyReach (link) | Yes | ManyReach offers a free trial. API keys are available under Account Settings → API in the ManyReach app. |
| Marketing360 (link) | No | Use an existing Marketing 360 account: log in as the account Owner or an Admin, open Settings > Developers, add a new API key with all Key Access options and copy the Client ID and Client Secret.
|
| Marketo (link) | No | Marketo REST API access requires a Marketo Engage subscription; a Custom Service (Admin > LaunchPoint) provides the Client ID/Secret used for OAuth 2.0 client-credentials auth. |
| Mastodon (link) | Yes | Mastodon has no official sandbox: create an account on any Mastodon server, then register an app with POST /api/v1/apps on that server to get a client ID and secret.
|
| Matrix Synapse (link) | Yes | Synapse is open source: run your own homeserver, create an admin user and request an access token to use the Admin API. |
| Mattermost (link) | Yes | Mattermost is self-hosted: run a server with Docker (or start a free Mattermost Cloud trial), enable personal access tokens in the System Console and create one under Profile → Security. |
| Maverick Payments (link) | No | Sandbox accounts are available on request from Maverick Payments (Developers → API Services in the Dashboard). |
| Max Messenger (link) | Yes | Create a bot with MasterBot inside the Max app to obtain a bot token. The bot must be added to a chat to read or send messages there. |
| Maxio (Chargify) (link) | Yes | Create a Chargify site (subdomain) and use API keys for sandbox testing. |
| MEDITECH (link) | Yes | Register at MEDITECH Greenfield, create a patient-access (SMART standalone launch) app with the Unified redirect URI, and connect with the Greenfield FHIR base URL https://greenfield-apis.meditech.com/v1/uscore/R4 using its test patients. |
| Medplum (link) | Yes | Register a free Medplum account and project at https://app.medplum.com/register, then create a ClientApplication under Project Admin > Clients to get a client ID and secret. Load synthetic data into the project before testing. |
| Medtech ALEX (link) | No | Medtech issues the Client ID/Secret and a UAT facility during ALEX vendor onboarding. Requests must come from a static IP address registered with Medtech (allowlist), for both UAT and Production. |
| MeetGeek (link) | Yes | Sign up at app.meetgeek.ai and generate an API key from Integrations > Public API card. API keys are region-specific (EU/US).
|
| Megaventory (link) | Yes | Sign up for a free Megaventory trial, then generate an API key from your profile (profile icon → key icon → Update). |
| Mem (link) | Yes | Sign up at mem.ai, then create an API key under Settings → API. |
| Mem0 (link) | Yes | Sign up for the Mem0 Platform and create an API key from the dashboard (keys are workspace-scoped). |
| Memberspot (link) | No | Request API access from Memberspot and create an API key in your school admin (Settings → Integrations). The key is sent on every request via the X-API-KEY header against https://api.memberspot.de. |
| MemberVault (link) | No | Use your live MemberVault admin account. Generate the Webhooks API key under Integrations → Other; the account subdomain is the hostname prefix before .mvsite.app or .vipmembervault.com. |
| Membrain (link) | No | API keys are created by a Membrain admin under System Setup. There is no public self-serve developer sandbox; use a customer or partner tenant. |
| Mercado Libre (link) | Yes | Self-serve: register an application in the Mercado Libre Developers portal to get OAuth client credentials; test with a real seller account (no separate sandbox host). |
| Mercado Pago (link) | Yes | Create an application in the Mercado Pago developer panel to obtain OAuth2 credentials and test (sandbox) access tokens. |
| MerchantPro (link) | No | MerchantPro is a hosted ecommerce platform. Create an API user under Settings → API and webhooks with the permissions you need (catalog, orders, customers). API calls are made against your store domain over HTTPS with Basic authentication (API User + API Secret). |
| MeritHub (link) | No | Log in to a MeritHub organization account, open the Admin Console and go to API to get a Client ID and Client Secret. If the API section is missing, contact MeritHub sales.
|
| MerusCase (link) | No | MerusCase API access requires registering a third-party app with MerusCase; there is no public self-serve sandbox documented. |
| Meta Muse (link) | Yes | Sign up for the Meta Model API (US developers, public preview), generate a one-click API Key in the console, and point an OpenAI-compatible client at https://api.meta.ai/v1 to call the Muse Spark chat models. |
| Metabase (link) | Yes | Start a 14-day Metabase Cloud trial or self-host the free Open Source edition, then create an API key in Admin > Settings > Authentication > API keys. |
| Method (link) | Yes | Method offers a free trial with full REST API access; generate an API Key under Integrations → API (Admin only). OAuth2 requires registering the redirect URI with Method by emailing api@method.me (subject "REST API | OAuth2 Client Request"). |
| Metriport (link) | No | Create an account on the Metriport Developer Dashboard (https://dash.metriport.com) and request Medical API access. Once approved, toggle Sandbox mode in the dashboard and generate a sandbox API key on the Developers page. The sandbox (https://api.sandbox.metriport.com) returns example de-identified clinical data for pre-defined test patients (e.g. first name Jane, Chris, Ollie, Andreas or Kyla). |
| Metronome (link) | No | Metronome accounts are provisioned by Metronome. Request a sandbox environment from the Metronome team. |
| Mews (link) | No | Mews provides a demo environment (api.mews-demo.com) alongside production; both the Client Token (partner registration) and an Access Token (per property) must be requested from Mews.
|
| Mews POS (link) | Yes | Mews publishes a shared Demo environment (https://api.mews-demo.com/pos) with a demo API token and Mews POS web / Android app logins on its Environments page; production keys come from Mews.
|
| MicroBilt (link) | Yes | Register for a free MicroBilt Developer Portal account for instant sandbox access, then create an API key under My API Keys to try APIs.
|
| Microsoft Active Directory / Entra ID (link) | No | |
| Microsoft Advertising (link) | No | |
| Microsoft Clarity (link) | Yes | Clarity is free. Sign in with a Microsoft, Google, or Facebook account, create a project, then generate a Data Export API token under Settings → Data Export (project admin only).
|
| Microsoft Dynamics 365 Finance and Operations (link) | No | Register an app in Microsoft Entra ID and add its client id under System administration → Setup → Microsoft Entra applications in the F&O environment. A Finance and Operations environment (e.g. via Lifecycle Services) is required to authorize and test the OData endpoints. |
| Microsoft Dynamics GP (link) | No | No hosted sandbox. Web Services for Microsoft Dynamics GP is installed on-premises alongside a GP deployment; the sample "Fabrikam" company (Company Id -1) is used for testing against a partner/demo GP instance.
|
| Microsoft Exchange (on-prem) (link) | No | No hosted sandbox. Exchange Server is installed on-premises; test against a lab or partner Exchange Server mailbox.
|
| Microsoft Foundry (link) | Yes | Create an Azure subscription, deploy a Microsoft Foundry resource, deploy at least one model, then copy the resource key and resource name from Keys and Endpoint. |
| Microsoft Power BI (link) | Yes | A Power BI tenant (any Microsoft 365 tenant with Power BI enabled) plus a Microsoft Entra app registration with the "Power BI Service" delegated permission Workspace.Read.All is required (plus Tenant.Read.All, used by a Fabric administrator, for analytics_event). A free Microsoft 365 Developer Program tenant can be used for testing. |
| Microsoft Viva Engage (link) | Yes | Join the Microsoft 365 Developer Program for a free sandbox tenant, then register an app in Entra ID (Azure portal) with the Community and User Graph permissions. |
| MightyCall (link) | Yes | Sign up for a MightyCall account and enable API access under Integrations → API (Manager/Admin). |
| Mihu AI (link) | No | Create a Mihu AI workspace and generate an API token in the Developer section. |
| Mijn Bureau (link) | Yes | Mijn Bureau is self-hosted. Use the Bureaublad compose stack locally (bureaublad.localhost) or your ministry deployment. Register an OAuth client in Keycloak with token-exchange enabled and supply the La Suite Drive/Docs base URLs from your helm values. |
| Mindbaz (link) | No | Mindbaz has no self-serve sandbox; request an account and API key from Mindbaz. |
| Mindbody (link) | No | Mindbody API access requires a developer account and approved API key. Contact Mindbody API Support to register OAuth clients and obtain sandbox site credentials. |
| MiniMax (link) | Yes | Register on the MiniMax API Platform and create a secret key under API Keys, then top up the pay-as-you-go balance to make calls.
|
| miniOrange (link) | Yes | Self-serve 30-day free IAM/SSO trial (no credit card). Sign up, add a SAML app with miniOrange as the IdP, then copy the IdP SSO URL, entity ID and X.509 certificate into the workspace integration.
|
| Minox (link) | No | Register an OAuth2 application with Minox to obtain a client id/secret, then authorize against a real Minox administration — the spec documents no separate sandbox/trial environment. |
| Missive (link) | Yes | Start a Missive trial on the Productive plan and create an API token under Preferences → API. |
| MistralAI (link) | Yes | Create a Mistral account, activate Studio in Free mode (no credit card required) and generate an API key from the API Keys section of the console.
|
| Mixedbread (link) | Yes | Sign up at Mixedbread, create an API key in the platform, and call the /v1 endpoints with it as a Bearer token. |
| Mixmax (link) | No | Email developer@mixmax.com for a trial sandbox account, or use your Mixmax workspace API token from Settings → Integrations → API. |
| Mixpost (link) | Yes | Install Mixpost Lite (free, self-hosted) or start a Mixpost Cloud trial, then create a personal key under the user menu → API. |
| Mobilia (link) | No | API credentials (client ID and secret) are issued from a Mobilia agency account; there is no public sandbox. |
| Mocean (link) | Yes | Sign up for a Mocean account and copy the API Key and API Secret from the dashboard. |
| MOCO (link) | Yes | Start a free 30-day MOCO trial (no payment details required), then copy your personal API key from Profile > Integrations or create an account API key under Settings > Extensions > API & Webhooks.
|
| ModelRunner (link) | Yes | Sign up for a ModelRunner account and create an API key under Profile → Keys; calls draw on a prepaid credit balance. |
| ModelRush (link) | Yes | Sign up at modelrush.ai, create an API key, and call the OpenAI-compatible /v1 endpoints (GET /v1/models needs no key). |
| ModMed (link) | No | Request developer tools from ModMed (synapSYS developer program). ModMed provisions a generic sandbox firm with vendor credentials; use the "Generic Sandbox" region with the firm URL prefix from the welcome email. Production keys are issued after a demo and technical review. |
| MoEngage (link) | No | Sign up for a MoEngage workspace to obtain a Workspace ID and API keys under Settings > Account > APIs. |
| Moka (link) | No | Moka does not publish a self-serve sandbox. API keys are issued per organization by your Moka Customer Success Manager (CSM). |
| Mollie (link) | Yes | Self-serve: sign up at mollie.com and create a website profile. Use its Test API key, or register an OAuth app under More → Developers → Your apps. Test mode has no separate sandbox host. |
| Moloni (link) | Yes | Create a Moloni account and a developer account (https://www.moloni.pt/dev/criar-uma-conta/) to get a client id and secret; Moloni documents a sandbox for API testing. |
| MoltSets (link) | Yes | Sign up for free at app.moltsets.com (closed beta), then create an API key under Dashboard → API Keys. |
| MONEI (link) | Yes | Sign up at dashboard.monei.com, switch the dashboard to test mode and create a test API key (pk_test_…) under Settings → API access. |
| Moneris (link) | Yes | Self-serve: register at the Moneris Developer Portal (https://developer.moneris.com), create a Client Credential application, and use the Test Merchant ID plus Client ID/Secret from Access & Credentials. Sandbox host: https://api.sb.moneris.io. |
| Moneybird (link) | Yes | Self-serve: register an OAuth application at moneybird.com/user/applications to get client credentials; developers test against their own Moneybird administration. |
| MongoDB (link) | Yes | MongoDB Atlas Free Tier clusters - which are also known as M0 Sandboxes - are limited to only 512MB of storage but it is more than enough for a pet project |
| MongoDB Database (link) | Yes | Create a free-tier (M0) MongoDB Atlas cluster, add a database user, and copy the cluster connection string. |
| Monster (link) | No | Monster issues Real Time Posting credentials through a Monster representative. The developer guide publishes a shared demo account for posting to the demo boards; production posting requires the customer account plus purchased job inventory.
|
| Moodle (link) | Yes | Moodle is open source and self-hosted. Spin up a local/demo site (e.g. the Docker images at github.com/moodlehq/moodle-docker or the MoodleCloud trial), then enable REST web services and issue a token under Site administration > Server > Web services. |
| MoonClerk (link) | Yes | MoonClerk accounts include API access on every plan. Create an account, connect Stripe, and generate an API key under Settings → API Key. |
| Moosend (link) | Yes | Sign up for a Moosend account, then copy an API key from Account → API key in the Moosend UI. |
| Moov (link) | Yes | Moov test mode is available from a free Moov Dashboard account; test mode has its own API keys. |
| MotherDuck (link) | Yes | Sign up at motherduck.com, create an organization, and generate an access token in Settings → Access Tokens. Free trial / community tiers are self-serve. |
| Motion (link) | Yes | Start a Motion free trial, then open Settings > Integrations > API in the app to create an API key (shown only once).
|
| Mouseflow (link) | Yes | Mouseflow offers a free plan. Sign up at mouseflow.com, then create an API key under API Keys in your account. |
| MoxiWorks (link) | No | Contact MoxiWorks (api@moxiworks.com or your Platform rep) to get an API Identifier and Secret pair; a QA environment exists at api-qa.moxiworks.com.
|
| mParticle (link) | No | Request API credentials from your mParticle account; a workspace is required to resolve profiles. |
| MplusKASSA (link) | No | API access requires MplusKASSA Partner registration (apply via https://developers.mpluskassa.nl/ or contact dev@mpluskassa.nl). Each customer has a dedicated API server (URL + port) authenticated with an ident/secret credential pair. |
| MRPeasy (link) | No | Start an MRPeasy trial or account on the Unlimited plan (the API is only available there), then create an API key and secret under Settings » Integration » API access. |
| MSG91 (link) | Yes | Create an MSG91 account and generate an Authkey from the control panel (Authkey menu). |
| Multiplier (link) | No | Multiplier API access is partner-gated: request Client ID / Client Secret from your Multiplier account manager. The production host (https://api.usemultiplier.com) also serves as the partner sandbox. |
| My Hours (link) | Yes | Start a My Hours trial of a paid plan, then create an API key in Settings → Integrations → API keys. |
| MyCase (link) | No | MyCase issues OAuth client credentials and registers redirect URIs through MyCase support for firms with API access. |
| MyCashflow (link) | No | Create a MyCashflow store on the Advanced, Pro or Enterprise plan, install the API extension (Account » Extensions) and create an API user. Use the API user name, password and your store name to connect. |
| MyFatoorah (link) | Yes | MyFatoorah publishes a demo account and test token for https://apitest.myfatoorah.com; use the Test (Sandbox) API URL when connecting. |
| MYOB (link) | No |
|
| Mysolution (link) | No | Mysolution is a managed package on Salesforce; testing requires a Salesforce org (or sandbox) with the Mysolution Recruitment package installed. |
| MyUnisoft (link) | No | No public self-serve sandbox. New partners send branding/contact details to the MyUnisoft team, who provide the X-Third-Party-Secret plus a dedicated test cabinet/schema for integration testing (see docs/documentation.md).
|
| NeetoForm (link) | Yes | Sign up for a NeetoForm workspace, generate a General API key under Admin → API keys, and use your workspace subdomain in the connection URL. |
| Neo4j (link) | Yes | AuraDB Free tier instances can be created in the Aura Console for development and testing. |
| Neon (link) | Yes | Neon offers a free tier with serverless Postgres projects for development. |
| Nethris (link) | No | Register on the Nethris Gravitee developer portal, subscribe to the published HC APIs, and request sandbox business data. SandboxData uses a separate X-Gravitee-Api-Key plan and is not used by this integration. |
| NetHunt CRM (link) | Yes | Sign up at nethunt.com and generate an API token under workspace integrations settings. |
| Netlify (link) | Yes | Sign up for a free Netlify account, then create a personal access token under User settings > Applications, or register an OAuth application for the client key and secret.
|
| Netsmart (link) | Yes | Sign up on the Non-Production Developer Portal (https://fhirtest.netsmartcloud.com/developers), create a patient-facing application with the Unified redirect URI, and request authorization for the myAvatar sandbox tenant d6c40265-c5c6-494f-b1aa-a27bf9a8c3f1 (approval takes 3-5 business days). Set the workspace API URL to https://fhirtest.netsmartcloud.com/provider/patient-access/v2/{domain} and use that tenant ID. Synthetic data only. |
| NetSuite (link) | No | Must have existing account |
| New Relic (link) | No | SCIM provisioning needs a New Relic organization on a paid Pro or Enterprise edition; then create an authentication domain with SCIM as the user source and copy the token shown.
|
| Newbook (link) | No | Register for a Newbook developer account at developers.newbook.cloud, then ask Newbook Support for REST API credentials. A test endpoint (testapi.newbook.cloud, region "staging") is available on request; access is not automatic. |
| Newegg (link) | No | Newegg Marketplace API access is not self-serve. Integration partners complete Partner Registration by contacting the Newegg Marketplace Integration Team (datafeeds@newegg.com); the developer-level API Key is paired with the Seller ID and Secret Key issued to the seller. |
| Nextcloud (link) | Yes | Nextcloud is self-hosted: run a server (e.g. the official Docker image), sign in as the admin and create an app password under Personal settings → Security. |
| NextGen Healthcare (link) | No | Join the NextGen API developer program, register a patient-access (SMART standalone launch) app with the Unified redirect URI, and request sandbox test patient credentials. |
| Nextiva (link) | No | Requires a Nextiva Contact Center account and a user with API access enabled; there is no documented self-serve sandbox. |
| NICE CXone (link) | No | Register a back-end application with NICE (typically 2–3 business days). Create a CXone API user without a login authenticator and generate an Access Key ID/Secret from that user’s Security tab. |
| Nimble (link) | Yes | Start a 14-day Nimble trial (no credit card), then generate an API key as an account administrator or register an OAuth app via the Nimble API access page.
|
| NinjaOne (link) | Yes | Sign up for a NinjaOne free trial, then register an API application (Administration → Apps → API) to obtain OAuth client credentials for the authorization-code flow. |
| Ninox (link) | Yes | Ninox trial workspace; generate a workspace API key under API & integrations for development. |
| NocoDB (link) | Yes | Sign up for NocoDB Cloud or run a self-hosted instance; create an API token under Account settings. |
| noCRM.io (link) | Yes | noCRM.io offers a trial; API access (Expert or Dream edition) requires an API key from Admin Panel → API Keys. See https://help.nocrm.io/en/articles/40-direct-integrations-with-api |
| Noon (link) | No | Sandbox access is granted through the Noon Partners program; FBPI provides a sandbox-order create endpoint for integration testing. |
| noon payments (link) | Yes | Sign up for a merchant account and use test-mode application credentials against the https://api-test.noonpayments.com base URL. |
| Novu (link) | Yes | Sign up for a free Novu Cloud account; the Development environment and its secret key are created automatically. |
| NOWPayments (link) | Yes | Sign up for a free NOWPayments sandbox account at account-sandbox.nowpayments.io and generate an API key; sandbox calls go to api-sandbox.nowpayments.io. |
| Nozbe Teams (link) | No | Create an API token under Settings → API tokens in the Nozbe Teams app. |
| Numier (link) | No | Numier issues API keys per customer account; contact Numier (info@numier.com) to request API access and credentials. |
| Nutshell (link) | Yes | Create a Nutshell account, then generate an API key under Setup > API keys. Nutshell documents a developer sandbox on the authentication page of their API docs. |
| O*NET (link) | Yes | Free O*NET Web Services API key via self-service signup; the same key works for all Online endpoints. |
| Ocean.io (link) | Yes | Sign up at ocean.io for API access. Credits are consumed per enrichment result; see the Credits section in the Ocean.io API docs. |
| Octopus (link) | Yes | Self-service: on octopus.be, click "Probeer gratis" and fill in the pop-up as a developer/integrator requesting webservice integration access to receive a demo dossier (account + password). https://login.octopus.be/manual/NL/api_requestdevelopmentdossier.htm |
| Octorate (link) | No | Octorate sandbox access and OAuth client credentials are issued by Octorate on request. |
| ODK Central (link) | Yes | ODK Central is self-hosted: install it with Docker, create a Web User and a project, then upload a form. |
| Officient (link) | No | Request a sandbox account from Exact Officient (OfficientProduct@exact.com), then create a client app under your avatar → Developers. Apps can connect to your own account immediately; connecting other accounts requires Officient to verify the app. |
| OKSign (link) | Yes | Create a free OKSign account to obtain REST API credentials under REST API → API Console. Free accounts can send up to 20 API emails for testing. |
| Okta (link) | No | |
| Oleeo (link) | No | Oleeo provides a default "developer-portal-base" sandpit system and per-customer config environments. Credentials are issued per customer by your Oleeo contact. |
| Ollama (link) | Yes | Install Ollama from ollama.com, run `ollama serve` (or the desktop app), pull a model with `ollama pull llama3.2`, and point the connection at localhost:11434. |
| Ometria (link) | No | Ometria documents no sandbox or free trial; book a demo to get an Ometria account, then generate an API key in that account for the Data API (X-Ometria-Auth header). |
| Omise (link) | Yes | Sign up for a free Omise account; test mode is available immediately with the skey_test_ secret key from Settings → Keys. |
| Omnisend (link) | Yes | Create a free Omnisend account and generate an API key under Store settings → API keys. The 2026-03-15 API uses the same production host. |
| ON24 (link) | No | ON24 has no self-serve sandbox. API tokens are created by an administrator of an existing ON24 customer account. |
| OnceHub (link) | No | OnceHub API keys are created in the account under APIs & Webhooks; use Booking Calendars API at api.oncehub.com/v2. |
| OneDesk (link) | No | OneDesk offers a free trial; API keys are created in-product under Admin → Integrations → API (account owner). |
| Oneflow (link) | Yes | Create a Oneflow account and generate an API token under Marketplace → API tokens; the same token works for testing. |
| OneSignal (link) | Yes | Sign up for a free OneSignal account to create an app, generate an App API Key, and obtain your App ID. |
| OneSpan (link) | Yes | Free OneSpan Sign developer sandbox (sandbox.esignlive.com). Sign up, then copy the account API Key from Admin > Integration. |
| OneUp (link) | Yes | Sign up for a OneUp account and generate an API email/key pair under Settings > API settings to test against your own company data. |
| OneUp Social (link) | Yes | Sign up for a OneUp account and generate an API key from the API Access page to test scheduling against your connected social accounts. |
| Onfido (link) | No | Generate a sandbox API token in the Onfido Dashboard (Developers → API authentication → Tokens). Every live endpoint can be called in the sandbox, which returns results with the same response structure. Dashboard access comes from Onfido (Entrust) sales. |
| Onit (contact for access) | No | Request a SimpleLegal / Onit sandbox tenant and API token from your account team (see the Unity API Toolkit). |
| ONLYOFFICE DocSpace (link) | Yes | Register a free DocSpace cloud portal at onlyoffice.com, then create OAuth credentials or an API key under Developer Tools in the portal settings. |
| OnlySocial (link) | Yes | Sign up at onlysocial.io, create an access token under Access Tokens, and copy your workspace UUID from the API base path. |
| OnSched (link) | Yes | OnSched has a separate staging environment (api-stage.onsched.com). Create a staging company in the v3 dashboard and generate a client ID and secret for it. |
| Ontra (link) | No | Sandbox supports OAuth client credentials without mTLS; create an API client in the Ontra sandbox admin. |
| Ontraport (link) | No | Apply for an Ontraport sandbox account (https://ontraport.com/tools/sandbox), then request an API key and App ID in its Administration settings. |
| Open Dental (link) | No | Open Dental publishes test credentials on the API setup page for limited remote testing. Production use requires a developer key, customer API key, and an eConnector at the practice. |
| OpenAI (link) | Yes | API keys are self-serve from the OpenAI platform. The Agents API is in public beta; OpenAI-hosted sandboxes are billed at container rates. |
| OpenAI Ads (link) | Yes | Create an ad account at ads.openai.com, then issue an Advertiser API key from the Settings page in Ads Manager. No separate sandbox is documented. |
| opencode (link) | Yes | opencode is open source and free to run: `npm i -g opencode-ai` then `OPENCODE_SERVER_PASSWORD=... opencode serve` gives a private test server with no vendor signup. |
| OpenRouter (link) | Yes | Sign up for an OpenRouter account and create an API key in the dashboard to call the models catalog and chat completions APIs. |
| OpenSanctions (link) | No | API keys are issued by OpenSanctions from the API product page (free for qualifying non-commercial users); there is no separate sandbox environment. |
| OpenSesame (link) | No | Delivery API access and a Customer Integration ID are provisioned by OpenSesame (Implementation Specialist / support@opensesame.com). Not self-serve. |
| OpenTable (link) | No | |
| Opsgenie (link) | No | Atlassian has ended new Opsgenie sales, so new sign-ups are no longer offered; testing needs an existing Opsgenie account. Create an API integration under Settings → Integrations and use its API key. |
| Oracle Fusion ERP (link) | No | Oracle Fusion Cloud ERP test environments require a paying customer subscription; access to a pod is granted within your organization. |
| Oracle HCM (link) | No |
|
| Oracle Health (link) | Yes | Register a SMART app (patient persona) in the Oracle Health developer Code Console with the Unified redirect URI, then connect with the public sandbox tenant ID ec2458f2-1e24-41c8-b71b-0e701af7583d. |
| Oracle JD Edwards EnterpriseOne (link) | No | JD Edwards EnterpriseOne is customer-hosted (on-premises or cloud IaaS); there is no public developer sandbox. Access requires a running JD Edwards EnterpriseOne 9.2 environment with the AIS Server (Application Interface Services) configured and a user granted access to the AIS REST services. |
| Oracle OPERA Cloud PMS (link) | No | OPERA Cloud test/sandbox properties and OHIP application registration (Client ID/Secret, x-app-key) are provisioned by Oracle for paying customers and registered partners; there is no public self-service signup. |
| Oracle Sales (link) | No | Oracle CX Sales test environments require a paying customer subscription; access to a pod is granted within your organization. |
| Oracle Simphony (link) | No | There is no public sandbox. STS Gen2 is provisioned by Oracle for a Simphony Cloud enterprise; an enterprise administrator creates the Simphony Transaction Services API account in Reporting and Analytics API Account Management. |
| Oracle Taleo Business Edition (link) | No | TBE REST API access requires a Premium-service-level Taleo Business Edition account and a System Administrator user. Sandbox/developer access is arranged with Oracle; there is no self-serve developer signup. |
| Oracle Utilities Customer Care and Billing (link) | No | Oracle Utilities Customer Care and Billing environments require a paying customer subscription; access to a cloud instance is granted within your organization. |
| Oracle Utilities Customer Cloud Service (link) | No | Oracle Utilities Customer Cloud Service environments require a paying customer subscription; access to a cloud instance is granted within your organization. |
| Order Desk (link) | Yes | Sign up for an Order Desk store and create API credentials under Store Settings → API. |
| Order Time (link) | No | Order Time offers sandbox accounts for testing; the Master Admin creates the API key under Admin > Rest API. |
| OrderLord (link) | No | OrderLord provides a staging API host, but credentials and production activation require support approval.
|
| Orion Health (link) | No | Orion Health issues API credentials and sandbox access through partner onboarding (per-customer HIE deployments). Register an application at https://developer.orionhealth.io to obtain a client ID and secret. |
| OTTO Market (link) | Yes | OTTO Market provides a parallel sandbox environment (sandbox.api.otto.market) with its own OPC credentials for integration testing. |
| Outbrain (link) | No | Amplify API access is partner/beta gated. Register at https://www.outbrain.com/partner-api/ then generate an OB-TOKEN-V1 token. |
| Outline (link) | Yes | Start an Outline Cloud trial or deploy self-hosted Outline, then create an API key under Settings → API & Apps with read/write scopes for collections, documents, and comments. |
| Outplay (link) | No | Generate API credentials from User settings → Company settings → Integrations & API in your Outplay account. A dedicated developer sandbox is not documented publicly. |
| Outseta (link) | Yes | Outseta offers a self-serve free trial; API keys are generated from the trial account under Settings → Integrations → API Keys. |
| Overloop (link) | Yes | Sign up for an Overloop account and generate an API Key from Settings > Integrations > API — no separate developer/sandbox program is documented. |
| OVHcloud (link) | Yes | Create a service account in the Control Panel, or register an API application at the createApp page. Use the matching regional API host (EU, CA, or US). |
| OwnerRez (link) | Yes | OwnerRez has a self-serve stage environment (https://appstage.ownerrez.com/join) with a Sandbox messaging channel and Stripe test cards. Create an OAuth app under Settings > Advanced Tools > Developer/API Settings and click "Grant Access To Me" to test against your own account; self-use also unlocks reviews, listings and messaging without a premium. |
| Oyster HR (link) | No | Request a developer sandbox (seeded data) at https://sandbox.oysterhr.com/request_account; it uses api-sandbox.oysterhr.com. |
| Paddle (link) | No | |
| PagerDuty (link) | Yes | PagerDuty offers a free trial account. Create a General Access REST API Key under your user profile to call https://api.pagerduty.com. |
| PageUp (link) | No | Contact your PageUp representative for UAT environment credentials. |
| PandaDoc (link) | Yes | Create a free PandaDoc developer sandbox account. |
| PAR Brink POS (link) | No | Brink API access (server subdomain, Access Token and per-location Location Token) is provisioned by PAR API Support (api.support@partech.com). |
| Parma (link) | No | |
| Particle Health (link) | No | Particle runs a Sandbox (https://sandbox.particlehealth.com) with synthetic test patients and every production API; it is limited to 500 queries per organization per day. Credentials come from your Particle Health representative. |
| Paycor (link) | No | |
| Payfactory (link) | No | Sandbox / developer API access is provided through Payfactory’s developer portal on request. |
| PayHere (link) | Yes | Create a separate PayHere sandbox account at sandbox.payhere.lk, then generate API Keys under Settings for OAuth access to merchant APIs. |
| Payhip (link) | Yes | Create a Payhip seller account and generate an API key under Settings → Developer. The public REST API currently supports coupons; license-key endpoints use a per-product secret key and are not connection-scoped here. |
| Paylocity (link) | No | Submit access request to receive OAuth credentials and sandbox account.
|
| Paylocity Assessment (link) | No | Sign the Paylocity technology-partnership agreement to receive a Client ID and Client Secret. Use the demo gateway (dc1demogwext) with testMode for mocked testing.
|
| Paylocity Recruiting (link) | No | |
| Paypal (link) | Yes | Create account on developer portal to access virtual sandbox accounts. |
| Payspace (link) | No | Payspace (Deel Local Payroll) exposes a test environment (web: test.payspace.com, api: apistaging.payspace.com, identity: staging-identity.yourhcm.com). Test API credentials are generated the same way as production, by logging into test.payspace.com and going to Config > Basic Settings > General Company > Integrations > API Credentials. |
| Paystack (link) | Yes | Create a free Paystack account and use test API keys from Settings → API Keys & Webhooks. |
| PayTabs (link) | No | PayTabs issues a Test (sandbox) profile alongside the live profile once a merchant account is approved. Request a merchant account from PayTabs, then use the Test profile Server Key + Profile ID against the account's regional endpoint. Test profiles are not self-serve — they are provisioned by PayTabs. |
| Paytm (link) | No | The Settlement APIs are production-only (no staging environment). A live Paytm Business account issues the MID, Client ID and Client Secret used to authenticate; obtain settlement API access from Paytm and generate credentials on the Paytm Business dashboard. |
| PCRecruiter (link) | No | Admin account needs to sign up and then choose from free or enterprise versions of the sandbox required. |
| PCRecruiter (On-prem) (link) | No | Admin account needs to sign up and then choose from free or enterprise versions of the sandbox required. |
| Pendo (link) | No | API access depends on your Pendo subscription. Contact your Pendo admin or representative to confirm access and create an integration key. |
| Pennylane (contact for access) | No | Please send a request to partnerships@pennylane.com with your full name & mail address to use for the sandbox creation. |
| People First (link) | No | A People First administrator generates an inbound-integration access token in-app (Administration > Settings > Inbound Integration). Non-production environments are addressed via the environment code in the tenant subdomain. |
| Peoplebox (link) | No | Peoplebox API access requires a Peoplebox account and an API token; request access from Peoplebox. |
| PeopleForce (contact for access) | No | |
| PeopleHR (link) | No | Contact customerservices@peoplehr.com to set up a sandbox account for testing. |
| Pera (link) | No | Contact sales@getpera.com to set up an account. API keys are created per user role and used as Bearer tokens. |
| Perforce Helix Swarm (link) | Yes | Helix Swarm is a free companion app to Helix Core. Install Helix Core (free for up to 5 users) and Helix Swarm, then create a login ticket with `p4 login -p` to test the REST API. |
| Permutive (link) | No | Create a private API key in the Permutive Dashboard to read cohorts. |
| Perplexity AI (link) | Yes | Sign up for a Perplexity account and create an API key in the API Console to call the Router chat completions and models APIs. |
| PersistIQ (link) | Yes | PersistIQ offers a free trial; generate the company API key from Settings → Integrations after signup. |
| Persona (link) | No | Persona provides sandbox inquiries for integration testing; inquiry templates are only exposed via the API with production keys. |
| Personio (link) | No | |
| Phenom (contact for access) | No | Premium users have access to sandboxes. |
| Phraseanet (link) | Yes | Self-host the free open-source (GPL v3) edition with Docker and sign in with the admin account from its .env file, then click your login → Developer → Create a new application (web application, with your callback URL) to get a client ID and secret.
|
| PicPay (link) | No | PicPay issues merchant API tokens to onboarded merchants; there is no separate sandbox host documented in the OpenAPI. |
| Picqer (link) | Yes | Picqer offers a free self-service trial account. Create an API key under Settings → API keys to access the REST API. |
| Pike13 (link) | No | Register an application with Pike13 (https://developer.pike13.com/docs/get_started) to obtain a Client ID and Client Secret. API access requires the Pike13 Premium plan on the business.
|
| Pims (link) | Yes | Pims documents a public demo domain (demo.pims.io) with sandbox data and shared demo credentials listed in its API docs. Credentials for a real customer domain are issued by Pims on request, with that customer's agreement.
|
| Pinpoint (link) | No | Email integrations@pinpointhq.com with your use case; Pinpoint creates a sandbox account if you do not have one. API keys are then created in Settings > API & Webhooks.
|
| Pinterest (link) | No | Register an app in the Pinterest developer portal and wait for Pinterest to approve it for Trial access, then generate a Sandbox access token from the app Configure tab (or via OAuth on api-sandbox.pinterest.com).
|
| Pipedrive (link) | No | Sign up for a developer sandbox |
| Pipeline CRM (link) | Yes | Sign up for Pipeline CRM, have an admin enable API access under Settings → API, then create a bearer API token from My Profile → API tokens. |
| Pipl (link) | No | Pipl access is account-based and sales-led: request a demo at pipl.com, then choose an API key on the API Keys page of your account. The docs demo page lets you try a few calls, and queries containing clark.kent@example.com are not charged. |
| Pivotal Tracker (link) | Yes | Sign up for a free Pivotal Tracker account and create an API token from your profile. There is no separate vendor sandbox; use a dedicated project. |
| Piwik PRO (link) | Yes | Piwik PRO offers a free trial. Create an account, add a website, then create an API key under Profile → API keys. |
| Plaid (link) | Yes | Free self-serve sandbox. Sign up at https://dashboard.plaid.com/signup to get a client_id and Sandbox secret; create test Items with /sandbox/public_token/create (or Plaid Link in Sandbox mode) to obtain an access_token. Production access requires requesting it in the Plaid Dashboard. |
| Plain (link) | No | Plain API access requires a workspace machine user and API key; there is no public self-serve sandbox API tenant. |
| Planday (link) | No | Product partners get a Planday demo portal from Planday API support (apisupport@planday.com) and create an API application under Settings > Integrations > API Access. |
| Plane (link) | Yes | Sign up for a free Plane Cloud workspace at app.plane.so, then generate a Personal API Key under Profile Settings → Personal Access Tokens. |
| Planhat (link) | No | Planhat provides API access to customers; a Private App API token is created from the Planhat app settings. |
| Planka (link) | Yes | Planka is self-hosted: run an instance with Docker and create a user to request an access token. |
| Planly (link) | Yes | Sign up at app.planly.com and create an API key from Settings → Security to call the API. |
| PlanSource (link) | No | Ask your PlanSource point of contact for an API user (lookup code, user key, and administrator username) and Partner-Dev access at partner-dev-api.plansource.com. |
| Planyo (link) | Yes | Planyo offers a trial site; API keys are available from Settings → API once you have a Planyo account. Use the REST playground linked from each method in the API docs. |
| Plausible Analytics (link) | Yes | Plausible offers a 30-day trial. Create an account, add a site, then generate a Stats API key under Account settings → API Keys for the team that owns the site.
|
| Pleo (link) | No | Pleo provides a staging environment (external.staging.pleo.io) to partners in its Early Access Programme; standalone API keys must be enabled by Pleo. |
| Plezi (link) | No | A Plezi account with API access is required; request the API key and tenant company name from Plezi. |
| Plivo (link) | Yes | Create a Plivo account and copy Auth ID and Auth Token from the console API Credentials page. |
| Pluralsight (link) | No | Pluralsight Skills GraphQL uses a plan API key. There is no separate public sandbox host; generate a key in the Developer Portal against a Professional or Enterprise plan. |
| PlusVibe (link) | No | PlusVibe API access requires a Business plan. Sign up at plusvibe.ai, upgrade the workspace to the Business plan, then copy the API key from Settings → API Access. |
| Pneumatic (link) | Yes | Sign up for a Pneumatic account and generate an API key from the Integrations page. |
| PointClickCare (link) | No | Apply for a PointClickCare partnership, create a USCDI Connector Developer Portal account (2-factor authentication is required), and register a Development app to get the Client ID and Secret and access to the shared FHIR Sandbox (My Sandboxes). The app needs a client certificate whose Common Name is registered with PointClickCare. |
| POLi (link) | Yes | Submit the POLi developer test account form to get permanent UAT credentials (Access Code and Auth Code); the UAT API at poliapi.uat3.paywithpoli.com is separate from production.
|
| Polinode (link) | No | Polinode API access (including the employee endpoints) is limited to Enterprise and Partner plans; contact Polinode to obtain API keys. |
| Polymer (link) | No | The Customer API is in beta. Admin users can create an API key from Polymer settings after the feature is enabled for the organization. |
| Popina (link) | No | The Pragma API is in private beta; contact Popina/Pragma to request an API key. A staging environment (https://api-staging.pragma-project.dev) is available for testing. |
| Postal (link) | Yes | Postal is self-hosted: install it from the official documentation, create a mail server and add an API credential to it. |
| Postiz (link) | Yes | Postiz Cloud offers a trial; API keys are under Settings → Developers. OAuth apps are created under Settings → Developers → Apps. |
| Postmark (link) | Yes | Use Postmark server sandbox mode or the POSTMARK_API_TEST server token for non-delivering API tests. |
| Postpone (link) | Yes | Sign up at postpone.app and create an API key under Settings → Integrations → Postpone API. |
| Postproxy (link) | Yes | Sign up at app.postproxy.dev, connect a social profile, then create an API key under Settings → API Keys. |
| PowerOffice (link) | No | Register for API access via the PowerOffice Go developer portal to obtain an Application Key; a Client Key is generated per PowerOffice Go client (company). |
| PracticePanther (link) | No | PracticePanther grants API access (OAuth client credentials) on request. |
| Prefinery (link) | No | Create a Prefinery account (free trial), then generate an API key under Settings → Company Settings → API Keys. |
| PrestaShop (link) | Yes | Self-hosted: install PrestaShop (or use a demo store), then enable the Webservice under Advanced Parameters → Webservice and create an API key with read access to the Products, Categories, Combinations, Stock Availables, Employees, Taxes, Customers, Order Invoices and Orders resources. Authenticate with HTTP Basic (API key as username, empty password). |
| pretix (link) | Yes | Create a free pretix account, create an organizer and a team, then add an API token to the team. |
| Prevail (link) | No | Prevail API access is issued per law firm. Use the firm’s API credential pair (Client ID and Client Secret) against https://portal.prevail.net/api; contact Prevail for sandbox or developer access. |
| Printful (link) | Yes | Create a free Printful account and a manual-order store, then generate a private token in the Developer Portal (Tokens). Orders left as drafts are never fulfilled or charged. |
| Printify (link) | Yes | Sign up for a Printify account and create a Personal Access Token under Connections → Printify API to call the REST API against your shops. |
| PrismHR (link) | Yes | |
| Prismic (link) | Yes | Create a free Prismic repository, then generate a write token under Settings → API & Security → Write APIs. |
| ProAbono (link) | No | Sign up for a ProAbono account and retrieve API keys from the back office Integration section. |
| Procore (link) | Yes | Procore provides a developer sandbox through the developer portal after registering an OAuth application. |
| Procountor (link) | No | Register as a developer at dev.procountor.com to be provisioned a private testing environment (pts-api.procountor.com / pts-secure.procountor.com) with credentials and an OAuth2 client. Access tokens live 1 hour; refresh tokens 6 months. The public testing server is rate-limited to 90 requests/minute. |
| Productboard (link) | Yes | Start a free 15-day Productboard trial, then create a Public API access token under Settings → Integrations → Public APIs → Access Token.
|
| Productive (link) | Yes | Start a free Productive trial, then generate an API token under Settings → API integrations. |
| Productlane (link) | Yes | Sign up for Productlane, then create a v2 API key under Settings → Integrations → API. |
| Proliant (link) | No | Request sandbox credentials from your Proliant Account Manager after completing the API Request form. Sandbox documentation is hosted separately at sandbox.proliant.com. |
| Pronto Xi (link) | No | Pronto Xi is a self-hosted ERP; API (Pronto Connect) access is granted per deployment. Contact Pronto Software or your Pronto partner to enable Pronto Connect and obtain a user with API access. The Pronto Connect endpoint (host/port/web-resource) is configured in API Administration (SYS X060). |
| ProProfs Project (link) | Yes | ProProfs Project offers a free trial; API keys are available from My Account after sign-up. |
| Prospeo (link) | Yes | Prospeo offers free API access for all users. Enrichment consumes credits per matched record (see the API docs for email vs mobile pricing). |
| PSI (link) | No | PSI provisions API credentials (account code, OAuth2 consumer key/secret and resource-owner username/password) per client. A staging/UAT gateway (apiuatapi.psiexams.com) is available for testing before going live. |
| Pumble (link) | Yes | Sign up for a Pumble workspace, create a marketplace app, and generate app + user/bot tokens from the developer portal. |
| Push Operations (link) | No | Push Operations issues partner API tokens to approved partners. There is no self-serve public sandbox — request access via Push Operations (developers.pushoperations.com). |
| PushEngage (link) | No | API access requires a PushEngage account; the site API key is passed in the `Api-Key` header. Some endpoints are limited to paid plans. |
| Pushwoosh (link) | Yes | Sign up for a Pushwoosh trial; the account includes a Server API token for the demo app under Settings → API Access. |
| Pydio Cells (link) | Yes | Pydio Cells Home is free and self-hosted: run a Cells v5 server (binary or Docker) and create a Personal Access Token for an administrator. |
| Pylon (link) | No | Pylon API access requires an Admin to generate an API token from a Pylon workspace; there is no self-serve developer sandbox. |
| Pyrus (link) | Yes | Create a free Pyrus account, add a bot (or use your own profile) and copy its security key from the Authorization section of the profile. |
| Qntrl (link) | Yes | Sign up for a Qntrl trial organization, then register a client in the Zoho API console (https://api-console.zoho.com/). |
| Qonto (link) | No | Register an application on the Qonto Developer Portal to obtain OAuth2 client credentials and sandbox access. Sandbox base URL: https://thirdparty-sandbox.staging.qonto.co. OAuth2 app registration requires a redirect URI and requested scopes; some scopes (e.g. organization.read, payment.write) are marked sensitive and need Qonto approval before production use. |
| Quaderno (link) | Yes | Sign up for a Quaderno account (including sandbox) and create an API key under Profile → API Keys to test against your own company data. |
| Qualtrics (link) | No | API access is a paid Qualtrics feature; ask your Qualtrics Account Executive to enable it, then generate an API token under Account Settings → Qualtrics IDs.
|
| QuickBooks (link) | Yes | Sandbox company automatically provided with developer account. Valid for 2 years.
|
| Quickbooks Payments (link) | Yes | Sandbox company automatically provided with developer account. Valid for 2 years.
|
| QuickBooks Time (link) | Yes | Sign up for a QuickBooks Time free trial, then install the API Add-On (Feature Add-ons → Manage Add-ons → API) to obtain OAuth2 client credentials and development access tokens. |
| QuickBooks Workforce (link) | No | Install the API Add-On inside a QuickBooks Time account (Feature Add-ons → API) to obtain an OAuth client ID/secret; the same page can mint long-lived access tokens for development. |
| QuickFile (link) | Yes | Register an app under Account Settings → 3rd Party Integration → "Create a QuickFile App", then use the built-in API sandbox to test requests. QuickFile accounts are free to create. |
| Quill (link) | No | Quill does not publish a self-serve API sandbox. Application registration and firm TenantId values are issued by Quill/Unity when onboarding an integration partner. |
| QuintaDB (link) | Yes | Free QuintaDB plan includes API access with per-plan record limits; create an API key from the API menu. |
| Quip (link) | No | A Quip account (a paid Salesforce Quip license) is needed; sign in and generate a personal access token at quip.com/dev/token. |
| Ragic (link) | Yes | Free trial database account; generate an API key under Personal Settings for HTTP API access. |
| Railway (link) | Yes | Sign up for a Railway account, then create an account or workspace API token from the account tokens page in settings.
|
| Raisely (link) | Yes | Create a Raisely trial campaign, enable the REST API under Settings → Developers, and use the campaign private key or an org-admin login token against the v3 API. |
| Ramp (link) | Yes |
|
| Rapyd (link) | Yes | Sign up for a free Rapyd Client Portal account; sandbox access and secret keys are available to all users under Developers → Credentials Details. |
| Razorpay (link) | Yes | Switch the Razorpay Dashboard to Test mode and generate Test API keys to try the integration without live charges. |
| RD Station CRM (link) | No | Create an RD Station CRM account on Basic, Pro, or Advanced (upgrade from Free in Conta e Planos if needed), then register an app in the RD Station App Store publisher portal for OAuth2 client_id and client_secret.
|
| Re:amaze (link) | Yes | Start a 14-day free trial (no credit card needed), then generate a per-user API token under Settings → Developer → API Token and authenticate with HTTP Basic using your login email and token.
|
| ReachFast (link) | Yes | ReachFast offers a freemium trial (5 free contacts on the marketing site). API keys are issued by support; rate limits are documented at 50 requests/minute, 200/hour, and 1,000/day. |
| ReachMee (link) | No | API access (client credentials + reachmee-* scopes) is provisioned by Talentech for existing customers and partners; there is no self-serve sandbox signup. |
| ReadMe (link) | Yes | Sign up for a ReadMe project, then create an API key under Configuration → API Keys. |
| Real Geeks (link) | No | API access is granted on request: Real Geeks registers the product, issues a username and password, and provides a test website and account. |
| Rebilly (link) | Yes | Sign up for a free Rebilly sandbox account, create a secret API key and copy the organization ID, then use the Sandbox API URL. |
| Recharge (link) | Yes | Merchants generate an API token from the Recharge admin. |
| Recruitee (contact for access) | No | Sandbox environments are available to Optimize customers |
| Recruitly (link) | Yes | Sign up for a Recruitly account (API access is available on every plan, including the free tier) and create an API key under My Profile > My API Keys. |
| Recurly (link) | Yes | Self-serve: create a Recurly account and use a Sandbox site; generate a Private API key from the API Credentials page. |
| Redash (link) | Yes | Redash is self-hosted: run an instance with the official Docker setup, sign in as the admin user and copy the API key from your profile page. |
| Redbooth (link) | Yes | Sign up for a Redbooth account (free trial), then register an OAuth app to get a client ID and secret. |
| Reddit Ads (link) | Yes | Use a Reddit Ads account, then have a business admin create a developer application in Business > Developer Portal to get an app ID and secret.
|
| Refersion (link) | Yes | Create a Refersion account, then generate an OAuth client (Client ID and Secret) under Settings > Integrations > Refersion API Keys.
|
| Regal Voice (link) | No | Contact support@regal.ai for API access and a sandbox brand. Reporting Webhooks are configured in the Regal app UI. |
| Regiondo (link) | No | Sandbox accounts (sandbox-api.regiondo.com, offers published on regiondo-dev-de.de) are not self-service: request one from your Regiondo contact or support@regiondo.com. API keys are generated in the dashboard under Connectivity → API configuration. Live-account offers do not appear in the sandbox. |
| Remarkety (link) | No | Request a sandbox or developer account via support@remarkety.com (see Remarkety Custom API V2 article). |
| Remote.com (link) | No | |
| RentalReady (link) | No | RentalReady has no self-serve sandbox. OAuth2 client credentials and a test account are arranged with RentalReady Partnerships. |
| Rentals United (link) | Yes | Sign up at https://rentalsunited.com: every new account is a sandbox account (isolated, with lower API limits) on the same https://rm.rentalsunited.com endpoint. Generate an API key pair in the account to call the API; the account becomes a production account once Rentals United certifies the integration. |
| RepairShopr (link) | Yes | RepairShopr offers a free trial; API tokens are created in Admin → API Tokens on your account with no separate developer approval. |
| Replicate (link) | Yes | Sign up for a Replicate account and create an API token to call the public models API. |
| Reply.io (link) | Yes | Reply.io offers a self-serve trial; generate an API key under Settings → API Key. Scopes on the key control which endpoints are available. |
| Request Tracker (link) | No | Request Tracker is self-hosted open-source software. Install an RT 5.x instance with REST 2.0 enabled and RT::Authen::Token for API token authentication. |
| Resend (link) | Yes | Sign up for a free Resend account, then create an API key under API Keys in the dashboard. |
| Resistant AI (link) | No | Resistant AI issues Documents API OAuth2 client credentials (client id and secret) to customers; contact Resistant AI to obtain them. |
| Resly (link) | No | Resly has a test environment (https://test.api.resly.com.au), but API access and test credentials are granted to certified partners on request (integrations@resly.com.au). |
| resOS (link) | No | Use a paid resOS account, activate the API add-on under Settings & add-ons > Integrations > API, and click Generate key.
|
| Resource Planner (link) | Yes | Sign up for a Resource Planner workspace and generate an API access key under Settings → API access for REST clients. |
| Respond.io (link) | Yes | Sign up for Respond.io (Growth plan or above for Developer API), then create an access token under Settings → Integrations → Developer API. |
| Restaurant365 (link) | No | Contact your R365 CSM / R365 Support to complete the API Credentials Request form for Public API access. R365 confirms permission with the customer and provides API login credentials (subdomain, user name, password) to the vendor. |
| Retable (link) | Yes | Free Retable account; generate an API key from the profile → API settings. |
| Retell AI (link) | Yes | Sign up for a Retell AI account at dashboard.retellai.com and create an API key on the API Keys page. |
| Reteno (link) | Yes | Sign up for Reteno and generate an API key under Settings → API. |
| Rev AI (link) | Yes | Sign up for a Rev AI account (free credits are included) and generate an access token on the Access Token page. |
| Revel Systems (link) | No | Sandbox access (api-sandbox-revel.revelup.com) is provisioned by Revel — contact interchangeiointegrations@revelsystems.com to request a developer/sandbox account and API credentials. |
| REVIEWS.io (link) | Yes | The REVIEWS.io API requires a Plus-tier (or higher) account. Sign up for a trial, then grab the store/apikey credentials from Integrations -> API in the dashboard. |
| Reviso (link) | Yes | A free, self-serve, read-only demo dataset is available immediately with X-AppSecretToken: demo and X-AgreementGrantToken: demo (GET only, no registration required). A real developer agreement (for App Secret Token issuance) is registered at https://app.reviso.com/developer. |
| Revolut Business (link) | Yes | Sign up for a free Revolut Business sandbox account, add an API certificate in Settings → APIs → Business API, and connect with the Sandbox URL. |
| Revver (link) | No | No self-serve developer sandbox. Request an Application ID and Secret from integrations@revverdocs.com; credentials are shared via a folder in the Revver account Documents view. |
| Rewardful (link) | Yes | Sign up for a Rewardful account (free trial), then copy the API Secret from Company Settings.
|
| Rezdy (link) | No | A Rezdy supplier account is needed, with an API key requested under Integrations → Rezdy API (or from Rezdy support). This integration calls the production API (api.rezdy.com); staging (api.rezdy-staging.com) accounts and keys are separate and do not work against it. |
| Rillet (link) | No | Rillet provisions sandbox organizations (https://sandbox.api.rillet.com) for customers and partners; API keys are created in Organization Settings. |
| Ring Central (link) | Yes | RingCentral provides developers with both a sandbox and production environment |
| Rippling (link) | No | |
| RMS Cloud (link) | No | RMS provides a sandbox with the API Developer Kit (one-time fee). Request access from apisupport@rmscloud.com with the RMS customer included; production credentials are issued to partners. |
| Roadie (link) | No | Roadie provides sandbox access tokens on request: contact Roadie API support when you are ready to test. Production tokens follow certification. |
| Roam (link) | No | Requires a Roam workspace; a workspace admin creates an API Key (or OAuth app) in Administration → Developer. |
| Rocket Matter (link) | No | Rocket Matter issues OAuth credentials on request via support. |
| Rocketlane (link) | No | API keys are created in your Rocketlane workspace under Settings → API. |
| RooR (link) | No | RooR does not document a self-serve sandbox. Request an account and an auto-responder campaign from RooR to obtain an API key and campaign id. |
| Rootly (link) | Yes | Rootly offers a trial workspace; API keys are created under Organization Settings → API Keys. |
| Rosnet (link) | No | Request API credentials (API User ID and API User Key) by emailing api@rosnet.com with your name, company name, and email address. |
| RotaCloud (link) | Yes | The RotaCloud API is available to paying customers and free-trial accounts. Generate an API key under Settings → API to test. |
| Rotageek (link) | No | Sandbox API access is provisioned by Rotageek; contact your Rotageek representative for credentials. |
| RudderStack (link) | Yes | Sign up for RudderStack and create a workspace Service Access Token to list sources and destinations. |
| Runway (link) | Yes | Sign up at dev.runwayml.com, create an organization and generate an API key. API usage is billed with prepaid credits. |
| Rydoo (link) | No | |
| SabeeApp (link) | No | SabeeApp has no self-serve developer sandbox. The Connect API key is generated by SabeeApp on request and the calling IP addresses must be whitelisted. |
| Sage 100 (France) (link) | No | No self-serve sandbox. Access needs a Sage 100 SPC environment (or an on-premise Sage 100 SQL install with a demo company such as "Bijou") from a Sage 100 partner, plus a SQL user with read access.
|
| Sage 100 (US) (link) | No | No hosted sandbox. eBusiness Web Services runs on the customer's own Sage 100 server; a partner/developer install of Sage 100 with the "ABC" demo company is used for testing.
|
| Sage 200 Standard & Professional (link) | No | The Sage 200 API is enabled by default on Sage 200 Standard Online (users must be enabled for API access); Sage 200 Professional exposes it via the Native API (Microsoft 365/Azure AD tunnelling). Request development client credentials from Sage Developer Services, and a Sage ID with access to a Sage 200 test company. |
| Sage 300 (Accpac) (link) | No | No hosted sandbox. The Web API runs on the customer's own Sage 300 server; Sage development partners test against a local Sage 300 install with the SAMLTD / SAMINC sample companies.
|
| Sage 300 Construction and Real Estate (Timberline) (link) | No | No hosted sandbox. Testing uses a partner or customer Sage 300 CRE server with Web API enabled and appropriate Job Cost / Payroll API licenses.
|
| Sage 300 People (link) | No | Sage 300 People is self-hosted. Ask Sage or your Sage 300 People partner for a test company and an API Key (API Administration). |
| Sage Accounting (link) | No | |
| Sage Brightpearl (link) | No | Requires a Brightpearl developer account and an app (public or confidential) registered in it, plus a Brightpearl account added as an early-access account. The user authorizes via the Authorization Code Grant; supply the app client_id/secret and developer reference. |
| Sage HR (contact for access) | No | To get a sandbox for your Sage People org, contact you Customer Success Manger or the Sage People support team. Your org comes with a fixed number of available sandbox licenses; if a license is available for the type of sandbox you want, Sage People builds the sandbox for you. |
| Sage Intacct (link) | No | |
| Sage People (link) | No | Sage People runs on Salesforce. Request a sandbox via your Customer Success Manager or Sage People support (org sandbox licenses are limited). Create a Connected App for OAuth, then use the Sandbox login URL (test.salesforce.com) when connecting. |
| Sage Sales Management (ForceManager) (link) | No | Sandbox implementations are provisioned in ForceAdmin. Generate sandbox-specific public/private API keys and connect using the Sandbox API URL. |
| Sage X3 (Sage Enterprise Management) (link) | No | Requires a Sage X3 instance (cloud or on-premise) with a Connected Application configured under Administration > Settings > Authentication. Use a dedicated Syracuse user for API access; on Sage X3 Cloud the endpoint URL must be HTTPS. |
| SailPoint (link) | No | SailPoint does not offer a fully self-serve free trial for Identity Security Cloud; sandbox/developer tenant access is typically arranged through a SailPoint account team or partner program. |
| Sailthru (link) | No | Sailthru API keys are issued from an existing Engage account (Settings → API & Postbacks). There is no public self-serve sandbox. |
| Sakari (link) | Yes | Start a free Sakari trial at hub.sakari.io/signup, then request API credentials (Client ID, Client Secret and Account ID) from the cog icon > Account Details > API Credentials. |
| Salesforce (link) | Yes | Free Developer Sandbox available through signup. |
| Salesforce Commerce Cloud (link) | No | Requires a Salesforce B2C Commerce (sandbox) instance and an Account Manager API client configured for the SCAPI Admin scopes (Products, Catalogs, Object Definitions). Access is arranged through Salesforce; there is no self-serve developer signup. |
| Salesforce Data Cloud (link) | Yes | Free Developer Edition / sandbox with Data Cloud can be provisioned; requires Data Cloud licenses and an External Client App for API access. |
| Salesforce OMS (link) | No | Requires a Salesforce org with Order Management enabled and a connected app with the api scope. Use a Salesforce sandbox or Order Management trial org; access is arranged through Salesforce. |
| Salesforge (link) | No | Salesforge API access requires a Growth plan. Generate an API key under Settings → API & MCP after upgrading. |
| Salesmate (link) | No | Salesmate provides API access keys per user on paid plans. Request a trial or demo workspace from Salesmate, then create an Access Key under My Account → Access Key. |
| SalesQL (link) | Yes | API access requires a paid SalesQL plan (Professional or Organization). Generate an API key under Settings → API Access; each successful enrichment consumes 1 credit. |
| SalesRobot (link) | No | Use your SalesRobot workspace API key; request a trial or sandbox via SalesRobot support if needed. |
| Salla (link) | Yes | Create a free developer/partner account at salla.partners, register an OAuth app, and create a demo store to test against the Merchant API. |
| SambaSafety (link) | No | Request demo credentials from SambaSafety (API gateway key plus OAuth client id/secret). Use https://api-demo.sambasafety.io. The demo environment simulates orders without state DMV fees. |
| Sangoma (link) | No | Requires a Sangoma CRM module license on a FreePBX / PBXact instance. Enable CRM API logging under CRM Settings and copy the RestAPI base URL and token from the admin UI. |
| Sanity (link) | Yes | Sign up for a free Sanity account, create a project (it comes with a production dataset), then add a robot token under API → Tokens in sanity.io/manage. |
| SAP Ariba (link) | No | Access requires an approved application on the SAP Ariba Developer Portal (OAuth client id/secret + application key) and Customer Support enabling API access for the site/realm. |
| SAP Commerce Cloud (link) | No | SAP Commerce Cloud is a licensed platform; there is no self-serve public sandbox. Testing requires access to a Commerce Cloud instance with an OCC OAuth client configured for the client_credentials grant. The OCC v2 API can also be explored via the SAP Business Accelerator Hub sandbox (api.sap.com). |
| SAP SuccessFactors (link) | Yes | Access through Learning Hub using Live Access option.
|
| SAP SuccessFactors (LMS) (contact for access) | No | |
| SAP SuccessFactors (OpenID Connect) (link) | Yes | Access through Learning Hub using Live Access option.
|
| Sarbacane Engage (link) | No | Contact Sarbacane for Engage API access; developer docs are at docs.datananas.com. |
| SatisMeter (link) | Yes | Sign up for SatisMeter, open Settings → Integrations → API to create an API key and copy your Project ID and survey (campaign) IDs. |
| SavvyCal (link) | Yes | Sign up for a free SavvyCal account, then create a personal access token or an OAuth application under Settings > Developers.
|
| Schoology (link) | No | No self-serve sandbox is documented. API consumer keys are issued inside a Schoology school or district: an administrator whose role has the "Access Schoology API" permission gets the key and secret under Integration → API. |
| Scoro (link) | No | If you list your integration in Scoro's Marketplace, you will get access to your own sandbox for devleopment and testing without any expiration date. |
| SeaTable (link) | Yes | SeaTable Cloud free tier or self-hosted server; create a base API-Token under base settings for API access. |
| Seismic (link) | No | Register an OAuth app in the Seismic developer portal (developer.seismic.com). API access requires a Seismic tenant; contact Seismic to obtain developer/sandbox tenant access. |
| Sellsy (link) | No | Create an OAuth2 client from the Developer page of your Sellsy account (Personal or Public API) to obtain client credentials for the authorization-code flow. |
| Semble (link) | No | Semble runs a separate sandbox environment (https://open.sandbox.semble.io/graphql) whose tokens are generated in a sandbox practice under Settings. Access to a sandbox practice is arranged with Semble; there is no public self-serve signup. |
| Sendbird (link) | Yes | Create a free Sendbird application in the dashboard to obtain an Application ID and API token for development. |
| Sendblue (link) | Yes | Sign up at sendblue.com, then copy the API key and secret from the dashboard under Developer → API Keys. |
| Sendcloud (link) | Yes | No separate sandbox is documented. Create a Sendcloud account, add invoice and sender addresses, then add the Sendcloud API integration under Integrations to generate a public and secret key. |
| Sender (link) | Yes | Create a Sender account, then generate an API access token under Settings → API access tokens. |
| Sendlane (link) | No | Sign up for a Sendlane account, then create an API token under Settings → API. |
| Sendloop (link) | Yes | Create a Sendloop account at sendloop.com. The free tier does not include email delivery; use a paid plan to send test campaigns. API3 keys are issued under Settings → API Settings. |
| SendPulse (link) | Yes | Sign up for SendPulse and create REST API credentials under account Settings → API. |
| Sendspark (link) | Yes | Sendspark offers a free trial; API credentials are available from the workspace API Credentials settings after signup. |
| Sent.dm (link) | Yes | Sign up at app.sent.dm, create an API key, and use sandbox mode on send requests to validate without delivering real messages. |
| Sentry (link) | Yes | Sentry Developer / organization accounts are self-serve. Create an internal integration (Settings → Developer Settings) for a Bearer token, or a public integration for OAuth2 client ID/secret. Required scopes: org:read, member:read, team:read, event:read. |
| Sequenzy (link) | Yes | Sign up for Sequenzy, then create an API key under workspace or account API key settings. |
| Sertifi (link) | No | Sandbox REST host is https://api-sbx.sertifi.com. An API code is issued by Sertifi (CSM or support); it is also visible under Administration → Account Settings. |
| ServiceM8 (link) | Yes | Sign up for a ServiceM8 account and create an API key under Settings → API Keys for private REST access, or register a developer add-on for OAuth. |
| ServiceNow (link) | No | Known as Personal Devleoper Instance (PDI) |
| ServiceTitan (link) | No | Register at developer.servicetitan.io and use the Request Access page to request an Integration (sandbox) environment; ServiceTitan reviews requests. Third-party developers receive Integration-environment client credentials only — production credentials come from the customer tenant. |
| Seven.io (link) | Yes | Sign up at seven.io, create an API key in the Developer area, and use the REST API against gateway.seven.io (test sends consume account credit). |
| Seven20 (link) | Yes | Free Developer Sandbox available through signup. |
| SevenRooms (link) | No | |
| Sezzle (link) | Yes | Create a sandbox merchant account in the Sezzle sandbox dashboard, generate sandbox API keys and use them with the Sandbox API URL. |
| Shapes (link) | No | |
| SheetDB (link) | Yes | Sign up for a free SheetDB account (500 requests per month), connect a Google Spreadsheet and create an API; then copy its API ID and Bearer token. |
| ShipBob (link) | Yes | Free self-serve sandbox at https://sandbox-api.shipbob.com. Sign up for a ShipBob Developer account at https://developer.shipbob.com, then generate a Personal Access Token from the Developer Portal — no approval wait. |
| Shipday (link) | Yes | Sign up at dispatch.shipday.com and generate an API key from the Integrations tab in My Account. |
| ShippingEasy (link) | No | API keys are created in a ShippingEasy merchant account under Settings → API credentials. There is no separate public sandbox host; curl examples also use https://app.shippingeasy.com. |
| ShipStation (link) | No | ShipStation API (formerly ShipEngine) customers get TEST_ sandbox keys from the API dashboard at api-portal.shipstation.com. Platform customers have no sandbox and must request a developer account from ShipStation support.
|
| Shiptheory (link) | Yes | Register a standard Shiptheory account and choose the Free Trial, which includes API access. Without a carrier account, enable "Generate Faux Tracking Numbers" in settings to test labels.
|
| Shopee (link) | Yes | Register an app in the Shopee Open Platform console and use a Test-Stable sandbox shop to authorize it. The partner_id and partner_key from the app are used as the OAuth client id/secret. |
| Shoper (link) | Yes | Register an application in the Shoper AppStore developer panel to obtain client_id/client_secret and a test store; the OAuth2 authorization-code flow issues per-store access and refresh tokens. |
| Shopify (link) | No | Only available for Shopify Plus |
| Shoplazza (link) | Yes | Create a partner account and a custom/public app in the Shoplazza Partners portal to obtain OAuth client credentials, then install it on a development store (mystore.myshoplaza.com) to authorize and test the Open API. |
| SHOPLINE (link) | Yes | Create a partner account and an app in the SHOPLINE Developer Center to obtain the app key and app secret, then install it on a development store (handle.myshopline.com) to authorize (bespoke signed OAuth) and test the Admin REST API. |
| Shopware (link) | Yes | Self-hosted: install Shopware 6 (Community Edition / cloud trial), then create an integration under Settings → System → Integrations and use its Access Key ID / Secret Access Key with the OAuth2 client_credentials grant. |
| Sifter (link) | Yes | Start a free Sifter trial, then create an access key under My Profile > Access Keys; it is sent in the X-Sifter-Token header.
|
| SignatureAPI (link) | Yes | Sign up for a SignatureAPI account and create a test API key (key_test_…) in the dashboard. Test-mode envelopes are free. |
| Signaturely (link) | Yes | Create a free Signaturely API key in Settings > API; requests can be issued in test mode via the `testMode` flag. |
| SignDocs Brasil (link) | No | Sandbox (HML) credentials are issued by SignDocs Brasil; use the Sandbox region with them. |
| Signeasy (link) | Yes | Create a Signeasy developer account, then in the Developer Portal go to Apps > Sandbox, create a sandbox app and click Generate Access Token.
|
| SignedBy (link) | Yes | No separate sandbox exists. Sign up for a free SignedBy account (no credit card) and generate an API key under Settings > Integrations & Connected Apps.
|
| SignNow (link) | Yes | Register a free developer account at signnow.com/developers to obtain OAuth client credentials; an eval (api-eval.signnow.com) sandbox environment is available for testing. |
| SignRequest (link) | Yes | SignRequest supports sandbox teams for testing. Sign up for a free account and enable a sandbox team; documents created there are marked with the "sandbox" flag. |
| SignWell (link) | Yes | Sign up for a free SignWell account and create an API key under Settings → API. Use test_mode on create requests while developing. |
| SikaFX (link) | No | Sandbox API keys (sk_test_...) use https://sandbox.sikafx.com. Contact SikaFX developer support (developers@sikafx.com) for access. |
| Silae (contact for access) | No | Silae issues API credentials (OAuth2 Client ID/Secret + subscription key) via its partner API portal on request. |
| Similarweb (link) | No | API access is a paid Similarweb subscription add-on: contact your Account Manager (or the Similarweb sales contact form) to get API access.
|
| Simla.com (link) | No | Request a Simla demo account or use an existing Simla CRM workspace; create an API key in Administration → Integration. |
| Simple Analytics (link) | Yes | Sign up for Simple Analytics, add a website, then create an API key and copy your User ID from account settings.
|
| SimpleLegal (contact for access) | No | Request a SimpleLegal sandbox tenant and API token from your account team (see the SimpleLegal API Toolkit at developer.simplelegal.com). |
| SimpleMeet.me (link) | No | API access is a paid-plan feature. Upgrade a SimplyMeet.me account, then generate an API key on the Integrations page.
|
| Sinao (link) | Yes | Create a free account on sinao.fr and ask Sinao support to switch it to Sandbox mode, then create an API key as the company administrator. |
| Sinch (link) | Yes | Sign up for Sinch Build, create an access key, and enable the Voice, Fax and SMS APIs on a project. SMS also needs the service plan ID and API token from SMS → APIs. |
| Sirportly (link) | Yes | Start a free Sirportly trial, then create an API token and secret under Admin → API Access. |
| Sirv (link) | Yes | Sign up for a free Sirv trial account, then create an API client under Settings → API to get a Client ID and Client Secret. |
| Skillcast (link) | No | Reporting API access is provisioned by Skillcast per client instance. Request an API key and confirm your client subdomain; the key is passed via the `X-API-Key` header. |
| Skillsoft (Percipio) (link) | No | Requires a Percipio organization. Generate a REST API service account (Bearer token + Organization UUID) in the Percipio admin console. |
| Slack (link) | Yes | Access through Slack Developer Program registration.
|
| Slack (bot) (link) | Yes | Access through Slack Developer Program registration.
|
| SleekFlow (link) | No | The Platform API is available on SleekFlow Premium and Enterprise plans; an admin copies the key from Integrations → Platform API. |
| Slite (link) | Yes | Sign up at slite.com, then create an API key under Settings → API in your workspace. |
| SMART on FHIR (link) | Yes | The SMART Health IT launcher (https://launch.smarthealthit.org) is a public FHIR R4 sandbox with synthetic patients. Use its FHIR base URL (shown on the launcher page) and any client ID; no account is needed. |
| SmartAdvocate (link) | No | SmartAdvocate offers no self-serve sandbox; a firm account (or a demo / partner tenant arranged with SmartAdvocate) with API access enabled by an administrator is needed. |
| SmartLead (link) | Yes | SmartLead offers a self-serve free trial; the API key is available immediately from Settings → API Keys with no separate developer application or approval process. |
| Smartlook (link) | Yes | Sign up for a free Smartlook account, create a project, then create a REST API token in Project settings → REST API. |
| SmartRecruiters (link) | Yes | Customers can obtain API credentials from Credential Manager. Partners must either work with specific customers or contact Partner Success Team.
|
| SmartRecruiters Assessment (link) | No | Requires a SmartRecruiters partner account. Partner registers global configuration (PUT /partner/configuration); each customer company generates client credentials for bilateral OAuth. |
| SmartSearch (link) | No | API Key and Secret Key are provisioned by SmartSearch; request access from support@smartsearch.plus. |
| Smartsheet (link) | Yes | Create a Smartsheet developer account, register an app for OAuth 2.0 credentials, or generate an API access token. |
| SmartTask (link) | No | Sign up for SmartTask, create an organization, then email support@smarttask.io to enable the Business plan so you can create an OAuth application (Client ID and Client Secret). |
| Smily (link) | No | Smily has no public sandbox; register an application in the Smily partner panel and test with a private application on a test account. |
| Smokeball (link) | Yes | Register an app in the Smokeball Developer Console; staging environments are available for each region. |
| Smoobu (link) | No | Smoobu has no self-serve developer sandbox. API keys and secrets are created inside a Smoobu account (Settings → Advanced → API Keys); API access is on request (contact Smoobu). |
| SMTP2GO (link) | Yes | Sign up for SMTP2GO and create an API key under Settings → API Keys in the SMTP2GO control panel. |
| SnelStart (link) | Yes | Self-serve: register on the SnelStart Developer Portal to subscribe to the B2B-API product and obtain a subscription key; a SnelStart administration provides the per-connection maatwerksleutel. |
| Snipe-IT (link) | Yes | Snipe-IT offers a public demo instance (https://snipeitapp.com/demo) that resets periodically, and the open-source app can be self-hosted for a private test instance. |
| Snov.io (link) | Yes | Sign up for a Snov.io account; the API User ID and Secret are on the account API page (API availability depends on the plan). Lookups consume credits. |
| Snowflake (link) | Yes | Start a Snowflake free trial (30 days, $400 in credits), choose a cloud, region and edition, and activate it from the email link. Then create an OAuth security integration with CREATE SECURITY INTEGRATION to get the client credentials.
|
| Socure (link) | No | |
| softgarden (link) | No | API credentials (Client ID / Client Secret) are issued by softgarden on request via support@softgarden.de. |
| SoftLedger (link) | No | SoftLedger grants API access on request (support@softledger.com). Create an API key in SoftLedger to get a Client ID and Client Secret. |
| solidtime (link) | Yes | Sign up for a free solidtime cloud account, then create an API token in the profile settings. |
| SOS Inventory (link) | No | Register an application in the SOS Inventory Developer Portal (My Apps) to get a client ID and secret, and authorize it with an SOS Inventory account. SOS support connects new applications to the account (support@sosinventory.com). |
| Space Invoices (link) | Yes | Sign up for a Space Invoices account; sandbox API keys (sk_sandbox_* / ek_sandbox_*) are available in the dashboard and use the same base URL as live keys with separate data. |
| Spektrix (link) | No | No self-serve sandbox is documented. API credentials are issued per Spektrix client system: a Spektrix user with Settings Administrator access creates an API user (login name + secret key). Third parties are given API access by the Spektrix client they work with. |
| Spendesk (link) | No | Ask Spendesk for demo-account credentials when requesting API access; they work against https://public-api.demo.spendesk.com. |
| Spiris (link) | Yes | Self-serve: register an application in the Visma Developer portal (oauth.developers.visma.com) to obtain OAuth client credentials for Visma Connect, then authorize a Spiris/eAccounting company. The sandbox uses the same production URLs (eaccountingapi.vismaonline.com / identity.vismaonline.com) with a Sandbox-type IdentityServer client and Visma Online account. |
| Spoki (link) | Yes | Sign up for Spoki and request an API key from the dashboard (approval may take up to 48 hours). |
| Spotify (link) | No | The Spotify Ads API (v3) is a partner product on api-partner.spotify.com; the OAuth app must be allow-listed for Ads API access. A sandbox server for testing is documented at https://api-partner.spotify.com/ads-sandbox/v3. |
| SpotOn (link) | No | SpotOn issues partner client credentials and test locations on request (integrationsupport@spoton.com); there is no self-serve sign-up. |
| SquareUp (link) | No | You need a Square account. Some developer tools require that you sign in to access features.Use of the Sandbox environment is free of charge. You can make an unlimited number of free Sandbox API calls. |
| SRFax (link) | Yes | Sign up for an SRFax account on srfax.com; the account number and password are the API credentials. |
| StackAdapt (link) | No | StackAdapt provides a sandbox GraphQL endpoint (https://sandbox.stackadapt.com/public/graphql). Contact your StackAdapt account team to request API access and a sandbox/API token. |
| Stackby (link) | Yes | Free plan includes API access; create a Personal Access Token from Builder Hub for development. |
| STACKIT (link) | No | Create a STACKIT customer account in the Portal, then create a project and a service account with a key to call the API.
|
| Starshipit (link) | No | Request API access from Starshipit Settings > API; developer keys are rate-limited to 2 req/s until production approval. |
| Statsig (link) | Yes | Statsig offers a free tier. Create a project in the Statsig console and generate a Console API key under Project Settings. |
| Stax (link) | No | Stax provides sandbox merchant accounts on a test gateway; once you have one, create an API key in Stax Pay under Apps → API Keys. |
| Sterling (link) | No | Request Integration-environment credentials from APISupport@sterlingcheck.com. Host: https://api-int.kennect.com. The Developer Portal uses the same Client ID / Client Secret to simulate screening results. |
| Strava (link) | Yes | Create a free Strava API application at https://www.strava.com/settings/api to obtain OAuth2 client credentials. Any Strava account can register an app. |
| Stream (link) | Yes | Sign up for a free Stream account, create an app in the Stream Dashboard and copy its API Key and Secret. |
| Stripe (link) | No | |
| SuiteDash (link) | Yes | Start a SuiteDash free trial, then open Integrations → Secure API to generate Public ID and Secret Key credentials. |
| Sumble (link) | Yes | Sign up at sumble.com, create an API key under Account → API keys, and connect with that key. API calls consume credits per the endpoint pricing in the Sumble docs. |
| SumUp (link) | Yes | Create a free sandbox merchant account at me.sumup.com/settings/developer, then create an API key from Settings → API keys to use with the sandbox merchant. |
| Supabase (link) | Yes | Create a free Supabase project for testing. |
| Superchat (link) | Yes | Sign up for Superchat and generate an API key from Settings → API. |
| SuperSaaS (link) | Yes | Free trial accounts include API access; generate an API key on the Account Info page. |
| SupportBee (link) | Yes | Sign up for a SupportBee trial desk, then copy your API token from profile → API Token and use your desk subdomain with the REST API. |
| SureContact (link) | Yes | SureContact offers a self-serve signup at app.surecontact.com. API keys are created under Profile → API Keys. |
| Symphony Messaging (link) | No | Symphony requires an on-premise Agent and customer-issued session and Key Manager tokens. Contact Symphony or your account team for sandbox access. |
| Sympla (link) | Yes | Create a Sympla producer account, then generate an API token under Minha Conta → Integrações. |
| Synchroteam (link) | Yes | Start a free Synchroteam trial, then copy the domain identifier and the API key from Configuration → Authentication Key. |
| Syncro (contact for access) | No | Syncro offers a free trial; create an API token from your user profile. |
| Tableau (link) | Yes | Tableau offers a free Tableau Cloud Developer Program site (and a self-hosted Tableau Server trial) for building and testing integrations. |
| Taboola (link) | No | Taboola provisions Backstage API client_id and client_secret through an account manager. There is no self-serve developer signup. |
| Talentech (link) | No | API access (client credentials + scopes) is provisioned by Talentech for existing customers and partners; there is no self-serve sandbox signup. |
| TalentHR (link) | No | Public API access requires the Essential plan. Generate API keys in Settings → Domain settings → API. |
| TalentLMS (link) | Yes | A free TalentLMS plan is available via self-service signup. A super-administrator enables the API and generates an API key under Account & Settings → Integrations → API. |
| TallyPrime (link) | Yes | No hosted sandbox. TallyPrime can run unlicensed in Educational Mode; the API Explorer "Prerequisites" page provides an integration setup package with a configured TallyPrime and a sample company.
|
| Tap Payments (link) | Yes | Create a Tap Payments account and use the test secret key (sk_test_...) from the dashboard. |
| TapClicks (link) | No | API access is granted by TapClicks to Super Admin accounts on request (API access request form); credentials arrive by email within 24-48 hours. No self-serve developer sandbox is documented. |
| Target Plus (contact for access) | No | Target Plus is invite-only; API credentials are issued to approved sellers. The official spec also documents a stage host (https://stage-api.target.com). |
| Taskade (link) | Yes | Sign up for a free Taskade account, then create a personal access token at taskade.com/settings/api. |
| Tave (link) | Yes | Create an API key in your VSCO Workspace studio under Settings → API Integrations. Read-only and read/write permission levels are available per key. |
| Tavus (link) | Yes | Tavus API keys are created in the PAL Maker developer settings. |
| TaxJar (link) | Yes | Create a TaxJar account and generate a sandbox API token from Account → API Access. Use the Sandbox API base URL when connecting test workspaces. |
| Tazworks (link) | Yes | TazAPI Advanced has a self-serve developer portal and sandbox at developer.tazworks.com (Bearer JWT, IP whitelist). This Unified integration uses the publicly documented TazAPI Basic XML gateway. Test orders with SSN 111-22-3333 (Joe Clean) or 333-22-1111 (Hank Mess) are not billed. XML userId/password come from your CRA. |
| TCN (link) | No | TCN API access and OAuth clients are provisioned through TCN; see the official API documentation for onboarding. |
| Teachable (link) | No | The Teachable API requires a school on the Growth plan or higher. Create an API key under Settings > API in the school admin. |
| Tealium (link) | No | Create a Tealium user with an API Key and note your account/profile names to list audience definitions. |
| Teamcamp (link) | Yes | Sign up for a Teamcamp workspace and generate an API key under Account Settings. The API is in public beta; see the official API reference for current limits. |
| TeamLeader (link) | Yes | Register an OAuth2 integration on the Teamleader Marketplace (Build) to obtain a client_id/client_secret, and authorize it against a Teamleader Focus (trial) account. |
| TeamSnap (link) | Yes | Register an OAuth application at https://auth.teamsnap.com/oauth/applications to obtain a Client ID and Secret. Scopes: read / write / write_teams. |
| Teamtailor (link) | No | Must be a partner |
| Teamtailor Assessment (link) | No | Must be a Teamtailor technology partner |
| Teamwork (link) | Yes | Sign up for a Teamwork.com trial workspace, then create an API key under your profile (API & Mobile). Use your site subdomain as the second credential. |
| Tebex (link) | Yes | Self-serve: create a Tebex account, add a webstore and a game server, then copy the game server secret key. |
| Tebra (link) | No | Tebra has no self-service developer sandbox. API access needs a Tebra customer account: a System Administrator requests API access via a Customer Care case, then retrieves the Customer Key (My Account > Get Customer Key) and gives the API user the System Admin role. Use a test practice inside that account for development. |
| Techzola (link) | Yes | Sign up for a free Techzola sandbox at https://techzola.com/sandbox.html — API credentials are issued for the sandbox.api.techzola.com environment. |
| Telegram (link) | Yes | Register an application at https://my.telegram.org to obtain an API ID and API Hash, then generate a user session string locally. |
| Telegram (bot) (link) | Yes | Create a free bot via @BotFather in any Telegram client to obtain a bot token. No approval required. |
| Telesign (link) | Yes | Sign up for a Telesign trial account; the Customer ID and API key are shown in the Telesign Portal. Trial accounts can only send SMS to verified phone numbers. |
| Telnyx (link) | Yes | Sign up for a Telnyx account, create an API key, then provision a Call Control Application and/or Messaging Profile for voice and SMS testing. |
| Telstra Messaging (link) | Yes | Register on the Telstra Dev Portal, create an app with the Messaging API product and use its Client ID and Client Secret. Free trial numbers are available. |
| TELUS Health CHR (link) | No | The CHR Enterprise API is a paid TELUS Health feature: after a quote, an intake questionnaire and a signed CHR Enterprise API contract, TELUS provides a sandbox CHR domain with fake patient data. Create an API Consumer there (Settings > Enterprise API) with your RSA public key, then use the domain endpoint and ISS Value. |
| TempWorks (link) | Yes | A Personal Access Token generated in TempWorks Beyond provides immediate self-serve API access. OAuth2 (client id/secret) requires partner registration with TempWorks. |
| Temu (link) | No | Register a Partner app at partner.temu.com, then authorize a seller mall (callback or in-app authorization). Sandbox test shops are documented under Developer Guide → Sandbox Test Shops. |
| Termii (link) | Yes | Create a free Termii account; the API key is under Settings > API token in the dashboard. |
| Test Partnership (link) | No | Test Partnership sets up API client credentials per integrator on request (email info@testpartnership.com). A Staging environment (staging.tptests.com) is available with staging credentials for testing before going live. |
| Text In Church (link) | No | Developer API access is enabled by Text In Church support on request (https://help.textinchurch.com); then create an API key under Account Settings → Developer API. |
| Text Request (link) | No | API access is an add-on of a paid Text Request account; request a trial from Text Request, then copy the API key from Integrations → API. |
| Text.com (link) | Yes | Create a Personal Access Token in the Text Developer Console (LiveChat). Use HTTP Basic auth with your Account ID and token against https://api.livechatinc.com. |
| Text2VIP (link) | No | Text2VIP is a paid SMS marketing platform. Request an account (a trial may be available from the vendor), then copy the API key from API Settings and the username from Account Settings. |
| TextBee (link) | Yes | Sign up for a free TextBee account, link an Android phone with the TextBee app (QR code), and generate an API key in the dashboard. |
| Textellent (link) | No | Request a Textellent account, then generate an Auth Code under Settings > API Key > Developer at client.textellent.com. |
| TextIt (link) | Yes | Sign up for a TextIt workspace (free trial credits are included), then copy the API token from the API Explorer. |
| Textmagic (link) | Yes | Start a Textmagic free trial, then create an API key under Services → API. |
| TextUs (link) | No | Log in to an existing TextUs Next account, open Profile > Advanced user settings > API Tokens, and create a token. TextUs documents no sandbox.
|
| The Companies API (link) | Yes | Sign up at thecompaniesapi.com and create an API token under Settings → API tokens. Company enrichment by domain or name uses credits per request as documented on each endpoint. |
| The Org (link) | Yes | Create a free The Org account, then create an API key under Manage subscription in the developers section.
|
| The Predictive Index (link) | No | A test sandbox account can be requested from the Predictive Index Integrations team (integrations@predictiveindex.com). API access must be enabled for the organization, after which an admin generates an API key under Account → Open API settings. |
| The SMS Works (link) | Yes | Sign up for a The SMS Works account, then generate a JSON Web Token in the API Key section of the account. |
| The Trade Desk (link) | No | |
| TheFork (link) | No | TheFork provisions a test restaurant (with TheFork Manager credentials) for partners to validate the POS integration before the POS instance is activated in production. |
| TheirStack (link) | Yes | TheirStack documents a self-serve signup with API keys in account settings. Job and company search calls consume API credits per their pricing pages. |
| Threema Broadcast (link) | Yes | Sign up for a Threema Broadcast account (free trial available), create a Broadcast identity and generate an API key in your profile. |
| Thrive Learning (link) | No | A staging environment (public.api.learnstaging.link) is provisioned by Thrive during implementation for SSO, provisioning, and import testing. Not self-serve. |
| Tick (link) | Yes | Tick offers a free trial. Sign up, then copy the API token and subscription id for the subscription from your Tick profile / roles list. |
| TickTick (link) | Yes | Register an OAuth application in the TickTick Developer Center to obtain a client ID and secret. |
| TiDB Cloud (link) | Yes | TiDB Cloud offers a free trial and serverless tier for development; Dedicated clusters require a paid project. |
| Tiendanube (link) | Yes | Create a free partner account and a demo store from the Tiendanube / Nuvemshop Partners Portal to obtain OAuth app credentials and a test store. |
| TietoEVRY Lifecare (link) | No | Lifecare Welfare API credentials (domain ID and API key) are provisioned by TietoEVRY for contracted municipalities and care providers. Contact TietoEVRY to obtain integration access. |
| TikTok Ads (link) | No | |
| TikTok Shop (link) | Yes | Create a custom app (no review required) and a Seller Center test account via the Development Shops section of Partner Center. |
| Tilled (link) | Yes | Self-serve: a Tilled sandbox account provides test-mode API keys (sk_test_…) and an account id; point the connection at the Sandbox API URL. |
| TimeCamp (link) | Yes | TimeCamp offers a free plan; API access is included on all subscription tiers. Sign up and generate an API token from Profile Settings. |
| TimelinesAI (link) | Yes | Sign up for a TimelinesAI workspace and generate a Public API token from Settings → Integrations → API. |
| Timely (link) | Yes | Sign up for Timely, then register an OAuth application under Settings → Devs (admin). Use the OAuth authorization code flow documented at developer.timely.com. |
| TimeSolv (link) | No | TimeSolv offers a 10-day free trial account (no credit card). API client credentials (client ID / secret) must be requested from TimeSolv. |
| TinyFish (link) | Yes | TinyFish API keys are created from the Agent dashboard; usage is billed per run. |
| TLDialer (link) | No | TLDCRM provides a sandbox host at sandbox.tldcrm.com; API credentials are created inside your TLDCRM account by an administrator. |
| Toast (link) | No | |
| TOConline (link) | Yes | API access is requested per company in TOConline (Empresa > Configurações > Dados API); the e-mailed link provides the client id, secret, OAuth URL and API URL. |
| Todoist (link) | Yes | Sign up for a free Todoist account, then create an API token under Settings → Integrations → Developer. |
| Toggl Track (link) | Yes | Toggl Track offers a free plan; sign up and generate an API token from Profile settings to call the API. |
| Tomba (link) | Yes | Sign up at tomba.io for a free tier (75 credits, no card). Create API key and secret under app.tomba.io/api and use them in the X-Tomba-Key / X-Tomba-Secret headers. |
| Track (link) | No | No self-serve sandbox. API keys are created by the property manager in Track (Configuration > Company Setup > API Keys); Track support cannot create or hand out keys. |
| TrackDrive (link) | No | TrackDrive provisions company accounts with API access tokens. Create Company Access Tokens in the dashboard under Settings → API Access Tokens. |
| TrackerRMS (contact for access) | No | Sandbox API environments are available on request; contact TrackerRMS support (clientsupport@tracker-rms.com) to have a sandbox account created for testing. |
| Treasure Data (link) | No | Use a Treasure Data account Master API key to read parent segment configurations (audiences). |
| Tremendous (link) | Yes | Sign up for a free sandbox account at testflight.tremendous.com, create an API key there and choose the Sandbox environment. |
| Trexity (link) | Yes | Sign up as a merchant at merchant.trexity.com and generate a Merchant API key from the portal. A sandbox API base URL is available for testing. |
| Trinet Zenefits (link) | No | To build an App Directory integration, contact TriNet through its integration partners program to register your OAuth application and receive a client ID and secret after review; each customer company connects when an HR admin completes the OAuth flow.
|
| Tripletex (link) | No | Tripletex API access requires a consumer token (issued per integration) and an employee token generated by the customer in Innstillinger → Firmainnstillinger → API-tilgang. Tripletex offers a demo/test company for development; contact Tripletex support for consumer-token issuance. |
| TruBridge (link) | No | Register a SMART app with TruBridge (see https://trubridge.com/fhir-api/) using the Unified redirect URI, and connect with the sandbox FHIR base URL https://thrive-gw-dev.cpsi-cloud.com/api/smart/sandbox/fhir/r4. |
| TrueLayer (link) | Yes | Sign up for TrueLayer Console to get a sandbox client ID and secret, enable Payments (and Mandates for VRP) in sandbox, then connect with the Sandbox API URL. |
| Trulioo (link) | No | Trulioo issues sandbox (trial) Client ID / Secret on request; sandbox verifications run against static test entities (GET /v3/configuration/testentities/{packageID}/{countryCode}). Contact support@trulioo.com or sales@trulioo.com. |
| Truora (link) | Yes | Create a free Truora account, then create an API key under API Keys in the account dashboard. Truora documents no separate sandbox environment: checks run against the live Checks API. |
| TrustID (link) | No | TrustID provides a sandbox at https://sandbox.trustid.co.uk. API key, username, and password come from TrustID. |
| TRYB Loyalty (link) | No | TRYB Loyalty requires a Business plan with API access. Create an API key under Settings → Integrations in the dashboard. |
| Turso (link) | Yes | Turso offers a free Starter plan with Platform API access for development databases. |
| Twenty (link) | Yes | Sign up at twenty.com or deploy self-hosted, then create an API key under Settings → API & Webhooks. |
| Twilio Segment (link) | No | Create a Public API token in the Segment workspace to access audiences. |
| Twinfield (link) | No | Register an application on the Twinfield developer portal (developers.twinfield.com) to obtain OAuth2 client credentials; production ClientId certification is required before go-live. Testing requires a Twinfield organisation/administration (a partner or trial account); access tokens live ~1 hour and refresh tokens are long-lived. |
| Typefully (link) | Yes | Sign up for a Typefully account, then create an API key under Settings → API. |
| TypeSafe AI (link) | Yes | Sign in to the TypeSafe console (early access) and create an API key to call the models and System One APIs. |
| Uber (link) | No | Uber for Business APIs are limited to Enterprise clients. Request the business.receipts / business.employees partner scopes from your Uber representative. The sandbox (https://sandbox-api.uber.com) only works with test organizations and test accounts that Uber provides. |
| Uber Direct (link) | No | Uber Direct access is granted by Uber. Once the account is approved, switch the Direct Dashboard (https://direct.uber.com) to Test mode: its Developer tab has test Client ID, Client Secret and Customer ID. Test deliveries use the production API host and are completed by a simulated robo-courier. |
| UKG HR Service Delivery (link) | No | Client API credentials (Application ID, Application Secret, and tenant Client ID) are issued by a UKG HR Service Delivery project manager. There is no self-serve developer signup. |
| UniOne (link) | Yes | Sign up for UniOne and create an API key in account settings to call the transactional API. |
| Unipile (link) | Yes | Sign up for Unipile, create an Application, link a provider account (e.g. WhatsApp or LinkedIn), and use the account id with an API key. |
| Unisender (link) | Yes | Create a Unisender account and copy the API key from account settings; the bulk email API is available on all plans. |
| UnitedHealthcare (link) | No | Create a OneHealthcare ID and register your organization in the Optum FLEX App Owner portal (https://flex.optum.com/portal); approval takes about 5 business days. Then register a sandbox app for the client ID and secret. The sandbox FHIR base is https://flex.optum.com/fhir/sandbox/R4, and you sign in with a OneHealthcare ID test member. |
| UpCloud (link) | Yes | Register an UpCloud account, activate the free trial in the Control Panel, then create an API token under Account > API tokens (or use a subaccount username and password for Basic auth).
|
| UpKeep (link) | No | The UpKeep API is enabled only for accounts on the Enterprise plan; an administrator then creates an organization API token under Settings → API Tokens. |
| Uplisting (link) | No | Uplisting provides a staging host (connect.staging-uplisting.io) with the same paths as production. API keys are issued from the Connect page on a subscribed account; partner OAuth clients are provisioned by partner@uplisting.io. |
| Upload-Post (link) | Yes | Sign up at app.upload-post.com for an API key. The Upload-Post API publishes to social platforms from connected user profiles. |
| User.com (link) | Yes | Sign up at user.com, create a workspace, then generate a Public API token under Settings → Workspace settings → API & Integrations → Public API. There is no separate sandbox host; use a trial workspace. |
| Userlist (link) | Yes | Userlist offers test accounts for integration development; sign up and generate a Push API key from Push Settings. |
| UserVoice (link) | No | UserVoice accounts are provisioned through UserVoice sales (request a demo / trial). An admin then creates a trusted API key under Settings → Integrations → UserVoice API keys. |
| VBOUT (link) | Yes | Sign up for a VBOUT account, then copy the API key from Settings → API Integrations. |
| Vectron (link) | No | Vectron issues the API token after partner approval (pm@vectron.de). The operator also generates an authorization token in myVectron. A demo host is available at demo-backend.vectron.cloud. |
| Veem (link) | Yes | Register as a developer in the Veem sandbox (https://developer.veem.com/page/dev-dashboard-sandbox) to get a client ID and secret for https://sandbox-api.veem.com. |
| Veeqo (link) | Yes | Sign up for a Veeqo account, then generate an API key under Settings → Users → Edit → API key (contact Veeqo support if API access is not enabled). |
| Veeva CRM (contact for access) | No | Veeva CRM sandbox access is provisioned by Veeva. Contact your Veeva administrator or Veeva support for a sandbox org. |
| Veeva Vault (link) | No | Request a sandbox Vault from a customer (created via Admin > Deployment > Sandbox Vaults in their production Vault) or obtain Vault software access through the Veeva Product Partner program (apply at https://www.veeva.com/meet-veeva/partners/become-a-partner/).
|
| Velo Payments (link) | No | Velo backoffice staff add your organization as a payor in the Velo sandbox (api.sandbox.velopayments.com) and issue a Payor ID, API key and API secret. Funding and payments there are simulated. |
| Vendus (link) | Yes | Sign up for a Vendus account and retrieve its API key; the API key is tied to a Vendus user. |
| Veradigm (link) | No | Sign up for Veradigm Connect, register a FHIR app with the Unified redirect URI, then request sandbox provider/patient credentials and connect with the sandbox FHIR base URL https://fhir.fhirpoint.open.allscripts.com/fhirroute/fhir/CP00101/. |
| Vercel AI Gateway (link) | Yes | Create a Vercel account, open AI Gateway in the dashboard, create an API key, and call the OpenAI-compatible endpoints at https://ai-gateway.vercel.sh/v1. |
| Veriff (link) | Yes | A test integration is created automatically when you onboard with Veriff (self-serve or enterprise). Its API Keys page in the Customer Portal shows the API key, shared secret keys and Base URL. Veriff does not decide test sessions; force the status yourself as the Veriff Knowledge Base describes. |
| Verified Credentials (link) | No | Email clientservices@verifiedcredentials.com (or your account manager) to activate API access. QA host is https://qa-atsapi.verifiedcredentials.com — use that URL when connecting until credentials are production-ready. |
| Verified First (link) | No | Request staging credentials from integrations@verifiedfirst.com. Use https://api2.verifiedfirst.com/external/verified-first and the staging portal at https://staging.verifiedfirst.com. Verified First must whitelist your domains and/or IP addresses before the API will accept requests. |
| Verint (link) | No | Verint Community is deployed per customer. Obtain a community site URL and API user token from your Verint Community administrator. |
| Vibe (link) | No | Create a Vibe account and register an OAuth app under My Applications. Developer Portal access may require a partner manager to enable My Applications on your account. |
| VICIdial (link) | Yes | VICIdial is self-hosted open-source software. Install on your own server or use a VICIdial hosting partner, then enable API access on a dedicated user. |
| Vikunja (link) | Yes | Vikunja is self-hosted: run an instance with Docker, create a user and an API token in Settings → API Tokens. |
| Vipps MobilePay (link) | Yes | Create a Vipps MobilePay test merchant from the test environment guide, then use the test credentials from the business portal. |
| Visier (link) | No | Visier provides API access (vanity subdomain, API key, and a user with API access) to customers and approved partners. A developer/partner account is arranged with Visier. |
| Vision6 (link) | Yes | Sign up for a Vision6 account, then create a REST compatible API key under Integrations → API Keys and note the REST API Endpoint host shown there. |
| Visma Business NXT (link) | No | Register a web application in the Visma Developer portal (oauth.developers.visma.com), request the business-graphql-api:access-group-based-readonly scope, and authorize with a Business NXT user (via Visma Connect) to test the GraphQL endpoint. |
| Visma eAccounting (link) | Yes | Self-serve: register an application in the Visma Developer portal (oauth.developers.visma.com) to obtain OAuth client credentials for Visma Connect, and use a Visma eAccounting company to authorize. A sandbox environment (identity-sandbox.test.vismaonline.com / eaccountingapi-sandbox.test.vismaonline.com) is available for testing. |
| Visma Netvisor (link) | No | Netvisor integrations require software-partner API identifiers (Sender / Partner ID / Partner Key) issued by Netvisor customer service, plus a Netvisor company whose user creates software-interface (API) identifiers. Partnership is arranged via Visma / Netvisor (developer.visma.com/api/netvisor). |
| Visma Severa (link) | No | Severa has no self-serve developer sandbox: API clients are created by a Severa administrator in Settings → REST API of an existing Severa organization. |
| Visma.net ERP (link) | No | Register an application in the Visma Developer portal (oauth.developers.visma.com) and request access to the Visma.net ERP API. A Visma.net ERP company/tenant is required to authorize (via Visma Connect) and test the endpoints. |
| VoIPstudio (link) | Yes | VoIPstudio offers a free trial account; create an API Key for an administrator user under Administration → Users → API Keys. |
| Vonage (link) | Yes | Create a free Vonage developer account, generate an API key/secret, then create a Voice/Messages-capable application with a private key in the Vonage Dashboard. |
| Vonage Video API (link) | Yes | Sign up for a Vonage Video (OpenTok) account, create a project, and use the project API key and secret for REST authentication. |
| Vonix (contact for access) | No | Vonix assigns the customer ID and API token. Request API access from Vonix support for your contact center. |
| VosFactures (link) | Yes | Create a free VosFactures trial account, then generate the API token from Paramètres → Paramètres du compte → Intégration. The account subdomain is the workspace name chosen at signup. |
| VTEX (link) | No | VTEX provisions merchant accounts through sales/partner onboarding; developers use a VTEX account and generate an appKey/appToken pair in the Admin (License Manager). |
| Vtiger CRM (link) | Yes | Sign up for a Vtiger CRM trial, then copy your username and Access Key from My Preferences and use your CRM host to connect. |
| Vultr (link) | Yes | Create a free Vultr account, verify your email and add a payment method, then enable the API under Account → API in the Vultr Console to generate a Personal Access Token.
|
| Vyte (link) | No | Create an organization in Vyte, then copy the API key from the organization setup page and send it in the Authorization header.
|
| Waalaxy (link) | No | No dedicated developer sandbox is documented. API access requires a live Waalaxy account with an API key generated from CRM Sync settings. |
| Wafeq (link) | Yes | Sign up for a Wafeq account at https://www.wafeq.com and generate an API key under Settings → Integrations → API Keys. The same key authenticates the REST API at https://api.wafeq.com/v1 via the `Authorization: Api-Key <key>` header. |
| WaiverFile (link) | Yes | Start a free trial from waiverfile.com; API keys are issued from Settings → API in the dashboard. |
| Warmly (link) | Yes | Sign up for Warmly, create an API key and copy your organization id from the admin UI to call the agent-tools API. |
| Wati (link) | Yes | Sign up for a WATI account to access API Docs with your endpoint URL and bearer token. |
| Wayfair (contact for access) | No | |
| webCRM (link) | No | webCRM API access uses an application token issued in a live webCRM account (Configuration → Integration → API). There is no separate public sandbox signup; contact webCRM if API access is not enabled. |
| Webdam (link) | No | Webdam accounts are provisioned by Bynder; request API client credentials from your account administrator. |
| Webex (link) | No | |
| Webex (meeting bot) (link) | No | |
| Webex Contact Center (link) | Yes | Sign in to developer.webex.com and click Request a Sandbox on the Contact Center sandbox page; login credentials for the sandbox org (with one administrator user) are emailed to you. Then create an Integration or Service App in My Webex Apps with the cjp: scopes. |
| Webflow (link) | Yes | Create a free Webflow account and register an OAuth (Data Client) app in the Webflow Developer dashboard. A site with Ecommerce enabled is required to test the ecommerce endpoints. |
| WeChat Pay (link) | No | WeChat Pay merchant and API certificates are issued after merchant onboarding on pay.weixin.qq.com. Sandbox/APIv2 test accounts are separate from production APIv3 credentials. |
| WeCom (WeChat Work) (link) | Yes | Register a free WeCom enterprise, create a self-built app, then use its CorpID, Secret and AgentId.
|
| Welkin Health (link) | No | Welkin is sold to care organizations and has no public developer sign-up. A Welkin customer creates a Sandbox environment in Admin > Environments and an API client in Admin > API Clients with access to that environment, then connects with the sandbox instance name. |
| WellSky Personal Care (link) | No | There is no self-serve sandbox. Connect API client credentials are issued by WellSky to a WellSky Personal Care agency or franchisor (or a partner working with one); request access through WellSky. |
| WhatsApp (link) | Yes | Access through Meta Developer Portal and WhatsApp Business API setup.
|
| When I Work (link) | No | API access is on the Premium plan. An account admin requests a developer key from When I Work support, then authenticates with that key plus a user email and password. |
| Whop (link) | Yes | Create a Whop account and an Account API key in the developer dashboard. Sandbox API host: https://sandbox-api.whop.com/api/v1. |
| WildApricot (link) | Yes | WildApricot offers a free trial. Enable API access under Settings → Authorized applications and use the assigned API key with the Admin API. |
| WinBooks on Web (link) | No | A WinBooks on Web license with at least License Admin rights is required. Register an external application under Control Panel > Company > External applications (optionally flag it as a "Trusted application" for development) to receive an Exchange Token by email, then connect using the license email, that Exchange Token, and a folder code. |
| Windsor.ai (link) | Yes | Windsor.ai offers a free forever plan. Create an account at windsor.ai, connect a data source in the app, then copy your API key from account settings for Connectors API access. |
| Wise (link) | No | Wise Platform sandbox uses separate API credentials from production; contact Wise to obtain sandbox client credentials. |
| Wisetail (link) | No | Wisetail API access is provisioned by Wisetail Technical Support. A Super Admin generates a token (Client ID + Client Secret) under Admin Tool > System > API; the numeric Tenant ID is provided by Wisetail. |
| Wish (link) | No | A Wish merchant account is required to register an OAuth2 app on the Merchant Dashboard and obtain a Client ID / Client Secret; a sandbox environment is available at sandbox.merchant.wish.com. |
| Wix (link) | Yes | Sign up for a free Wix account; for app development, register at https://dev.wix.com. |
| Wiza (link) | Yes | Wiza offers a free tier on wiza.co; API access requires API credits. Generate an API key from your account settings after signing up. |
| Wonderlic (link) | No | Wonderlic issues sandbox client tokens through Customer Success during the Data Exchange implementation phase. Web service calls target https://sandbox-integration.wonderliconline.com/integration.asmx; there is no self-service signup. |
| Woodpecker (link) | Yes | Woodpecker offers a trial; API access is included for trial accounts with the API add-on. |
| Workable (link) | No | Must be a partner |
| Workable Assessment (link) | No | Must be a partner |
| Workbooks (link) | No | Workbooks API access requires a live Workbooks database and an API key created by an administrator (Start → Configuration → Automation → API Keys). There is no separate public sandbox signup URL. |
| Workday (link) | No | Private demo tenants available for an annual fee.
|
| Workday (Legacy) (link) | No | Private demo / impl tenants available for an annual fee.
|
| Workiz (link) | No | Workiz API access requires the Developer API add-on on a Workiz account. There is no separate public sandbox tenant; use a trial or internal account for testing. |
| Workleap (link) | No | Workleap does not document a separate public API sandbox host. Use a Workleap test organization and an API key from Settings → API or API Provisioning. |
| Worksnaps (link) | Yes | Worksnaps offers a free trial; after signup, generate an API token under Profile & Settings → Web Service API (see api.worksnaps.com/api_docs/api_token.html). |
| WorkTango (link) | No | Contact your WorkTango account manager for API enablement and demo environment access. |
| WorkWave Route Manager (link) | No | API keys are issued per Route Manager account (Account Settings → API Integration). There is no separate sandbox host; API access may need to be enabled by WorkWave support. |
| Worldpay (link) | Yes | Free self-serve sandbox: create a Worldpay Developer Hub account and use the Try (test) Basic Auth credentials against https://try.access.worldpay.com. |
| Wrike (link) | Yes | Register a Wrike developer app and use OAuth 2.0 or a permanent access token for API access. |
| Writer (link) | Yes | Sign in to Writer AI Studio, create an API agent, and copy an API key to call the chat and models endpoints. |
| X Ads (Twitter Ads) (link) | No | |
| Xata (link) | Yes | Sign up for Xata and create a project with at least one database branch for testing. |
| Xelion (link) | No | Xelion is sold through partners. Obtain an API host, tenant and a Xelion user (without MFA) from your Xelion partner/administrator; the REST API is enabled per tenant. See the Partner Portal API docs for details. |
| Xero (link) | No | Either use a demo copmany or start a trial |
| Xledger (link) | No | Requires an Xledger customer or partner tenant (test.xledger.net for test environments) and an API token created by a user with API-token access. |
| Xodo Sign (link) | Yes | Create a free Xodo Sign account and use the sandbox flag (`sandbox: 1`) on documents to test without consuming credits. |
| Xurrent (link) | Yes | Xurrent offers free trial/demo accounts. OAuth applications (Client ID/Secret) are registered under My Profile → Applications; personal access tokens are also available under My Profile. |
| Yahoo DSP (link) | No | Client ID and Client Secret are issued in the DSP UI (My Account → Activate) after a seat user is API-enabled. Yahoo does not publish a self-serve public sandbox. |
| Yandex Ads (link) | No | |
| Yardstik (link) | No | Email support@yardstik.com to reach the Enterprise Solutions team, who credential a staging account and a production account; then create an API key in each at app.yardstik.com/developer/api-keys.
|
| YOOBIC (link) | No | YOOBIC provides a sandbox environment (https://api-sandbox.yoobic.com). Contact your YOOBIC Customer Implementation Manager to provision a sandbox tenant and service account. |
| Younium (link) | No | Younium provides a sandbox environment on request; generate a Personal Token (Client ID and Secret) in the sandbox tenant. |
| Your.Rentals (link) | No | Your.Rentals provides a test environment (https://api-dev.your.rentals) with demo listings and test payment cards; its access token is issued by Your.Rentals on request (api@your.rentals). |
| Yousign (link) | Yes | Create a free Yousign sandbox account and generate a sandbox API key at https://api-sandbox.yousign.app. |
| YouTrack (link) | Yes | Start a free YouTrack Cloud instance (free for up to 10 users), then create a permanent token in your profile under Account Security → Tokens. |
| Yuki (link) | Yes | Register an application in the Visma Developer Portal (Visma Connect) to obtain OAuth client credentials for Yuki, then authorize against a Yuki domain. See https://developer.yukisoftware.com/guides/guides-getting-started. |
| Yuki Webservices (link) | No | No open sandbox. A Yuki account (or partner/accountant portal) with web-services enabled provides the access key used for API testing.
|
| Z.ai (link) | Yes | Register on the Z.ai Open Platform and create an API key in the API Keys console to call the chat completions API. |
| Zalando (link) | No | Zalando provides a full sandbox at https://api-sandbox.merchants.zalando.com. Access requires a Zalando partner account; OAuth2 client credentials (Client ID / Client Secret) are created per application in the zDirect Portal (https://zdirect.zalando.com/). |
| Zanda (link) | No | The Zanda Public API is in closed beta and enrolment is closed: only practices already in the beta group can generate an API key (Tools > Zanda API Key). There is no separate sandbox. |
| Zeevou (link) | No | Zeevou lists a sandbox server (https://sandbox.zeevou.com) in its OpenAPI document. OAuth client credentials are issued by Zeevou; contact openapi@zeevou.com. |
| Zellis (link) | No | Zellis sets up API portal accounts together with your IT team as part of the implementation project; once accounts exist, you create and regenerate subscription keys in the portal.
|
| ZendeskSell (link) | No | Zendesk provides trial and sponsored developer accounts for building and testing Sell integrations without impacting production data. |
| Zenoti (link) | No | Zenoti API access requires a Zenoti account. Generate an API key from a backend app in the Zenoti admin (Admin > Organization). Contact Zenoti to obtain sandbox/developer access. |
| Zettle (link) | Yes | Sign up for a free Zettle developer account at developer.zettle.com and create a partner-hosted OAuth app to obtain a Client ID and Client Secret. |
| Zid (link) | Yes | Register a partner account in the Zid Partner Dashboard, create an OAuth app (client_id/secret + redirect URI), and connect a demo store to test against the Merchant API. |
| Zinc (link) | No | Contact the Zinc team to provision a sandbox test environment and a development account for building and testing your integration. |
| Zixflow (link) | Yes | Sign up for a Zixflow workspace and create an API key under Workspace Settings → Developer. |
| Zoho Bigin (link) | Yes | Register a client in the Zoho API console (https://api-console.zoho.com/) with the Bigin scopes listed in the OAuth docs. Bigin REST is available in each Zoho data center; sandbox hosts use sandbox.zohoapis.* as in other Zoho products. |
| Zoho Books (link) | Yes | No sandbox account yet. Use trial version for testing (can request extension).
|
| Zoho Campaigns (link) | Yes | Zoho Campaigns offers a free plan. Register a Zoho API client and use OAuth scopes ZohoCampaigns.campaign.ALL and ZohoCampaigns.contact.ALL. |
| Zoho CRM (link) | Yes | Sign up for free trial to access test account.
|
| Zoho Desk (link) | Yes | Free-forever "Express" plan and a 15-day trial of paid editions are available via self-service signup — no dedicated developer sandbox is documented. |
| Zoho Inventory (link) | Yes | Sign up for a Zoho Inventory trial and register an OAuth app in the Zoho API console.
|
| Zoho Invoice (link) | Yes | |
| Zoho Payments (link) | Yes | Sign up for free trial to access test account.
|
| Zoho People (link) | Yes | |
| Zoho Recruit (link) | Yes | |
| Zoho Sign (link) | Yes | Zoho Sign offers a free trial and a developer console (https://accounts.zoho.com/developerconsole) to register an OAuth2 app. API access requires a paid Zoho Sign plan for production use. |
| Zoom AI Services (link) | Yes | Sign in to Zoom Platform Studio, start a free trial or purchase AI Services credits, then create an API key with the Decisions permission under Credentials. |
| Zulip (link) | Yes | Create a free Zulip Cloud organization or use the Zulip development environment; generate an API key under Personal settings → Account & privacy. |
| Zūm Rails (link) | No | Request sandbox portal access, then generate an API username/password from Settings -> Webhook & API Settings. |
| Zus Health (link) | No | Zus provisions a sandbox builder for customers (app https://app.sandbox.zushealth.com, API https://api.sandbox.zusapi.com). A Builder Admin creates a machine-to-machine App Client under Admin Settings > Developers to get the Client ID and Client Secret, then picks the Sandbox URL when connecting. |
| Zylvie (link) | Yes | Create a Zylvie account and generate an API key under Settings → API. |
For integrations requiring partner program enrollment or special access, we recommend:
- Starting the application process early in your development cycle
- Having a clear description of your integration use case ready
Are we missing anything? Let us know
Was this page helpful?