Set up webhooks for legacy recurring payments to receive start and end event notifications
Setting up a Pay Stream
Pay Streams are recurring payments, great for subscriptions or gated content.
NOTE: When using the production environment (app.hel.io), set your API endpoint to api.hel.io/v1 and generate API keys there. For the development environment, use api.dev.hel.io/v1 and generate API keys from app.dev.hel.io.
API Endpoint: https://api.hel.io/v1/webhook/stream/transaction
You can retrieve the streamId from the end of your Pay Stream URL. For example, in the URL https://app.hel.io/s/636a74162e72d4ad24ac9ce9, the streamId is 636a74162e72d4ad24ac9ce9
For streamId: 636a74162e72d4ad24ac9ce9, a similar curl command can be used to register recurring payment webhooks. The POST request is sent to targetUrl: https://target-url.com/post-endpoint.
You can list all the webhooks that have been created for a pay stream.
NOTE: When using the production environment (app.hel.io), set your API endpoint to api.hel.io/v1 and generate API keys there. For the development environment, use api.dev.hel.io/v1 and generate API keys from app.dev.hel.io.
API Endpoint: https://api.hel.io/v1/webhook/stream/transaction
This will return an array of all Webhooks that are registered for the Pay Stream. In case the API key isn't associated with stream, an unauthorised request error will be thrown.