Automated Urgency & Priority Scoring
Classifies priority level into low, medium, high, or critical emergency based on customer frustration and deadlines.
Loading RSFlowHub...
Intelligent email processing API for urgency scoring, intent classification, entity extraction, and sentiment tagging.
https://test.rsflowhub.com/api/v1/ai/email-analyze
Email Content, Urgency & Priority Analysis 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/email-analyze 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/email-analyze" \
-H "Content-Type: application/json" \
-H "X-API-Key: rfh_your_api_key" \
-d '{"subject":"Issue with my recent invoice","email_content":"Hello, I was double charged for my Pro subscription this month. Please fix this ASAP as I am very frustrated.","allowed_categories":["sales","support","billing","spam"],"allowed_intents":["refund_request","cancellation","technical_issue"]}'
<?php
$client = new \GuzzleHttp\Client();
$response = $client->post('https://test.rsflowhub.com/api/v1/ai/email-analyze', [
'headers' => [
'Content-Type' => 'application/json',
'X-API-Key' => 'rfh_your_api_key',
],
'json' => array (
'subject' => 'Issue with my recent invoice',
'email_content' => 'Hello, I was double charged for my Pro subscription this month. Please fix this ASAP as I am very frustrated.',
'allowed_categories' =>
array (
0 => 'sales',
1 => 'support',
2 => 'billing',
3 => 'spam',
),
'allowed_intents' =>
array (
0 => 'refund_request',
1 => 'cancellation',
2 => 'technical_issue',
),
),
]);
echo $response->getBody();
const response = await fetch('https://test.rsflowhub.com/api/v1/ai/email-analyze', {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'X-API-Key': 'rfh_your_api_key'
},
body: JSON.stringify({"subject":"Issue with my recent invoice","email_content":"Hello, I was double charged for my Pro subscription this month. Please fix this ASAP as I am very frustrated.","allowed_categories":["sales","support","billing","spam"],"allowed_intents":["refund_request","cancellation","technical_issue"]})
});
const data = await response.json();
console.log(data);
import requests
url = "https://test.rsflowhub.com/api/v1/ai/email-analyze"
headers = {
"Content-Type": "application/json",
"X-API-Key": "rfh_your_api_key"
}
payload = {"subject":"Issue with my recent invoice","email_content":"Hello, I was double charged for my Pro subscription this month. Please fix this ASAP as I am very frustrated.","allowed_categories":["sales","support","billing","spam"],"allowed_intents":["refund_request","cancellation","technical_issue"]}
response = requests.post(url, json=payload, headers=headers)
print(response.json())
Classifies priority level into low, medium, high, or critical emergency based on customer frustration and deadlines.
Automatically categorizes emails into billing, technical support, sales inquiries, refund requests, or spam.
Extracts customer names, order IDs, account numbers, requested action dates, and key summary takeaways.
Identifies source language and measures emotional tone across positive, neutral, frustrated, or angry sentiment.
See how developers integrate this API endpoint into production apps.
Classify incoming customer support emails to route high-urgency billing complaints directly to senior support managers.
Extract company names, team size, and buyer purchase intent from inbound contact sales emails.
Automatically tag incoming company inbox emails by department (Billing, Support, Legal, Careers) for team routing.
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 2 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 |
email_content
string
Raw text content or body of the incoming email to analyze.
subject
string
Subject line of the incoming email.
allowed_categories
array
Optional list of allowed classification categories (e.g. ["sales", "support", "billing", "spam"]).
allowed_intents
array
Optional list of allowed intents (e.g. ["refund_request", "cancellation", "technical_issue"]).
custom_instructions
string
Custom classification rules or department mapping guidelines.
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": {
"category": "billing",
"intent": "refund_request",
"priority": "high",
"sentiment": "negative",
"language": "en",
"entities": {
"invoice_number": "INV-2041",
"amount": "49.00 USD"
},
"summary": "Customer was charged twice for invoice INV-2041 and asks for a refund of the duplicate payment."
}
},
"meta": {
"version": "v1",
"timestamp": "2026-10-05T09:30:00Z"
}
}
Everything you need to know about integrating and using Email Content, Urgency & Priority Analysis 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.