API reference for triggering bots via webhooks
Webhook triggers allow you to invoke your lil’bots from any external platform through a simple API endpoint. This documentation provides a complete reference for the webhook triggers API, including authentication, request formats, and response structures.
All endpoints in the Webhook Triggers API require authentication via an API key. This key is specific to each trigger and is provided when you create a trigger in the lil’bots platform.
The API key should be passed in the X-Key
header with each request:
Security Note
Protect your trigger keys carefully. Anyone with access to your trigger URL and key can invoke your bot, potentially accessing any data your bot has access to and using up your credits.
When using the webhook API, bot inputs are passed as a JSON body in your request. These values will be available to your bot’s main
function.
To ensure platform stability, the webhook API has the following rate limits:
Exceeding these limits will result in a 429 Too Many Requests
response.
Below is a complete example of triggering a bot and waiting for its results using curl:
API reference for triggering bots via webhooks
Webhook triggers allow you to invoke your lil’bots from any external platform through a simple API endpoint. This documentation provides a complete reference for the webhook triggers API, including authentication, request formats, and response structures.
All endpoints in the Webhook Triggers API require authentication via an API key. This key is specific to each trigger and is provided when you create a trigger in the lil’bots platform.
The API key should be passed in the X-Key
header with each request:
Security Note
Protect your trigger keys carefully. Anyone with access to your trigger URL and key can invoke your bot, potentially accessing any data your bot has access to and using up your credits.
When using the webhook API, bot inputs are passed as a JSON body in your request. These values will be available to your bot’s main
function.
To ensure platform stability, the webhook API has the following rate limits:
Exceeding these limits will result in a 429 Too Many Requests
response.
Below is a complete example of triggering a bot and waiting for its results using curl: