Quickstart
Get an API key and make your first request.
API reference
Browse the complete API reference.
The integration model
The API is deliberately simple:- Get an API key from Peoplewisher → Settings.
- Create or identify the Celebration Group you want to use.
- Send your contacts to Peoplewisher and assign each contact to its group.
- Peoplewisher continues the workflow automatically.
What your application owns
Your application remains the source of truth for your own users and customer records. Use the API to keep the relevant Peoplewisher contact data synchronized and to place each person in the appropriate group.What Peoplewisher owns
Peoplewisher owns the celebration workflow after the contact is in the group:- celebration timing
- email, SMS, and WhatsApp configuration
- templates and message content
- group celebration settings
- delivery processing
- delivery reporting
Built for SaaS and multi-tenant applications
Peoplewisher can be used by a SaaS application that serves multiple organizations or customers. A common model is:group_id values.
If each customer needs an independently managed Peoplewisher account, each account can use its own Peoplewisher API key.
Do I need to build the workflows?
No. You do not need API calls for:- creating message templates
- writing the SMS message
- writing the email
- configuring WhatsApp messages
- choosing delivery times
- enabling or disabling channels
- changing celebration settings for a group
What happens after I create a contact?
Once the contact is created in a Celebration Group, PeopleWisher’s existing automation engine can process the contact according to that group’s configuration. For example, if a group is configured for birthday celebrations with email and WhatsApp enabled, adding a person with a birthday to that group is enough for Peoplewisher to handle the configured workflow.Supported channels
Peoplewisher supports:- SMS
Enterprise capabilities
Some platform capabilities are available by Enterprise agreement:- outbound webhook access
- delivery-status forwarding to your HTTP endpoint
- higher-volume or specialized API requirements
