Tutorials
Integrate with COUNT
The whole partner integration end to end: register an app, send a user through OAuth, exchange the code for a workspace token, sign a request, and read their books.
5 steps · about 43 seconds · from registering an app to your first signed call
What you just saw
- 1The client secret is shown onceCOUNT Partners displays it on creation and never again. Copy it then, or re-roll it — and store it server-side, because it signs every request and is never sent over the wire.
- 2Redirect URLs must match exactlyThe authorization request is rejected if its redirectUri is not one you registered. This is the most common reason a first OAuth attempt fails.
- 3The token is scoped to the workspaces the user tickedConsent is per workspace, not per account. Store the access token against the workspace it covers rather than against the user.
- 4The signed path drops the /partners prefixThe base string is METHOD:path:timestamp:bodyHash, where path is relative to the mount — so /partners/customers signs as /customers. A GET signs an empty body hash.