Skip to main content
Only an Admin can manage API keys in API Center.

​
Create an API key

1

Name the key and choose its type

Open API Center > Create API Key. Enter a Key name, choose Sandbox or Live, and select Next.Sandbox keys test supported workflows without changing business records. Live keys can perform real operations. Read Sandbox Mode before testing.
2

Select access

Choose a Preset (Full Access, Read Only, or Reports Only) or use Advanced to select individual access areas. Select at least one area, then Next.Grant only the access your integration needs. Credential-bearing and destructive service endpoints require Full Access (admin:full), not just service-write access. See API scopes.Forms, Settings, and scheduled-report scopes are reserved. Selecting them does not add public v1 endpoints for those features.
3

Choose the IP restriction

Create API key dialog at the IP restriction stepSelect Restrict by IP address or Unrestricted access, then Next.Restricted keys use the broker’s shared whitelist. You can create a restricted key with an empty list, but it rejects all requests until you add a matching address. See IP Firewall for setup.
4

Review, create, and save the secret

Review the name, type, access, and IP restriction, then select Create API key.
The secret appears only once. Copy it into secure storage before closing the dialog. Do not put it in public code or send it to support.
Verify API access from the system that will use the key.

​
Manage existing keys

API Keys table with masked live and sandbox keys The table shows masked keys, their status, and their IP restrictions. Last Used is the last time a key passed authentication, firewall, and rate-limit checks. It shows Never before that happens. Use the key’s actions to:
  • Deactivate a key to revoke access temporarily. Activate makes the same secret valid again.
  • Regenerate a key to replace its secret while keeping its type, name, access, status, and IP restriction.
  • Delete a key to remove it permanently.
Regeneration invalidates the old secret immediately. Save the replacement and update your integration. Deletion cannot be undone.
To add or remove allowed addresses or change a key’s restriction, follow IP Firewall. Its whitelist is shared by all restricted keys for your broker.

​
Troubleshooting

  • A name and at least one access area are required to create a key.
  • Add a whitelist entry before enabling IP restriction on an existing unrestricted key.
  • For 401, 403, or 429 responses, use Errors and Retries and Verify API Access.
  • If creation fails after correcting the input, contact support with the error message, not a key secret.
Last modified on September 8, 2026