warden

Integrate

Test before production

Rehearse with a dry run, and send synthetic records to a test organization.

Rehearse against your real key

A dry run is a real request with a real key that stores nothing. It is the right first call against production, and the right way to look at a first import before it happens.

Send synthetic records to a test organization

There is no self-serve sandbox yet. Ask for a key in a Warden test organization under a provider name of your own, and send synthetic records to it. Use trading names and addresses that belong to nobody, such as example.com domains.

A key in a test organization behaves exactly as one in a real organization does, including the request allowance.

What to check

  1. A record with an email address in a field of its own is refused by name, and the rest of the batch is written.

  2. Sending the same batch twice changes no public_id.

  3. A lapsed member's page still resolves, and says the membership is not active.

  4. A revoked key answers 401 at once.

  5. Your client waits for Retry-After on a 429.