Export webhooks let you receive mapping results automatically instead of polling for them. When Mapping.Travel completes a mapping export, it sends a POST request to each active webhook URL you have configured. You can register multiple webhooks, enable or disable them individually, and update them at any time.Documentation Index
Fetch the complete documentation index at: https://docs.mapping.travel/llms.txt
Use this file to discover all available pages before exploring further.
All webhook endpoints require authentication. Include your bearer token in the
Authorization header.POST /api/v1/export-webhooks
Create a new webhook configuration.Request body
The HTTPS endpoint that will receive webhook payloads. Must be a publicly reachable URL.
Whether the webhook is active immediately after creation.
Optional signing secret used to verify webhook payloads on your server.
Response
Returns200 OK with the created webhook configuration.
UUID of the webhook configuration.
The configured endpoint URL.
Whether the webhook is currently active.
ISO 8601 timestamp of creation.
Example
GET /api/v1/export-webhooks
List all webhook configurations for your organization.Query parameters
When
true, only active webhook configurations are returned.Response
Array of webhook configuration objects.
Example
GET /api/v1/export-webhooks/
Retrieve a single webhook configuration by ID.Path parameters
UUID of the webhook configuration.
Example
PUT /api/v1/export-webhooks/
Update an existing webhook configuration. All request body fields replace the current values.Path parameters
UUID of the webhook configuration to update.
Request body
New endpoint URL.
Whether the webhook should be active.
Updated signing secret.
Example
DELETE /api/v1/export-webhooks/
Delete a webhook configuration. The webhook will stop receiving payloads immediately.Path parameters
UUID of the webhook configuration to delete.
Response
Returns204 No Content on success. The response body is empty.