POST Ticket Workflow API
/api/v1/ai/ticket-workflow
Analyze a customer support ticket and context to determine the next automated workflow action, priority, and routing destination.
Architecture Role & AI Definition
Ticket Workflow API provides low-latency, deterministic REST execution for production engineering workflows. It processes structured payloads with strict schema validation, returns uniform JSON envelopes, and is secured via SHA-256 API key authentication with atomic credit pre-authorization locks.
Production Reliability Guidelines
Configure a hard client timeout of 5 to 8 seconds. If network latency spikes, cancel connection to avoid holding open sockets in worker pools.
Upon receiving 429 Rate Limit or transient 5xx, pause with exponential backoff:
wait = min(max_backoff, base * 2^attempt + jitter).
RSFlowHub acquires an atomic lock verifying base credits before model invocation. If validation fails, zero credits are deducted.
Request Body Parameters
| Field | Type | Required | Description |
|---|---|---|---|
ticket |
string | Required | The customer support ticket message text (Max: 20,000 characters). |
subject |
string | Optional | Optional ticket subject header. |
customer_context |
string | Optional | Optional customer account details context. |
product_context |
string | Optional | Optional product details context. |
business_context |
string | Optional | Optional support operational policies or rules context. |
previous_messages |
array | Optional | Optional array of previous messages in conversation thread. |
available_departments |
array | Optional | Optional list of available departments to restrict routing decisions. |
Example Request
This example demonstrates how to evaluate a ticket to resolve the next workflow state.
{
"ticket": "My payment was deducted but my subscription is still not active.",
"customer_context": "Billing database shows payment pending verification.",
"available_departments": ["technical_support", "billing", "sales"]
}curl -X POST https://rsflowhub.com/api/v1/ai/ticket-workflow \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"ticket": "My payment was deducted but my subscription is still not active.",
"customer_context": "Billing database shows payment pending verification.",
"available_departments": ["technical_support", "billing", "sales"]
}'Example Response
The response returns workflow decisions, department routing, safety flags, and details on any missing inputs required from the user.
{
"success": true,
"request_id": "req_7f3a9c2d1e4b8a6f",
"data": {
"result": {
"decision": "REQUEST_MORE_INFO",
"priority": "high",
"route_to": "billing",
"requires_human": true,
"reason": "Payment deduction occurred but subscription not active. System is waiting for user transaction receipt verification details.",
"can_auto_reply": true,
"required_information": [
"transaction_receipt_id"
]
}
},
"meta": {
"version": "v1",
"timestamp": "2026-09-27T12:34:56+00:00"
}
}API Request Example
Use the cURL snippet below to test the endpoint.
curl -X POST 'https://rsflowhub.com/api/v1/ai/ticket-workflow' \
-H 'Authorization: Bearer YOUR_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"ticket": "My payment was deducted but my subscription is still not active.",
"customer_context": "Billing database shows payment pending verification.",
"available_departments": [
"technical_support",
"billing",
"sales"
]
}'Want to try it without code? Test this request in the live Playground.
Common Failure Modes & Troubleshooting Matrix
| HTTP Code | Error Code | Root Cause | Recommended Remediation |
|---|---|---|---|
| 401 | API_KEY_MISSING / INVALID_API_KEY |
No key sent, or the key was mistyped or regenerated. | Copy the current key from Dashboard → API Keys and send it as Authorization: Bearer (or X-API-Key). |
| 402 | INSUFFICIENT_CREDITS |
Your balance cannot cover the estimate for this call (base 3 credits plus input/output size). | Buy a plan in Dashboard → Billing. Nothing was charged. |
| 422 | VALIDATION_ERROR |
A field is missing, too long or the wrong type, or the body is not valid JSON. | Read error.details for the field messages and fix the request. Do not retry the same body. |
| 429 | RATE_LIMIT_EXCEEDED |
Your plan-wide or per-endpoint per-minute limit was reached. | Wait the seconds in the Retry-After header, then retry with jitter. Rate limits |
| 502 | AI_PROVIDER_ERROR |
The AI model and its backup both failed. | Retry with backoff and check the status page. Nothing was charged. |