Praecise account/ Reference/ Service tokens

Mint a service token

post/api/tokens

The only time the token itself is readable. A signed-in person only: a token that could mint its successors would make revoking the original pointless.

Before you call

Credential: Authorization: Bearer $KEY

Request bodyapplication/json, required

namestringrequired
At most 80 characters.

Responses

201application/json
Minted.
- namestringrequired
- tokenstringrequired
  Starts prc_. Shown once.
- notestringrequired
400application/json
The token needs a name of 1 to 80 characters.
- errorstringrequired
  What went wrong, in a sentence.
- detailstring
401application/json
Nobody is signed in.
- errorstringrequired
  What went wrong, in a sentence.
- detailstring
403application/json
A service token was presented. Tokens are managed by a signed-in person, not by another token.
- errorstringrequired
  What went wrong, in a sentence.
- detailstring

Example request

curl -X POST 'https://accounts.praecise.com/api/tokens' \
  -H 'Authorization: Bearer $KEY' \
  -H 'Content-Type: application/json' \
  -d '{
  "name": "my-service, production"
}'

$KEY stands for your own key. No key is shown or kept on this site.

This page as Markdown