Going live

Checklist#

• Your key stays on your servers

  Not in an app, a browser, a log line or a repository.

• You told your people

  They know you are adding them to Active Giving and that a welcome email is coming.

• Each workout has a stable externalId

  The same workout always carries the same ID, and a timeout or 5xx is retried with it.

• You handle 429 and 503

  You wait (for Retry-After when it is sent) and send again, instead of failing or hammering.

• You handle refused workouts

  A 409 daily_limit_reached or 409 overlapping_activity is not stored. You show the reason to the person and do not retry it in a loop.

• You stop sending for people who left

  A 409 person_unlinked, or a lookup that says ENDED, means they left. You stop sending for them, and never add someone again whose lookup answers 404 user_not_found after you added them.

• You only send accepted types

  You map your workout types to the keys in Get your team, and skip the rest.

• You log request IDs

  X-Request-Id is stored with each call, so we can trace any problem together.

Switching to production#

Change two things: the base URL to https://partner.activegiving.de/v1 and the key to your ag_live_ key. Everything else stays the same. People and workouts on staging do not carry over.