Sign in

Get token

GET https://{organization}.myguper.com/api/connect/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.

Headers

Name Type Description
Content-Type * string Always `application/json` for endpoints that accept a JSON body.
x-guper-apikey * string Public identifier of your integration account (issued by Guper).
x-guper-apisecret * string Secret value of your integration account. Treat as a password — never expose to the browser.

Responses

{
    "accessToken": "c074cb9bd30d7b431230877facb45e0a06790e93dea6a728cef9fdaf656bf349",
    "expiresIn":   "2023-08-11T15:13:00-03:00",
    "dateTime":    "2023-08-11T09:13:00-03:00"
}
Copied to clipboard