Thanks for operating the best product. It has really helped me a lot.
Syncing Subscription Status
Webhooks are commonly used to sync a customer's subscription status across multiple systems. Because different webhook events contain unique information, we recommend calling the
GET /subscribersREST API endpoint after receiving any webhook. That way, the customer's information is always in the same format and is easily synced to your database. This approach is simpler than writing custom logic to handle each webhook event, and has the added benefit of making your system more robust and scalable.
It is recommended to call the REST API after receiving the webhook.
If you follow the recommendation and refer to the latest REST API v2 documentation, the `GET/subscribers` entry is not present.
The v1 documentation had a `GET/subscribers` entry.
Does this mean that v2 cannot retrieve customer information based on user ID?
If I want to get customer information based on user ID, do I have to use v1?
Also, Webhook authorization is recommended, but it appears to be unavailable with v1.
What are the current best practices?
Best Practices: Webhook authorization
We recommended setting an authorization header value via the RevenueCat dashboard. When set, RevenueCat will send this header in every request. Your server can use this to authenticate the webhooks from RevenueCat.