The authorization-code flow for apps that sign your customers in to Shout About Us — they enter their password on our page, your server gets a token.
The authorization-code flow for apps that sign your customers in to Shout About Us — they enter their password on our page, your server gets a token.
Prerequisites
- A bearer token in the
Authorizationheader. Any endpoint that needs no token says so on its own page. - The id of each record the call targets. Every endpoint page lists the ids it needs.
Errors
| Status | Meaning |
|---|---|
401 | The bearer token is missing, expired or invalid |
403 | The token is valid but the record sits outside your account |
422 | The request failed validation — the response names the fields |
500 | Unexpected server error |
Individual endpoints may return more; each page lists its own.
Endpoints
| Method | Endpoint | Description |
|---|---|---|
GET | Step 1: Send the user to sign in | Step 1 — Authorize (browser redirect, documentation) |
POST | Step 3: Exchange the code for a token | Step 3 — Exchange code for token |
GET | Revoke a token | Revoke token |