Send a test webhook delivery
Deliver one signed test event to your endpoint so you can verify your handler without waiting for a real event.
What gets sent
The delivery is identical to a live one — same headers, same signature scheme, and the same envelope with the event payload indata — with two differences that let you tell it apart:
- The envelope carries
"test": true. - The event ID starts with
evt_test_.
data is your most recent event of this type from the last 30 days when you have one, and the documented example payload for a dummy profile otherwise — payload_source in the response says which. Either way the field names, shapes and caps match a live delivery, so a handler written against a test delivery works unchanged against the real one. Verify the signature exactly as you would for a live delivery: see Events & signatures.
Omit event_type to test the first event type the endpoint subscribes to. Slack incoming-webhook endpoints receive the same formatted Slack message a live delivery would.
Reading the result
A200 means Orbit attempted the delivery and is reporting the outcome — including a failure on your side:
delivered is true only when your server answered 2xx. When it never answered, response_status is null and error carries the reason, for example ECONNREFUSED or timeout of 10000ms exceeded.
Authorizations
Use an Orbit API key from the developer dashboard.
Path Parameters
The webhook endpoint ID returned at creation.
Body
Optional. Defaults to the first event type the endpoint subscribes to; must be one of its subscribed types.
profile.updated, company.thesis.changed, company.alert, portfolio.changed Response
The delivery was attempted. A non-2xx response from your server is reported here, not as an API error.
The delivery ID sent in x-orbit-webhook-event-id. Test deliveries always start with evt_test_.
profile.updated, company.thesis.changed, company.alert, portfolio.changed recent_event when the body replayed your most recent event of this type from the last 30 days, example when it carried the documented example payload.
recent_event, example True when your server answered 2xx.
How long the attempt took, in milliseconds.
The endpoint URL the test was delivered to, redacted the same way list responses redact it.
The HTTP status your server returned, or null when the request never completed.
Why the delivery failed, for example http_500 or ECONNREFUSED. Null on success.
