Authentication

Every request to the Remux API must be authenticated. You can use an API key (for programmatic access) or a Clerk session (for the dashboard UI).

API keys

API keys start with nte_ and are 52 characters long. You create them in the dashboard and they’re shown only once — copy the full key when it’s displayed.

Sending your key

You can pass your API key in either of two headers:

curl https://remux.recaststudio.ai/api/v1/jobs \
  -H "Authorization: Bearer nte_your_api_key_here"

curl https://remux.recaststudio.ai/api/v1/jobs \
  -H "X-API-KEY: nte_your_api_key_here"

const response = await fetch('https://remux.recaststudio.ai/api/v1/jobs', {
  headers: {
    'Authorization': 'Bearer nte_your_api_key_here'
  }
});

import requests

response = requests.get(
    "https://remux.recaststudio.ai/api/v1/jobs",
    headers={
        "Authorization": "Bearer nte_your_api_key_here"
    }
)

Both methods are equivalent. Use whichever fits your HTTP client best.

Creating a key

Sign in at remux.recaststudio.ai/app
Go to Dashboard → Tokens
Click Create Token and give it a name (e.g., “Production API”)
Copy the full key immediately — it won’t be shown again

Revoking a key

In Dashboard → Tokens, click the delete button next to any key. Once revoked, all requests using that key will receive a 401 response immediately.

Dashboard sessions

The web dashboard at /app uses Clerk for authentication. When you interact with the dashboard, it calls the same /api/v1/* endpoints using your Clerk session token — no API key needed.

This means you can test API endpoints from the dashboard UI with the same data your API keys access.

Error responses

If authentication fails, the API returns a 401 status with this JSON body:

{
  "error": {
    "code": "UNAUTHORIZED",
    "message": "Authentication required. Provide a valid Bearer token or sign in via the dashboard.",
    "retryable": false
  }
}

Common causes:

Missing Authorization or X-API-KEY header
Key doesn’t start with nte_
Key has been revoked
Key was copy-pasted incorrectly (check for trailing spaces)

CORS

Browser requests are allowed from the configured dashboard origin (set via REMUX_PUBLIC_ORIGIN). If CORS is not configured, all origins are allowed.

The API accepts these headers in cross-origin requests:

Authorization
Content-Type
X-API-KEY