Customer State Endpoint & Webhook

[birkjernstrom]

Resource specific API endpoints & webhooks are great and especially for more advanced integrations to have complete control.

However, a lot of customers can go a long way (and much easier) if they could fetch a customer (using their own external ID) to get their complete state vs. having to integrate numerous endpoints. Combined with a webhook for the same "aggregated state" once it changes.

E.g an endpoint+webhook that would return the customer along with:

• Active subscriptions
• Active benefits
• Active meters (soon)

These resources should be "thin" to avoid an unnecessarily large response object, i.e no embedded sub-resources on the above by default unless needed.

In addition, all our events related to these resources which have their own dedicated webhooks should fire a customer_state.changed event (and webhook). We should debounce this to avoid it being fired repeatedly within short succession since a lot of events are async and trigger one another for the same fundamental outcome, e.g subscription created.