Creating an Endpoint
Configure Endpoint
Enter a name and optional description for your endpoint.
- Name: A URL-safe identifier (e.g.,
stripe-events,github-hooks) - Description: Optional notes about what this endpoint is for
Endpoint Naming Rules
Endpoint names must follow these rules:- Length: 3-50 characters
- Characters: Lowercase alphanumeric and hyphens only
- Start/End: Must start and end with an alphanumeric character
Valid Names
stripe-eventsgithub-pushmy-webhook-1orders
Invalid Names
ab(too short)-webhook(starts with hyphen)My_Webhook(uppercase/underscore)events/stripe(slashes)
Managing Endpoints
Viewing Endpoints
The Webhooks page in the dashboard shows all endpoints for your workspace, including:- Endpoint name and description
- Endpoint URL for configuration
- Creation date
- Number of deliveries received
Deleting an Endpoint
To delete an endpoint:- Go to Webhooks in the dashboard
- Click on the endpoint you want to delete
- Click Delete Endpoint and confirm
Because historic deliveries are preserved, endpoint names are reserved even after deletion — pick a new name if you need to recreate a similar endpoint.
Configuring External Services
Once you have your endpoint URL, configure your external service to send webhooks to it.Stripe Example
- Go to Developers → Webhooks in your Stripe dashboard
- Click Add endpoint
- Enter your agntdata webhook URL
- Select the events you want to receive
- Click Add endpoint
GitHub Example
- Go to your repository Settings → Webhooks
- Click Add webhook
- Enter your agntdata webhook URL as the Payload URL
- Set Content type to
application/json - Select events to trigger the webhook
- Click Add webhook
Generic Services
Most services have a webhook or callback URL setting. Enter your agntdata endpoint URL:hookId is the endpoint’s unique identifier, returned in the id and
url fields when you create the endpoint.
Security Considerations
Endpoint URLs are Semi-Secret
Endpoint URLs are Semi-Secret
Endpoint URLs are opaque (
/ingest/{hookId}) and not publicly discoverable. However, anyone with the URL can send data to it — treat it like a shared secret.Validate Payloads
Validate Payloads
When processing deliveries, validate that the payload structure matches what you expect from your source service.
Use Webhook Signatures
Use Webhook Signatures
Many services (Stripe, GitHub, etc.) sign their payloads. Store the signature from headers and verify it when processing.
Next Steps
Receiving Webhooks
Learn about webhook payload format and structure.
Managing Deliveries
View and acknowledge webhook deliveries.