Scout Camp Developers

REST API + OAuth2

Build on Scout Camp

Approved developers create an OAuth2 application (not tied to a camp). A MASTER account, camp administrator, or leader with the OAuth2 applications permission then authorises it with their camp access code. Tokens never reach billing accounts, medical notes, or family contact details. Camp consent is not collected over the API.

TutorialsCreate a child, submit a registration, pull people safely.Request rulesComma-separated tags, booleans, and what each scope accepts.ScopesPass and return fields for every OAuth scope.OAuth2Authorization code + refresh tokens, locked to a camp.REST APIRegistration URLs, people, sub-camps, and module data.PrivacySubmit personal details. You cannot pull them back.

Quick start

  1. Apply for a developer account. Staff approve applications from admin.scoutcamp.co.uk.
  2. Create an OAuth2 application (name, logo, redirect URIs).
  3. Send camp users to the authorize URL on scoutcamp.co.uk. They enter their camp access code and sign in as they would on the website.
  4. Exchange the code at /oauth/token and call /api/v1.
Tag fields. When you create a young person or submit a registration, send dietary needs, allergies, and disabilities as comma-separated values (or a JSON array). See request rules.