Multi-Label Intent Classification
Identifies single or multiple customer intents (e.g. "billing_support", "subscription_cancel") from free-form text.
Loading RSFlowHub...
High-accuracy customer intent classification and entity extraction API for support ticket routing and workflow automation.
https://test.rsflowhub.com/api/v1/ai/intent-detection
Customer Intent & Entity Recognition API is a ready-to-use REST API on RSFlowHub for developers building web, mobile and AI agent applications. Send a JSON request to POST /api/v1/ai/intent-detection with your API key; RSFlowHub runs it on a tuned AI model (with automatic fallback to a backup provider) and returns a structured JSON result, usually within 1 to 3 seconds.
X-API-Key Header
curl -X POST "https://test.rsflowhub.com/api/v1/ai/intent-detection" \
-H "Content-Type: application/json" \
-H "X-API-Key: rfh_your_api_key" \
-d '{"text":"I want to cancel my subscription on web and talk to the billing team.","intent_types":["billing_support","subscription_cancel"],"intent_entities":{"subscription_cancel":["channel"]}}'
<?php
$client = new \GuzzleHttp\Client();
$response = $client->post('https://test.rsflowhub.com/api/v1/ai/intent-detection', [
'headers' => [
'Content-Type' => 'application/json',
'X-API-Key' => 'rfh_your_api_key',
],
'json' => array (
'text' => 'I want to cancel my subscription on web and talk to the billing team.',
'intent_types' =>
array (
0 => 'billing_support',
1 => 'subscription_cancel',
),
'intent_entities' =>
array (
'subscription_cancel' =>
array (
0 => 'channel',
),
),
),
]);
echo $response->getBody();
const response = await fetch('https://test.rsflowhub.com/api/v1/ai/intent-detection', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'X-API-Key': 'rfh_your_api_key'
},
body: JSON.stringify({"text":"I want to cancel my subscription on web and talk to the billing team.","intent_types":["billing_support","subscription_cancel"],"intent_entities":{"subscription_cancel":["channel"]}})
});
const data = await response.json();
console.log(data);
import requests
url = "https://test.rsflowhub.com/api/v1/ai/intent-detection"
headers = {
"Content-Type": "application/json",
"X-API-Key": "rfh_your_api_key"
}
payload = {"text":"I want to cancel my subscription on web and talk to the billing team.","intent_types":["billing_support","subscription_cancel"],"intent_entities":{"subscription_cancel":["channel"]}}
response = requests.post(url, json=payload, headers=headers)
print(response.json())
Identifies single or multiple customer intents (e.g. "billing_support", "subscription_cancel") from free-form text.
Extracts target entities such as order IDs, account emails, channel types, and requested action dates.
Returns numeric confidence scores (0.0 to 1.0) for each detected intent to trigger automated fallback rules.
Built for instant integration with Zendesk, Freshdesk, Intercom, and custom CRM ticket workflows.
See how developers integrate this API endpoint into production apps.
Classify incoming customer support emails to instantly route them to Billing, Technical Support, or Sales.
Understand customer request intent to trigger instant order tracking or return authorization workflows.
Flag cancellation and complaint intents immediately to trigger retention team alerts.
Comparing RSFlowHub's specialized API gateway vs raw multi-turn LLM prompts vs legacy regex rules.
| Evaluation Metric | RSFlowHub API | Raw LLM Prompts | Legacy Regex / Rules |
|---|---|---|---|
| Response Structure | Validated JSON envelope | Unstructured markdown or chat format | Brittle custom regex tuples |
| Setup Effort | One POST request, no prompts | Write and maintain prompts + output parsing | Fast, but rule lists miss context and sarcasm |
| Pricing Model | Flat 1 credit/request | Volatile token-based billing | High server maintenance overhead |
| Multi-Turn Hallucination | Zero (Deterministic validators) | Output format can drift between model versions | No semantic AI intelligence |
| Developer Integration | 3 lines cURL, PHP, JS, Python | Complex prompt engineering & retry loop | Fragile manual rule maintenance |
text
string
User message, email body, or chat prompt to analyze for intent.
intent_types
array
Optional list of allowed intent category labels to match against.
intent_entities
object
Optional custom entity schema mapping for targeted extraction.
Every endpoint returns the same envelope: success, request_id, data.result and meta.
{
"success": true,
"request_id": "req_3f9a2c7e-5b1d-4e8a-9c2f-7d6e1a0b4c8d",
"data": {
"result": {
"intent": "cancel_subscription",
"confidence": 0.96,
"entities": {
"refund_requested": true,
"payment_method": "credit_card"
}
}
},
"meta": {
"version": "v1",
"timestamp": "2026-10-05T09:30:00Z"
}
}
Everything you need to know about integrating and using Customer Intent & Entity Recognition API.
Get started in minutes with free welcome credits and instant API key generation.
🐞 Found an issue? Report it and our team replies within 1 business day.
💡 Need a custom endpoint? Tell us what you need and we will scope it with you.