keys.create

Create an API key

POST/keys

Operation: keys.create
MCP tool: not exposed over MCP

Mint a key for this account. The plaintext is in the response and nowhere else: it is never stored in readable form and cannot be recovered. A key may hold any scope except keys:manage: a credential that could create credentials would outlive its own revocation. At most 25 active keys per account.

curl -X POST "https://api.gogoscreen.com/api/v1/keys" \
  -H "Authorization: Bearer $GOGOSCREEN_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{ "name": "<name>", "scopes": [ "<scopes>" ] }'

The shape of a request to this operation. The dashboard sends it with the signed in person's session; an API key is refused.

At a glance

Fact	Detail
Scopes	`keys:manage`
Credentials	a signed in dashboard session. An API key cannot be granted these scopes, so this operation is reachable only from a signed in dashboard session.
Rate limit	120 requests a minute per credential, in the `write` class.
Idempotency	Required. Send an `Idempotency-Key` header; a retry with the same key and the same body returns the stored answer with `Idempotent-Replayed: true`. How idempotency works.
MCP tool	Not exposed over MCP.
Always sets	`Cache-Control: private, no-store`
Verified email	Required. An account whose email address is not verified meets `403 email_unverified` before the operation runs.
Audit	Every call is written to the audit log as `api_key_management`.

Request body

A JSON body is required. Unknown fields are refused rather than ignored, so a typo is a 400 validation_failed rather than a setting that silently did nothing.

Name	Type	Required	Description
name	string	Required	What this key is for. Shown in the console and in the account's audit trail.1–120 characters
scopes	string[]	Required	What the key may do. At least one, and from this list only: two scopes are never on it. `keys:manage` is withheld because a key that could mint keys would outlive its own revocation, and `assistant:use` because the in-app assistant is for people in the dashboard, not for integrations.1–12 items
expiresAt	string \| null	Optional	When the key stops working. Omit for a key that does not expire.format: date-time
rateLimitPerDay	integer \| null	Optional	A daily request cap for this key alone (up to 864000, the per-minute ceiling run for 24 hours).1–864000
rateLimitPerMinute	integer \| null	Optional	A ceiling below the rate class's own. Cannot raise it.1–600

Response

Answers 200. Every answer also carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset, and every error body carries a requestId.

200 OK

Create an API key

Name Type Description

apiKey object

12 fields inside apiKey

Name	Type	Description
createdAt	string	format: date-time
expiresAt	string \| null	format: date-time
id	string
last4	string	The last four characters, for telling two keys apart in a list.
lastUsedAt	string \| null	Written at most once a minute, so it is accurate to the minute and not to the request.format: date-time
name	string
prefix	string	`gsk_live_` plus the first eight characters of the secret. Enough to recognise a key; not enough to use one.
rateLimitPerDay	number \| null	A per-key daily cap. Null means uncapped by the key itself.
rateLimitPerMinute	number \| null	A per-key ceiling. Null means the rate class's own limit applies; a number can only ever lower it.
revokedAt	string \| null	format: date-time
scopes	string[]
status	string	one of: active, revoked, expired

key string THE KEY. This is the only time it is shown: it is never stored in readable form and cannot be recovered. Save it now; if it is lost, rotate.

200 OK headers
Header	Meaning
`Cache-Control`	Always `private, no-store`.
`Idempotent-Replayed`	Present only when this answer was stored by an earlier call with the same Idempotency-Key. Nothing new was done.

Errors

Every refusal is { error: { code, message, details?, requestId } }. Branch on code, never on the sentence. The full catalogue is at Errors.

Code	Status	When it happens	What to do
idempotency_key_required	400	A mutating operation arrived over HTTP with no `Idempotency-Key` header. It is refused before the body is parsed, so a caller missing both learns about both at once.	Add an `Idempotency-Key` header of up to 128 characters, unique to this request. Over MCP the same value goes in the `idempotencyKey` tool argument.
validation_failed	400	The merged path, query and body did not match the operation's schema. The schemas are strict, so an unknown field is a failure rather than something ignored, and a string carrying half of a character is refused before it can be stored.	Read `details.issues`. Each entry carries a `path`, a `message` and a machine readable `code`. Fix every named field and send the request again; the same body always fails the same way.
unauthorized	401	No credential was presented, or the key is unknown, revoked or expired, or an `X-API-Key` header carried something that is not an API key. `details.reason` says which.	Send `Authorization: Bearer gsk_live_…`. A revoked or expired key never starts working again, so issue a new one in the developer console. Put a dashboard session token in `Authorization`, never in `X-API-Key`.
email_unverified	403	The operation declares a verified email and the owning account's address is not verified. A key reads the account's current fact, not the fact that was true when the key was issued.	Verify the address on the account, then retry. The key does not need to be reissued.
forbidden_scope	403	The credential does not carry every scope the operation declares, or it is the wrong kind of credential for it. `keys.` and `assistant.` are user only and can never be called by a key.	`details.requiredScopes` and `details.missingScopes` name what is missing. A key's scopes cannot be changed after it is issued, so create a new key with them. When `details.allowedActors` is present, no key can call this operation at all.
not_found	404	No resource of that id belongs to this account. A resource that belongs to somebody else answers 404 as well, never 403.	Check the id. Do not treat this as a permissions problem.
conflict	409	The request conflicts with the state the resource is in, and no more specific code applies.	Re-read the resource and decide from its current state. Retrying the same request unchanged will not help.
idempotency_conflict	409	That idempotency key has already been used on this operation with a different request body.	Use a fresh key for a different request. A key stands for one intent, not for one attempt.
idempotency_in_progress	409	The first request under that key is still being worked. Two concurrent identical requests both reach the store and one of them is told this.	Wait the `Retry-After` seconds, which is 2, and send exactly the same request again with the same key. Do not change the body and do not mint a new key.
payload_too_large	413	The request body is over the transport's limit: 256 kb over HTTP, 1 mb over MCP.	Send less. `details.limit` carries the limit. Version 1 has no upload operations, so a body this size is usually a mistake.
unsupported_media_type	415	The request carried a body whose `Content-Type` is not `application/json`, whose charset is not utf-8, or whose `Content-Encoding` this API does not decode. A body nobody can read would otherwise be silently discarded.	Send `Content-Type: application/json` and utf-8 bytes. `details` names the charset, encoding or content type that was objected to.
rate_limited	429	The credential's per minute budget, the account's per minute ceiling, or a daily cap was exceeded. `details.scope` is `minute`, `day` or `account`, or `global` when the product's own daily cap on voice previews is spent.	Wait the `Retry-After` seconds and retry. `details.limit` and `details.resetAt` say what was hit and when it reopens. The `RateLimit-*` headers on every answer let a client pace itself before it gets here.
internal_error	500	An unhandled failure inside this API. The original message is logged and never answered.	Retry once, then quote `requestId` to support. A 5xx deletes the idempotency claim rather than storing it, so retrying under the same key is safe.