Add a notification endpoint
Notification
Add a notification endpoint
POST
Add a notification endpoint
Registers an HTTPS endpoint to receive webhook notifications. Return Helper sends a verification request to the URL before storing it — registration succeeds only if your endpoint answers.
Endpoint requirements
All of the above are checked before the verification request is sent, so a rejected request never reaches your server.
The endpoint receives every event
A registered endpoint receives all notification events for your account. There is no per-event subscription or filter on the Return Helper side. Filter on your side: read thecategory and action fields from the notification body and ignore the events you do not handle. Acknowledge every request with a 2xx status even when you ignore it — a non-2xx response counts as a failed delivery and repeated failures suspend delivery to your endpoint. See Retry Mechanism.
Get HTTP notification action types for users lists the action values you can expect.
Verification request
Before the endpoint is stored, Return Helper sends aPOST to the URL you supplied. It carries a fixed sample payload in the shape of a label generated notification and the complete set of notification headers, including a valid ReturnHelper-Signature — so your handler and your signature check can be exercised end to end before you go live.
Registration succeeds only if your endpoint returns a 2xx status within 30 seconds. Any other status, a timeout, a DNS failure, a refused connection or a TLS error fails the call, and the endpoint is not stored.
The IDs and values in the verification payload are samples — they do not refer to real objects in your account. Make sure your handler tolerates unknown IDs, or acknowledge the request before processing it.
The stored URL
Theendpoint value in the response is the normalized URL — the exact string Return Helper stores, and the string later duplicate checks compare against. It can differ from what you submitted. Keep the returned value, not your own input.
Idempotency
Thex-returnhelper-idempotency-key header is optional. A call without it runs normally, with no protection against duplicates. See Idempotency.
Errors
Every failure below arrives as HTTP200 with meta.status 400, meta.errorCode VALIDATION_FAILED, and the message under meta.error.endpoint.
Related
- List notification endpoints
- Delete a notification endpoint
- Webhooks — event list, payloads and signature verification.
Authorizations
Your API key
Your API token — keep this private
Body
application/json
HTTPS URL to receive webhook notifications. Maximum 255 characters after normalization, must be publicly reachable, and must answer the verification request with a 2xx status within 30 seconds.
Example:
"https://acme.example/hooks/returnhelper"
Response
Success — data carries the stored endpoint and its identifier. The endpoint value is the normalized URL that Return Helper stored, which can differ from the submitted value.