Create API key

POST/v1/admin/keys

How to call this endpoint

Every ACP API request uses bearer authentication. The examples here show the actual request path, auth header, and body shape that the platform expects.

Path, query, and header parameters

These parameters control which ACP object the endpoint acts on and how the request is processed.

Path parameters
None.
Query parameters
None.

Body schema

Content type: application/json · Required

FieldTypeRequiredDescription
namestringYesHuman-readable name.
descriptionstringNoHuman-readable description.
prefixstringNo
keyTypestandard | internalNo
userIdstringNoUser ID.
expiresInintegerNoExpiration window in days.
scopesstring[]No
metadataobjectNoFree-form metadata object.

What the API returns

Each response code below includes the documented payload shape for the ACP API.

201API key createdapplication/json
FieldTypeRequiredDescription
idstringNoUnique identifier.
keyPrefixstringNo
keyTypestandard | internalNo
namestringNoHuman-readable name.
descriptionstringNoHuman-readable description.
userIdstringNoUser ID.
createdAtstringNoISO 8601 timestamp.
lastUsedAtstringNoISO 8601 timestamp.
expiresAtstringNo
isActivebooleanNo
scopesstring[]No
metadataobjectNoFree-form metadata object.
keystringNoPlaintext API key. Returned exactly once at creation time.
warningstringNo
Create API key
Loading...
Response 201
Loading...
See the ACP quickstart and SDK flow