---
type: "product"
title: "FSSAI License Verification API India | Food License Validation"
description: "Verify FSSAI food license details and status in real time. Integrate FSSAI verification for food business onboarding, marketplace compliance, and regulatory checks."
category: "verification"
canonical: "https://eps.eko.in/products/fssai-verification-api"
---


> **Canonical URL:** https://eps.eko.in/products/fssai-verification-api
> This is a machine-readable Markdown version of the page for AI agents and LLMs. The primary (HTML) version lives at the canonical URL above.

# FSSAI License Verification API for Food Business Compliance

Validate FSSAI food license details and status instantly — verify food business registration for marketplace onboarding, delivery platform compliance, and regulatory checks.

_Verify FSSAI food license details and status_

To get started, fill the form at https://eps.eko.in/signup (with your name, mobile number and email) or call us at +919513181707

## Overview

The FSSAI License Verification API enables businesses to validate Food Safety and Standards Authority of India (FSSAI) license details. Use it for food business onboarding, delivery platform compliance, and food safety regulatory checks.

## Features

- License Validation: Verify FSSAI license number and retrieve registered business details.
- Status Check: Confirm whether the food license is active, expired, or suspended.
- Business Details: Fetch registered business name, address, and license category.
- Real-Time Processing: Instant validation for food business onboarding and compliance workflows.

## Who Should Use This

- Food delivery and aggregator platforms
- E-commerce and marketplace platforms
- Restaurant management SaaS
- Food safety compliance teams

## Use Cases

- Food seller onboarding on marketplaces
- Delivery platform restaurant verification
- Food safety audit and compliance checks
- Cloud kitchen registration verification

## What Can You Verify With FSSAI License Verification API?

- **FSSAI License Number** — The FSSAI license number that was queried.
- **License Status** — Current status of the FSSAI license — Active, Expired, Suspended, or Cancelled.
- **License Category** — Category of the FSSAI license — Registration, State License, or Central License — reflecting the scale of the food business.
- **Business Name** — Registered name of the food business operator (FBO) as on the FSSAI license.
- **Address** — Registered business address of the FBO as on the FSSAI license.
- **State** — Indian state in which the food business is registered.
- **Expiry Date** — License validity expiry date in YYYY-MM-DD format. Use to flag expired or soon-to-expire licenses.

## API Preview — FSSAI License Verification

`POST /tools/kyc/fetch-fssai`

### Example inputs

| Field | Value |
| --- | --- |
| Fssai | 11521998000045 |

### Example outputs

| Field | Value |
| --- | --- |
| FSSAI License Number | 11521998000045 |
| License Status | Active |
| License Category | State License |
| Business Name | Spice Garden Restaurant |
| Address | 123 Main Street, Mumbai, Maharashtra |
| State | Maharashtra |
| Expiry Date | 2026-03-15 |

## Integration Steps

1. **[Sign Up](/console)** — Sign up in minutes with your mobile number (OTP verify).
2. **Verify Identity** — Complete your basic KYC with PAN and address details to verify your identity.
3. **Test APIs Live** — Load funds into your wallet and test the verification APIs live — evaluate before you integrate.
4. **[Integrate with AI](/ai)** — Ready to build? Visit our AI hub for free plugins & tools to integrate faster.
5. **Go Live** — Start verifying FSSAI licenses in production.

## FAQs

### What input is required?
Only the FSSAI license number is required for verification.

### What details are returned?
The API returns FSSAI license status, license category, registered business name, address, state, PIN code, and license expiry date.

### Is this mandatory for food delivery platforms?
Yes. FSSAI regulations require food delivery platforms to verify that all listed restaurants and cloud kitchens have valid FSSAI licenses.

### How fast is the check?
The API returns results in real time with sub-second response times.

### How do I get started?
Four steps: **sign up** at the [developer console page](/console), verify your identity with PAN and address details, load your wallet to test the APIs live, then integrate and go live. Sandbox credentials are issued immediately — you can call your first endpoint before any paperwork clears.

### What is EPS?
**EPS (Eko Platform Services)** is the technology arm of Eko — the developer tools, AI tooling and APIs that power modern fintech integration, from money transfer and AePS to identity verification.

### What are the different ways to integrate with Eko EPS?
Three paths, pick whichever suits your stack:

