Skip to main content
APIContext
Talk to salesStart free
Start HereGuidesConceptsCLIReferenceChangelog

Get a token and try an endpoint

The API Reference pages include a Try-It console that lets you send live requests directly from your browser. This guide walks you through getting your API key and using it to authorize the console.

CORS prerequisite

Try-It sends requests directly from your browser to client.apimetrics.io. For those requests to succeed, the API server must include Access-Control-Allow-Origin: https://docs.apicontext.com in its responses. If you see a network error or a CORS error in the browser console, contact the APIContext team — this is an API platform configuration, not a docs issue.

Step 1: Get your API key​

  1. Log in to client.apimetrics.io.
  2. Open Settings (gear icon in the top-right).
  3. Select API Keys.
  4. Click + New API Key, give it a name, and copy the generated key.

Keep this key safe — it provides full access to your account.

Step 2: Authorize the console​

  1. Open any page in the API Reference.
  2. Click the Authorize button (lock icon, top-right of the page).
  3. In the dialog, paste your API key into the ApiKeyAuth field.
  4. Click Authorize, then Close.

The lock icon turns closed when authorization is stored.

Step 3: Send a request​

  1. Expand any endpoint — for example, List all calls under API Settings.
  2. Click Try it out.
  3. Fill in any required parameters.
  4. Click Execute.
  5. The console shows the full request URL, response code, headers, and body.

A 200 response confirms your credentials are working and CORS is configured correctly.

Troubleshooting​

SymptomLikely cause
Browser shows CORS errorCORS headers missing on client.apimetrics.io — contact API Platform
401 UnauthorizedAPI key not set or expired — re-authorize
403 ForbiddenKey lacks the required permission level
Network error, no responseCORS preflight blocked — same as CORS error above