Webhooks notify your application when entities are created, updated, or deleted in Mokapen. Use them for event-driven integrations instead of polling the REST API.
Register a webhook URL and select the events you want to receive. When an event occurs, Mokapen sends an HTTP POST request to your endpoint with a JSON payload.
Webhook management endpoints require a valid Bearer token with appropriate scopes.
GET /api/webhooks
POST /api/webhooks
PUT /api/webhooks/{webhook_id}
DELETE /api/webhooks/{webhook_id}
GET /api/webhooks/{webhook_id}/logs
GET /api/webhook-events
Send a POST request with your callback URL, organization ID, and selected events:
POST /api/webhooks
Authorization: Bearer YOUR_ACCESS_TOKEN
Content-Type: application/json
{
"url": "https://example.com/webhooks/mokapen",
"org_id": 849,
"events": ["task.created", "task.updated", "contact.created"]
}
Verify incoming webhook requests on your server. Use HTTPS endpoints only. Store webhook secrets securely and validate payloads before processing.
When registering a webhook, you can subscribe to one or more of the following event types:
task.createdtask.updatedtask.deletedproject.createdproject.updatedproject.deletedcontact.createdcontact.updatedcontact.deletedcompany.createdcompany.updatedcompany.deletedticket.createdticket.updatedticket.deletedbooking.createdbooking.updatedbooking.deletedproduct.createdproduct.updatedproduct.deletedservice.createdservice.updatedservice.deletedquote.createdquote.updatedquote.deletedorder.createdorder.updatedorder.deleteddeal.createddeal.updateddeal.deletedappointment.createdappointment.updatedappointment.deleteddocument.createddocument.updateddocument.deletedcampaign.createdcampaign.updatedcampaign.deletedPotrzebujesz pomocy?