Skip to main content

Overview

The iClear API uses API keys for authentication. Each API key is workspace-scoped, so it can only access resources within its associated workspace — you never send a workspace ID in the request body. The workspace is derived from the key. Live keys are prefixed sk_live_ and sandbox keys are prefixed sk_test_. Both use the same base URL and paths; the prefix alone selects the environment. See the Sandbox Guide for sandbox behavior.

Creating an API key

1

Open the control plane

Log in to the iClear control plane at https://mediamagicverify.com
2

Navigate to API keys

Go to Settings → API Keys → Generate New Key
3

Copy your key

The API key will be displayed once. Copy it immediately — you won’t be able to see it again.
4

Store securely

Store your API key in your application’s environment variables, secrets manager, or key vault.

Using your API key

Include your API key in the X-API-Key header of every request:

Checking which workspace a key belongs to

API keys are scoped to a single workspace, and every endpoint takes that workspace implicitly from the key — no request names it. To find out which one you are holding, call GET /api/workspace:
Useful if your integration holds keys for several workspaces, or stores anything keyed by workspace. apiKeyName is the label given to the key when it was created, which helps tell keys apart in your own logs.
Prefer this over deriving an identifier from the key itself. The workspace id is stable across key rotation; a value derived from the key is not.

Security best practices

Never hardcode API keys in your application code or commit them to version control. Always use environment variables or a secrets manager.
  • Store API keys in environment variables or a secrets manager (e.g., AWS Secrets Manager, Azure Key Vault)
  • Rotate API keys regularly — we recommend monthly rotation
  • Use different API keys for different environments (development, staging, production)
  • Monitor API key usage in the control plane to detect suspicious activity
  • Revoke API keys immediately if you suspect they’ve been compromised

Authentication errors

If your API key is missing, invalid, expired, or revoked, you’ll receive a 401 Unauthorized response with a detail message:
The detail message tells you exactly what went wrong. Common messages include:
  • Missing X-API-Key header — no key was sent
  • Invalid API key — the key is not recognized
  • This API key has expired
  • This API key has been revoked
Check that:
  • The header name is exactly X-API-Key (case-sensitive)
  • Your API key is correct and has not expired or been revoked
  • You are using a key for the workspace whose resources you are trying to access

Rate limiting

API requests are rate limited per API key. See Rate Limiting for details.