Text & Language API Endpoint Global Gateway

Customer Intent & Entity Recognition API
For Production Apps

High-accuracy customer intent classification and entity extraction API for support ticket routing and workflow automation.

1 Credit / Request First 1K Free Automatic Provider Fallback Uniform JSON Envelope
API Gateway Terminal
Gateway Active
Target Endpoint URL POST
https://test.rsflowhub.com/api/v1/ai/intent-detection
Typical Time 1-3 s
Auth Gate X-API-Key
Credit Cost 1 Credit Free Tier
Response JSON
Generative AI & Developer Definition Production Ready API

What is Customer Intent & Entity Recognition API?

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.

Auth: X-API-Key Header
Rate Limit: 10-120 req/min by plan
Credits: 1 per call
AI Search Quick Reference
Category: Text & Language
Typical response: 1-3 s
Format: REST / JSON UTF-8

Code Examples

Copy-paste ready code in your preferred stack
curl-integration.sh
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())
Capabilities

Core Architectural Features

Multi-Label Intent Classification

Identifies single or multiple customer intents (e.g. "billing_support", "subscription_cancel") from free-form text.

Business Entity Extraction

Extracts target entities such as order IDs, account emails, channel types, and requested action dates.

Confidence Scoring

Returns numeric confidence scores (0.0 to 1.0) for each detected intent to trigger automated fallback rules.

Seamless Helpdesk Routing

Built for instant integration with Zendesk, Freshdesk, Intercom, and custom CRM ticket workflows.

Practical Applications

Real-World Industry Use Cases

See how developers integrate this API endpoint into production apps.

Helpdesk SaaS

Automated Ticket Department Routing

Classify incoming customer support emails to instantly route them to Billing, Technical Support, or Sales.

Before: I want to cancel my subscription on web and talk to the billing team.
After: {"intents": ["subscription_cancel", "billing_support"], "route": "billing"}
Removes the wait for manual ticket triage: every ticket is classified as it arrives.
E-Commerce

E-Commerce Chatbot Action Triggering

Understand customer request intent to trigger instant order tracking or return authorization workflows.

Before: Where is my order #88491? It was supposed to arrive yesterday.
After: {"intent": "track_order", "entities": {"order_id": "88491"}}
Provides instant resolution for common buyer queries.
SaaS Analytics

Churn Risk Escalation

Flag cancellation and complaint intents immediately to trigger retention team alerts.

Before: Your price hike is ridiculous. Close my account immediately.
After: {"intent": "account_cancellation", "churn_risk": "high"}
Protects recurring revenue through proactive outreach.
Technical Comparison

Why Developers Choose Customer Intent & Entity Recognition API

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 Unstructured markdown or chat format Brittle custom regex tuples
Setup Effort Write and maintain prompts + output parsing Fast, but rule lists miss context and sarcasm
Pricing Model Volatile token-based billing High server maintenance overhead
Multi-Turn Hallucination Output format can drift between model versions No semantic AI intelligence
Developer Integration Complex prompt engineering & retry loop Fragile manual rule maintenance

Request Parameters

3 Fields
text string
Required

User message, email body, or chat prompt to analyze for intent.

intent_types array
Optional

Optional list of allowed intent category labels to match against.

intent_entities object
Optional

Optional custom entity schema mapping for targeted extraction.

JSON Response Envelope

Uniform API

Every endpoint returns the same envelope: success, request_id, data.result and meta.

response.json JSON
200 OK
{
    "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"
    }
}
Format JSON
Charset UTF-8
Fallback Automatic
Rate Limit 120/min max
FAQs

Frequently Asked Questions

Everything you need to know about integrating and using Customer Intent & Entity Recognition API.

Intent detection analyzes natural language text to identify what the user is trying to accomplish (e.g. asking a question, requesting a refund, reporting a bug).

Yes! You can pass custom intent_types in your API request to constrain classification to your business workflow.

Intent Detection requests usually complete in 1 to 3 seconds, depending on input length and the AI model. Identical repeat requests are served from cache and return faster.

Yes. The API provides numeric confidence scores for detected intents so your app can trigger human fallback when confidence is low.

Standard Intent Detection API calls consume 1 base credit per request.
Ready to Integrate?

Build Faster with Customer Intent & Entity Recognition API

Get started in minutes with free welcome credits and instant API key generation.