Version 1
Partner API
Add your people to a sponsored Active Giving team and send us their workouts. Each workout becomes real impact, like trees planted, ocean restored or plastic removed, paid for by the team's sponsor. Your people never have to install our app.
Quickstart
Add a person and log their first workout in five minutes.
Playground
Send real calls to staging from your browser with your test key.
API reference
Every endpoint, field and response in one place.
How it works#
- 1
We set you up
We create your partner account, link it to your sponsored team and send you a staging key. - 2
You add your people
Send each person's name and email toPOST /users. They join your team straight away and we send them a welcome email that explains what happens with their data. - 3
You send their workouts
When a workout finishes, send it toPOST /activities. The response says at once whether it counted and how much impact it made. Nothing waits in a queue. - 4
You show the impact
Read the totals for one person or the whole team and show them in your product.
Environments#
Each key works in one environment only. Build and test on staging, then switch the base URL and the key when you go live.
| Environment | Base URL | Key starts with |
|---|---|---|
| Staging | https://dyb5ahy4siv91.cloudfront.net/partner/v1 | ag_test_ |
| Production | https://partner.activegiving.de/v1 | ag_live_ |
- Staging. For building and testing. Workouts create impact on paper only: nothing is planted, restored or removed. Only email addresses we allow can be added: send us the ones you test with.
- Production. Real people, real impact. We issue a live key once your integration passes the go-live checklist.
Conventions#
- JSON over HTTPS. Send
Content-Type: application/jsonwith every body. - Times are ISO 8601. Send them with an offset, like
2026-10-14T07:30:00+02:00. Responses always use UTC, like2026-10-14T05:30:00Z. - Distance in meters, duration in seconds, energy in kilocalories.
- Impact is counted in units (trees, ocean, plastic), never in money.
- Lists come a page at a time:
pagestarts at 0 andsizegoes up to 200. - The version is in the path. New fields can appear in responses at any time, so ignore fields you do not know. A breaking change ships as
/v2, with 6 months notice before v1 stops.