Get an API key with an email (no dashboard, no prior signup)

curl --request POST \
  --url https://api.juicer.io/v1/authorize \
  --header 'Content-Type: application/json' \
  --data '
{
  "email": "ai-dev@example.com",
  "client_name": "Acme CLI"
}
'

{
  "status": "issued",
  "api_key": "jcr_9f...ab",
  "expires_at": "2023-11-07T05:31:56Z",
  "email_confirmation_required": true,
  "rate_limit": {
    "requests_per_hour": 60,
    "burst_per_minute": null
  },
  "upgrade_hint": "Confirm your email to raise your rate limit to 300 requests/hour and extend this key to 12 hours.",
  "upgrade_url": "<string>"
}

Quickstart

Get an API key with an email (no dashboard, no prior signup)

Provision an API key using just an email address. The behavior depends on whether the email already belongs to a confirmed Juicer account:

New or unconfirmed email — returns a short-lived (2 hour) temporary API key immediately (Mode A). Subject to a strict per-key rate limit until the user confirms the email we send. Once confirmed the same key is extended to the standard 12-hour session TTL — it is not promoted to a permanent key.
Existing confirmed user — returns a device authorization request (Mode B) with an authorization_url the user must visit to approve access. Poll poll_url until the key is issued. The resulting key is also a 12-hour temporary key.

Every key issued by this endpoint is time-bounded. For a long-lived key, users should generate one from the Developer page in the Juicer dashboard; that is the only path to a permanent key. The dashboard key and any number of /authorize-issued keys coexist — issuing a new session key never revokes an existing permanent or session key.

POST

authorize

Get an API key with an email (no dashboard, no prior signup)

curl --request POST \
  --url https://api.juicer.io/v1/authorize \
  --header 'Content-Type: application/json' \
  --data '
{
  "email": "ai-dev@example.com",
  "client_name": "Acme CLI"
}
'

{
  "status": "issued",
  "api_key": "jcr_9f...ab",
  "expires_at": "2023-11-07T05:31:56Z",
  "email_confirmation_required": true,
  "rate_limit": {
    "requests_per_hour": 60,
    "burst_per_minute": null
  },
  "upgrade_hint": "Confirm your email to raise your rate limit to 300 requests/hour and extend this key to 12 hours.",
  "upgrade_url": "<string>"
}

Body

application/json

string<email>

required

Example:

"ai-dev@example.com"

client_name

string

Optional free-text name of the calling application. Shown verbatim on the authorization page for Mode B (for example "Acme CLI" or "My Feed Tool"). If omitted, the page uses a generic fallback.

Example:

"Acme CLI"

Response

Mode A — temporary API key issued immediately. Valid for 2 hours pre-confirmation; extended to 12 hours once the user confirms their email. expires_at is always present.

status

string

Example:

"issued"

api_key

string

Example:

"jcr_9f...ab"

expires_at

string<date-time>

email_confirmation_required

boolean

Example:

true

rate_limit

object

The rate limit tier applied to this pre-confirmation key

Show child attributes

upgrade_hint

string

Example:

"Confirm your email to raise your rate limit to 300 requests/hour and extend this key to 12 hours."

upgrade_url

string<uri>

Link to the plans page where the user can upgrade

Poll the status of a device authorization request