Home
APIs
Email
Email Content, Urgency & Priority Analysis API

Email API

Email Content, Urgency & Priority Analysis API

Intelligent email processing API for urgency scoring, intent classification, entity extraction, and sentiment tagging.

POST https://rsflowhub.com/api/v1/ai/email-analyze

2 credits per call
X-API-Key header
JSON in, JSON out

Try it in the playground API reference

POST /api/v1/ai/email-analyze

{
    "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"
    ]
}

200 OK response.json

{
    "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."
    }
}

Definition

What is the Email Content, Urgency & Priority Analysis API?

Email Content, Urgency & Priority Analysis API is a REST API on RSFlowHub for 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, falls back to a backup provider if needed, and returns a structured JSON result, usually within 1 to 3 seconds.

Category: Email
Endpoint: POST /api/v1/ai/email-analyze
Authentication: X-API-Key header
Price: 2 credits per call
Rate limit: 10 to 120 requests / minute by plan
Typical response: 1 to 3 seconds
Format: JSON, UTF-8

Request parameters

Send these fields as a JSON body. An invalid or missing field returns a 422 error that names the field.

Field	Type	Required	Description
`email_content`	string	Required	The main body of the email to analyze (Max: 20,000 characters).
`subject`	string	Optional	Optional email subject line. Providing this increases analysis accuracy.
`allowed_categories`	array of strings	Optional	Optional list of allowed categories. If provided, the AI forces the output category into one of these buckets.
`allowed_intents`	array of strings	Optional	Optional list of allowed intents. If provided, the AI forces the output intent into one of these buckets.
`custom_instructions`	string	Optional	Optional specific guidelines to customize the analysis or extraction process.

Code examples

Copy, replace rfh_your_api_key with your key and run. Prefer a client library? See the official SDKs.

request.sh

curl -X POST "https://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"]}'

client.php

<?php

$client = new \GuzzleHttp\Client();
$response = $client->post('https://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();

client.js

const response = await fetch('https://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);

main.py

import requests

url = "https://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())

Response

Every RSFlowHub endpoint uses the same envelope, so one parser handles all of them. Failed calls are not charged.

response.json

{
    "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"
    }
}

error.json

{
    "success": false,
    "request_id": "req_8c1d4e2a-7f3b-4a9c",
    "error": {
        "code": "VALIDATION_ERROR",
        "message": "The given data was invalid.",
        "details": {
            "email_content": [
                "This field is required."
            ]
        }
    },
    "meta": {
        "version": "v1",
        "timestamp": "2026-10-05T09:30:00Z"
    }
}

Envelope fields
Field	Type	Meaning
`success`	boolean	true when the call worked, false on any error.
`request_id`	string	Unique id for this call. Quote it when you contact support.
`data.result`	object	The result of this endpoint (see the example).
`error`	object	Only on failure: code, message and details per field.
`meta`	object	API version and server timestamp.

All error codes: Errors reference

Features

Automated Urgency & Priority Scoring

Classifies priority level into low, medium, high, or critical emergency based on customer frustration and deadlines.

Category & Intent Classification

Automatically categorizes emails into billing, technical support, sales inquiries, refund requests, or spam.

Entity & Action Item Extraction

Extracts customer names, order IDs, account numbers, requested action dates, and key summary takeaways.

Language & Sentiment Detection

Identifies source language and measures emotional tone across positive, neutral, frustrated, or angry sentiment.

Use cases

How teams use the Email Content, Urgency & Priority Analysis API in production.

Customer Support SaaS

Helpdesk Inbox Prioritization & Routing

Classify incoming customer support emails to route high-urgency billing complaints directly to senior support managers.

Input: Hello, I was double charged for my Pro subscription this month. Please fix this ASAP as I am very frustrated.
Output: {"category": "billing", "intent": "refund_request", "urgency": "high", "sentiment": "negative"}

Surfaces critical billing issues first so they are answered sooner.

CRM & Sales SaaS

Sales Lead Intent Qualification

Extract company names, team size, and buyer purchase intent from inbound contact sales emails.

Input: We are interested in an enterprise plan for 250 developers at Acme Corp. Need a demo next week.
Output: {"category": "sales", "intent": "enterprise_demo", "company": "Acme Corp", "seats": 250}

Accelerates enterprise sales qualification pipelines.

Workplace Productivity

Shared Inbox Auto-Categorization

Automatically tag incoming company inbox emails by department (Billing, Support, Legal, Careers) for team routing.

Input: Please send your tax form W-9 and vendor registration agreement.
Output: {"category": "legal_compliance", "intent": "w9_request", "department": "finance"}

Eliminates manual inbox triage for operations teams.

Email Content, Urgency & Priority Analysis API vs building it yourself

The same job done three ways.

Topic	RSFlowHub API	Raw LLM prompts	Rules / regex
Output	Validated JSON fields	Free text you have to parse	Fixed patterns only
Setup	One POST request, no prompts	Write and maintain prompts and parsing	Write and maintain rule lists
Provider outage	Automatic fallback to a backup model	You build retries and a second vendor	Not applicable
Pricing	2 credits per call, failed calls free	Per token, per vendor	Your own servers and upkeep
Understands context	Yes, AI model	Yes, AI model	No, keywords only

Frequently asked questions

How does the API determine email urgency and priority?

The API evaluates sender sentiment, key phrases (e.g. "double charged", "down system", "ASAP"), and explicit customer deadlines to assign a numeric urgency score.

Can I define custom categories and allowed intents?

Yes! You can pass allowed_categories and allowed_intents arrays to constrain output classification to your specific CRM schema.

Does the API strip email signatures and disclaimers?

Yes. The engine automatically isolates the core message body while ignoring corporate legal disclaimers and email signatures.

How fast is the Email Analysis API?

Email Analysis 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.

How many credits does each request consume?

Standard Email Analysis API calls consume 2 base credits per request.

Start using the Email Content, Urgency & Priority Analysis API

Free plan with 100 credits/month + 1,000 bonus credits when you sign in before 23 Nov. Test it in the playground first, no code needed.

Get a free API key Try it now