Does webhook expect basic authentication? If true it means you created this webhook with a username and password. MailSlurp will use these in the URL to authenticate itself.
WebhookDto
When the webhook was created
WebhookDto
Optional
eventWebhook trigger event name
WebhookDto
ID of the Webhook
WebhookDto
Optional
ignoreShould notifier ignore insecure SSL certificates
WebhookDto
Optional
inboxThe inbox that the Webhook will be triggered by. If null then webhook triggered at account level or phone level if phoneId set
WebhookDto
HTTP method that your server endpoint must listen for
WebhookDto
Optional
nameName of the webhook
WebhookDto
Deprecated. Fetch JSON Schema for webhook using the getJsonSchemaForWebhookPayload method
WebhookDto
Optional
phoneThe phoneNumberId that the Webhook will be triggered by. If null then webhook triggered at account level or inbox level if inboxId set
WebhookDto
Optional
requestRequest body template for HTTP request that will be sent for the webhook. Use Moustache style template variables to insert values from the original event payload.
WebhookDto
Optional
requestWebhookDto
WebhookDto
URL of your server that the webhook will be sent to. The schema of the JSON that is sent is described by the payloadJsonSchema.
WebhookDto
Optional
useShould notifier use static IP range when sending webhook payload
WebhookDto
User ID of the Webhook
WebhookDto
Representation of a webhook for an inbox. The URL specified will be using by MailSlurp whenever an email is received by the attached inbox. A webhook entity should have a URL that points to your server. Your server should accept HTTP/S POST requests and return a success 200. MailSlurp will retry your webhooks if they fail. See https://api.mailslurp.com/schemas/webhook-payload for the payload schema.
Export
Interface
WebhookDto