Refresh Inbound Metadata
Push updated agent configuration to Tabbly inbound routing.
Endpoint
https://www.tabbly.io/api/inbound/refresh-metadata
Refresh Inbound Metadata
Push updated agent configuration to Tabbly inbound routing after editing an agent.
Endpoint
http
POST https://www.tabbly.io/api/inbound/refresh-metadataAuthentication
See Introduction. This is a POST endpoint — include api_key in the JSON request body.
Request body
| Parameter | Type | Required | Description |
|---|---|---|---|
api_key |
string | Yes | Your organization API key |
agent_id |
string | Yes | Voice agent ID |
Example request
bash
curl -X POST "https://www.tabbly.io/api/inbound/refresh-metadata" \
-H "Content-Type: application/json" \
-d '{
"api_key": "YOUR_API_KEY",
"agent_id": "6376"
}'Response
Success (200)
json
{
"status": "success",
"data": {
"action": "metadata_refreshed",
"agent_id": "6376",
"voice_agent_id": "6376",
"phone_number": "+919876543210",
"old_rule_id": "SDR_...",
"inbound_dispatch_rule_id": "SDR_...",
"inbound_trunk_id": "ST_..."
}
}Error responses
json
{
"status": "error",
"message": "Human-readable error description"
}| HTTP status | When |
|---|---|
| 400 | Missing fields |
| 401 | Invalid or missing API key |
| 403 | Wrong org, inactive subscription, or free-tier phone blocked |
| 404 | Agent not found, or inbound not configured |