Skip to content

Key Request

Users without an API key can submit an access request via this public endpoint. Submissions are queued for operator review. By default, keys are not issued automatically — an operator must approve each request and provision the key manually.

Endpoint: POST /access/request-key

Authentication: None

{
"email": "user@example.com",
"use_case": "Building a customer support chatbot for an e-commerce store."
}
FieldTypeRequiredDescription
emailstringYesContact email for the requester
use_casestringYesBrief description of how the API will be used

A successful submission returns HTTP 202 Accepted with a request_id you can reference when following up.

{
"request_id": "kreq_01j9xkz3p4q5r6s7t8u9v0w1",
"status": "pending",
"message": "Your request has been received. An operator will review it and reach out to you at user@example.com."
}
FieldTypeDescription
request_idstringUnique identifier for this access request
statusstringAlways "pending" at submission time
messagestringHuman-readable confirmation
  1. User submits POST /access/request-key with email and use case.
  2. The gateway stores the request and returns a request_id.
  3. An operator reviews the submission out-of-band.
  4. If approved, the operator provisions a Bearer token and delivers it to the requester’s email.

There is no polling endpoint — the operator contacts the requester directly once the key is ready.

Terminal window
curl -X POST https://your-gateway.workers.dev/access/request-key \
-H "Content-Type: application/json" \
-d '{
"email": "user@example.com",
"use_case": "Building a customer support chatbot for an e-commerce store."
}'
StatusDescription
400Missing or invalid email / use_case field
429Too many requests from this IP — try again later