API documentationBahasa Indonesia
POST/api/v2/webhooks
Add a webhook
Register your system's HTTPS URL and the events you want to receive.
At most 5 webhooks per business. The response contains secret only once (it can be viewed again in Settings › API & Webhook (Pengaturan › API & Webhook)). Use that secret to check the Klikflow-Signature header.
Send an Idempotency-Key header (for example a new UUID per request). A repeat with the same key within 24 hours gets the first answer again, so nothing is sent twice.
Body (JSON)
urlstringrequiredPublic HTTPS URL, at most 500 characters.
eventsarray: message.received | message.status | contact.created | lead.created | order.paid | ticket.created | ticket.status | template.status | channel.statusrequiredEvents to send; see the Webhook events guide.
descriptionstringDescription, at most 120 characters.
Possible errors
- 400
invalid_jsonBody is not valid JSON - 400
idempotency_key_invalidInvalid Idempotency-Key - 401
missing_keyAPI key not sent - 401
key_invalidUnknown API key - 401
key_revokedAPI key revoked - 401
key_expiredAPI key expired - 401
member_inactiveKey creator is no longer a member - 403
ip_not_allowedServer IP not in the key's list - 403
plan_no_apiPlan does not include the API for live keys - 403
tenant_blockedBusiness access suspended - 403
scope_missingKey lacks this permission - 403
permission_missingKey creator's role lacks this permission - 403
live_key_requiredLive key required - 409
idempotency_conflictIdempotency-Key used for different content - 409
request_in_progressThe same request is still being processed - 422
invalid_requestInvalid field - 422
webhook_limitWebhook limit reached - 429
rate_limitedToo many requests per minute - 500
internal_errorProblem at Klik Flow
Try it
This endpoint needs a live key, so it cannot be tried from the docs. Call it from your server.