API keys and Zapier

A key lets Zapier or another tool add members, send in payments for an officer to approve, and switch webhooks on for itself.

An owner makes a key under Connections, gives it a name, and copies it once. renuzy keeps only a scrambled copy, so it cannot show it again. Revoke a key at any time; anything using it stops at once, and webhooks it switched on stop with it.

With a key, a tool can:

• Add a member. They come in as not yet active, as when an officer adds them. Someone already on your list is not added twice.
• Record a payment. It waits on Payment claims for an officer to approve, like a member saying they paid. Nothing from outside renuzy writes a payment by itself.
• Hear about happenings, the same as a webhook.

The renuzy app in Zapier's list is on its way. Until it is there, use Zapier's own Webhooks by Zapier: its Catch Hook step gives you an address to add as a webhook.

For developers

Send the key as Authorization: Bearer rzk_.... GET /api/v1/me checks it. POST /api/v1/members takes first_name, last_name, email, phone. POST /api/v1/payments takes email or member_id, amount, method, paid_on. POST /api/v1/hooks with target_url and event subscribes, DELETE /api/v1/hooks/ID unsubscribes. 120 requests a minute per key.