Inbound endpoints
Give any system a URL it can post JSON to: open requests, upsert customers or products.
An inbound endpoint is a tokenised URL that accepts HTTP POST with a JSON body. Create one in Settings, then Integrations, choose its action and Kabaido shows the URL and a signing secret once. Pausing or deleting the endpoint revokes the URL immediately.
Actions
| Action | Body | Result |
|---|---|---|
| Create request | { text, title?, customer?, external_ref? } | Opens a request thread your team sees in Requests; responds 202 with the request id |
| Upsert customers | { customers: [{ company, email?, phone?, external_id? }] } | Creates or updates up to 500 customers, matched by external id then email domain |
| Upsert products | { products: [...], schema_id? } | Creates or updates up to 1000 products by SKU, same validation as the import wizard |
Example
curl https://kabaido.ai/api/in/whin_your_token \
-H "Content-Type: application/json" \
-d '{ "text": "RFQ: 25x 12mm carbide end mills, 4 flute, AlTiN" }'Signatures and limits
When the endpoint requires signatures, send X-Kabaido-Signature computed exactly like outbound webhook signatures, keyed by the endpoint secret over the raw body. Leave verification off for senders that cannot set headers; the token in the URL is then the only credential, so share it carefully. Bodies are limited to 1MB and each endpoint is throttled to short bursts of up to 120 posts.
Every receipt appears under the endpoint in Settings with its outcome, so a misconfigured sender is visible immediately.