- Call the **REST APIs** directly.
- Use our official **Node.js, Python, PHP, Go or Java SDKs** to skip request-signing boilerplate.
- Let an **AI coding agent** build it via our [MCP server and agent skills](/ai#install).

For multi-step flows (onboard a sender, *then* transfer) start from a [transaction-flow recipe](/recipe) rather than wiring single endpoints together yourself.

### How does API authentication work?
Each request carries your static `developer_key` header plus a per-request `secret-key` header — an **HMAC-SHA256** signature of the current timestamp, keyed by your access key. The access key itself is **never sent over the wire**. You receive UAT keys on signup and production keys after KYC.

The [How Authentication Works](/docs/how-auth-works) guide has the full signing recipe in five languages plus an **in-browser playground** that generates and verifies a real `secret-key` against your own access key.

### Why does my API call return 401 Unauthorized?
Authentication failed. For the known causes, the response body's `status` names the check that failed:

- `2483` — The developer_key is wrong.
- `2484` — The secret-key (signature) is wrong.
- `2485` — The secret-key-timestamp is more than 2 minutes older or newer than the server clock, or was reused from an earlier request.
- `2486` — The secret-key-timestamp is not in milliseconds (13 digits) — often seconds (10 digits).
- `2487` — The secret-key or secret-key-timestamp header is missing.

If your signature checks out in the [secret-key playground](/docs/how-auth-works#try-it-secret-key-playground) and you still get a `401`, make sure the base URL matches your keys (UAT vs production) and, in production, that your server's IP is whitelisted.

### Is there a sandbox environment for testing?
Yes. A full **sandbox** is available immediately on signup — test your integration end-to-end before going live, no commitment required. For offline work you can also run our [mock server](/ai#artifacts) (`npx -y @ekoindia/eps-mock-server`) and get canned responses with no network calls at all.

### What are the sandbox and production base URLs?
Sandbox and production share the same paths and differ **only** by base URL:

- UAT / Sandbox — `https://staging.eko.in/ekoapi/v3`
- Production — `https://api.eko.in/ekoicici/v3`

A common cause of failures is calling the sandbox URL with live credentials, or vice-versa — **make sure the base URL matches the keys you are using**.

### Do I need to whitelist my server IP?
It's optional. **IP whitelisting** is available for **production** access as an extra layer of security — share your **static public (server) IP** with us and we'll whitelist it.

### Can an AI coding agent build the integration for me?
Yes — that is the fastest path. Point your agent (Claude Code, Codex, Cursor, Copilot, …) at our **MCP server** and it can look up any endpoint, generate correctly-signed requests, and scaffold the integration in your own stack. Install it in [one step from the AI hub](/ai#install), or start from a [ready-made prompt](/ai#quick-start).

We also publish an **OpenAPI 3.1 spec**, a **Postman collection** and per-agent **context packs** (`AGENTS.md`, `CLAUDE.md`, `.cursorrules`) so an agent has the ground truth instead of guessing.

### What response times can I expect?
Most verification APIs return in **real time with sub-second responses**, and 99th-percentile latency stays under two seconds across verification endpoints. Transaction APIs (DMT, AePS, BBPS) respond within seconds.

### Can the API handle high volumes?
Yes. The API is designed to handle **large-scale volumes** reliably without performance degradation.

### How is API usage billed?
Usage is billed **per successful API call** with no minimum commitment. Volume-based pricing tiers are available — see the [pricing calculator](/pricing) for indicative rates, or contact our team for a custom quote.

## API Endpoints

- [FSSAI License Verification](https://eps.eko.in/docs/fetch-fssai.md) (POST)

## API Documentation

- [Full developer docs](https://eps.eko.in/docs/fetch-fssai)

## Related Products

- [Mobile/OTP Verification](https://eps.eko.in/products/mobile-otp-verification-api): Send, verify & validate mobile OTPs with a signed proof token ([markdown](https://eps.eko.in/products/mobile-otp-verification-api.md))
- [PAN Verification](https://eps.eko.in/products/pan-verification-api): Full PAN identity fetch in <2 seconds ([markdown](https://eps.eko.in/products/pan-verification-api.md))
- [Bank Account Verification](https://eps.eko.in/products/bank-verification-api): Penny-drop bank account validation ([markdown](https://eps.eko.in/products/bank-verification-api.md))
- [GST Verification](https://eps.eko.in/products/gst-verification-api): GSTIN lookup & filing status ([markdown](https://eps.eko.in/products/gst-verification-api.md))
- [DigiLocker Integration](https://eps.eko.in/products/digilocker-api): Fetch notarised docs — Aadhaar, DL, marksheets, etc ([markdown](https://eps.eko.in/products/digilocker-api.md))

- [Site index](https://eps.eko.in/index.md): Full list of API products, industries, and solution packs