Get token
Issues a new access token for an integration. Uses the API Key + API Secret
pair issued during account setup — not the user x-guper-authorization
token (this endpoint is what produces it). The returned accessToken is
sent on every subsequent request as x-guper-authorization.
Mind expiresIn. A token presented after that moment is refused with
401 and Code: E0002 by every endpoint that takes
x-guper-authorization — call this endpoint again to get a fresh one.
Asking for a new token before the current one expires is fine and does not
revoke it.
Wrong credentials answer 401. After 8 failed attempts for the same
key and origin IP this endpoint answers 429 for 15 minutes; other
callers of the same organization are not affected.
Try-it values populated from environment ACME (Demo)
Authentication
Apikey
Send your x-guper-apikey + x-guper-apisecret credentials. Do not send
x-guper-authorization — this endpoint issues it.