Create a System Access Token
Create a System Access Token for your company.
The response is the only place the credential appears. access_token is not stored in retrievable form and no
other endpoint returns it, so if it is lost the token has to be deleted and recreated.
The new token’s expiry is rounded down to whole days, so the expires_at you get back can be earlier than the
one you asked for.
Requires write access to access_tokens.
Authorizations
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
Body
The name of the token.
1 - 256The permissions to grant. Omit this to get the default set — read and write on the resources a platform user normally works with.
When the token should expire. Accepts either an RFC 3339 timestamp or a bare YYYY-MM-DD date, which is read
as midnight UTC.
The gap between now and this value must be at least 1 and at most 365 whole days — a value less than 24 hours out rounds down to 0 days and is rejected. Omit it to get the maximum, 365 days.
^\d{4}-\d{2}-\d{2}T"2023-10-31T11:19:13.400498Z"
Response
The token was created. This is the only response that contains access_token.
A newly created System Access Token. This is the only response that carries access_token — store it now,
because no later call returns it and there is no way to recover it.
The id of the token.
The name of the token.
The permissions granted to the token.
When the token expires, RFC 3339. Expiry is stored with day granularity, so this is the requested expiry rounded down to a whole number of days from when the token was created — ask for 36 hours and you get 24.
"2023-10-31T11:19:13.400498Z"
The credential, base64-encoded. Send it as Authorization: Bearer <access_token>.

