1. Make your first call
Open a terminal and paste this. It uses the public sandbox key, so it works straight away.expiresAt: nullmeans the key never expires.environmentsays which Scoutworks answered.demoholds only made-up people. Your own key saysproduction.links.tryis a good second call. It is always a list that your key may read.
| jq to the end of the command to make it readable, if you have jq.
No terminal? Open GET /me in the API reference, paste the sandbox key into the Authorization box, choose the Demo server and press Send.
2. Read a list
{ "data": [...], "nextCursor": "..." }. To get the next page, see Pagination.
3. Create your own key
1
Join the beta
The API is in beta. A group admin turns it on in Settings → Beta programme, or asks us to join.
2
Open the API keys page
In Scoutworks, go to Settings → Integrations → API keys. Only a group admin can see this page.
3
Create a key
Give the key a name that says what it is for, for example “Membership spreadsheet”. Choose only the scopes it needs. You can set an expiry date.
4
Copy the key
Scoutworks shows the key once. Copy it into your tool straight away. If you lose it, revoke it and create a new one.
5
Swap it in
In any recipe, replace the sandbox key with your key, and
api-demo.scoutworks.app with api.scoutworks.app. The Test connection button on the key page checks that the key works.Next
Recipes
Google Sheets, Excel, n8n, Zapier, Python and curl.
Keys and scopes
What each scope unlocks, and when a key stops working.