Tatvora AI API Platform

Integrate advanced AI models using simple REST APIs

Every model is a plain HTTPS endpoint that takes a bearer key and returns JSON. No SDK is required, and nothing needs to be installed or hosted on your side.

  1. Customer Application
  2. Tatvora API
  3. AI Model
  4. JSON Response
Quick start

From account to first response

Eight steps, most of which you only do once.

1

Create or request an account

Register for a Tatvora developer account or request access from our team.

2

Select an API plan

Choose the tier matched to your expected volume, starting at $49 per month for 5,000 calls.

3

Receive an API key

Generate a key from the dashboard. The secret is shown once at creation.

4

Choose an AI API

Pick the model that matches the job — OCR, face detection, recognition, verification, liveness or prediction.

5

Send API requests

Call the REST endpoint over HTTPS with your key in the Authorization header.

6

Receive JSON responses

Handle a predictable JSON payload with a consistent success flag, request id and error shape.

7

Monitor API usage

Track consumption, success rates and per-model usage from the dashboard.

8

Upgrade as the application grows

Move to a higher plan for better effective pricing and higher limits as volume increases.

Authentication

One header, every endpoint

Requests are authenticated with an API key sent as a bearer token. Keys are scoped to your account and can be restricted per API and per environment.

  • All requests must use HTTPS — plain HTTP is rejected
  • The secret value is shown once at creation and cannot be retrieved again
  • Keep keys server-side; never ship one in a browser or mobile binary
  • Revoking a key takes effect immediately
  • Use separate development and production keys from the Business plan upward
Never expose a secret key Every example on this site uses an environment variable (TATVORA_API_KEY). No real key is published anywhere in these docs.
Authorization header
POST https://api.tatvora.com/api/v1/ocr HTTP/1.1
Host: api.tatvora.com
Authorization: Bearer YOUR_API_KEY
Content-Type: multipart/form-data

# Response
HTTP/1.1 200 OK
Content-Type: application/json

{
  "success": true,
  "request_id": "req_8f2c41d0",
  "text": "Extracted document content..."
}
API reference

Endpoints

All endpoints are versioned in the path and served from https://api.tatvora.com.

Tatvora AI API endpoint reference
Endpoint Model Content type Key response fields
POST /api/v1/ocr OCR AI multipart/form-data text, pages, fields
POST /api/v1/face/detect Face Detection AI multipart/form-data faces_detected, faces[].bounding_box
POST /api/v1/face/recognize Face Recognition AI multipart/form-data matched, identity_id, similarity
POST /api/v1/face/verify Face Verification AI multipart/form-data match, similarity
POST /api/v1/face/liveness Face Liveness AI multipart/form-data is_live, spoof_detected
POST /api/v1/predict Predict AI application/json predictions[]

REST APIs

Standard HTTPS endpoints that work with any language or framework.

JSON responses

Consistent, predictable payloads with a stable success and error shape.

API-key authentication

Bearer-token authentication with separate development and production keys.

Usage tracking

Per-model and per-key consumption visible in the dashboard.

Rate limiting

Per-plan request limits that protect both your application and the platform.

Developer documentation

Endpoint reference, request and response schemas and integration examples.

Error handling

Documented HTTP status codes and machine-readable error codes.

API logs

Request history for debugging integrations and investigating failures.

Usage analytics

Trends, quota forecasting and per-API breakdowns of your consumption.

Code examples

Integration examples for every model

cURL, Python, JavaScript, C# and Java for each endpoint. C# examples use HttpClient; in ASP.NET Core, register a typed client through IHttpClientFactory rather than newing one up per request.

Tatvora OCR AI

Turn documents into usable data.

POST https://api.tatvora.com/api/v1/ocr
curl -X POST https://api.tatvora.comPOST /api/v1/ocr \
  -H "Authorization: Bearer $TATVORA_API_KEY" \
  -F "document=@invoice.pdf"

Tatvora Face Detection AI

Detect human faces inside images and video frames.

POST https://api.tatvora.com/api/v1/face/detect
curl -X POST https://api.tatvora.comPOST /api/v1/face/detect \
  -H "Authorization: Bearer $TATVORA_API_KEY" \
  -F "image=@frame.jpg"

Tatvora Face Recognition AI

Recognise identities using intelligent facial analysis.

POST https://api.tatvora.com/api/v1/face/recognize
curl -X POST https://api.tatvora.comPOST /api/v1/face/recognize \
  -H "Authorization: Bearer $TATVORA_API_KEY" \
  -F "image=@capture.jpg" \
  -F "candidates=@candidates.json"

Tatvora Face Verification AI

Verify whether two faces belong to the same person.

POST https://api.tatvora.com/api/v1/face/verify
curl -X POST https://api.tatvora.comPOST /api/v1/face/verify \
  -H "Authorization: Bearer $TATVORA_API_KEY" \
  -F "reference_image=@reference.jpg" \
  -F "probe_image=@selfie.jpg"

Tatvora Face Liveness AI

Verify that the person in front of the camera is real and live.

POST https://api.tatvora.com/api/v1/face/liveness
curl -X POST https://api.tatvora.comPOST /api/v1/face/liveness \
  -H "Authorization: Bearer $TATVORA_API_KEY" \
  -F "image=@selfie.jpg"

Tatvora Predict AI

Make typing faster and smarter.

POST https://api.tatvora.com/api/v1/predict
curl -X POST https://api.tatvora.comPOST /api/v1/predict \
  -H "Authorization: Bearer $TATVORA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
  "text": "Please find attached the invoice for",
  "max_suggestions": 3
}'
Error handling

Predictable failures, documented codes

Errors use standard HTTP status codes with a JSON body carrying a machine-readable code, a human-readable message and the request id. Log the request id — support conversations start there.

  • Retry 429 and 5xx with exponential backoff and a ceiling
  • Do not retry 400, 401 or 403 — fix the request
  • 402 means the monthly quota is exhausted; add credits or upgrade
  • Validate file type and size before forwarding user uploads
HTTP status codes returned by the Tatvora API
Status Meaning
200Request processed successfully
400Invalid request — missing field, unsupported file type
401Missing or invalid API key
403Key not permitted to call this API
402Monthly quota exhausted
413Payload too large
429Rate limit exceeded — honour Retry-After
5xxProcessing error — retry with backoff
Error response shape
{
  "success": false,
  "request_id": "req_3d90ba71",
  "error": {
    "code": "unsupported_file_type",
    "message": "Expected png, jpg, pdf or docx; received tiff."
  }
}
Architecture

What a request passes through

From your application to a model and back, with the checks applied on the way.

Your systems

Web application Mobile application Backend service HRMS ERP

Edge

HTTPS / TLS Abuse protection Request id issued

Tatvora API gateway

Token validation Credential validation Subscription check API permission check Rate limit Quota check Routing

AI models — six independent services

OCR Face Detection Face Recognition Face Verification Face Liveness Predict AI

Platform services

Usage tracking Analytics rollups Quota & alerts Billing Notifications Audit log

Data — metadata only, never request content

Transactional database Usage rollups Cache Queue

No object store and no payload store: submitted documents and images are processed in memory and discarded when the response is sent.

Client dashboard

Usage & quota Analytics API logs API keys Plan & billing
Roadmap

What is coming to the platform

Published so you can plan around it. Dates are not committed; scope may change.

Self-service billing

Register, verify email, choose a plan, pay online and receive an API key without a sales conversation. Stripe and Razorpay are the candidate gateways.

Key management

Key rotation, IP whitelisting, allowed origins, per-key rate limits and environment separation from the dashboard. See the concept.

New model families

Vision AI, Language AI, Speech AI and Generative AI categories, alongside the current Document, Face and Predictive families.

FAQ

Developer questions

Tatvora is an AI technology company based in Gujarat, India. We develop AI models and expose them through REST APIs so businesses and developers can add AI capabilities to their applications without building and maintaining their own AI infrastructure.

Six models today: OCR AI for document intelligence, Face Detection AI, Face Recognition AI, Face Verification AI, Face Liveness AI, and Predict AI for context-aware next-word prediction. The four face models are separate APIs grouped under the Tatvora Face AI platform.

Your application sends an HTTPS request to a Tatvora endpoint with your API key in the Authorization header. The request is routed to the relevant AI model and the result is returned as JSON. There is nothing to install and no model to host.

Yes. Your plan quota is shared across every API, so you can call OCR, face and prediction endpoints from the same key without separate subscriptions. Many workflows chain several models together.

No. The APIs are stateless. What you send is received over TLS, held in memory only while the model computes the result, returned in the response to that same request, and discarded. It is not written to a database, a file or object storage. A deliberate consequence is that we cannot retrieve or resend the content of a past request — if you need a record of what was processed, your application has to keep it.

No. Content submitted to a Tatvora API is never used to train, retrain, fine-tune, benchmark or evaluate any model, and never becomes part of a dataset. This is not an opt-out you have to find in a settings page — since requests are never stored, there is no mechanism by which your traffic could reach a training set.

Operational metadata about the call itself: which API key was used, the timestamp, the endpoint, the HTTP status, how long it took, the request size and the source IP. That is what counts calls against your quota, applies rate limits, raises usage alerts and produces the API logs and analytics in your dashboard. Metadata records that a request happened — never what was in it.

Your application sends the captured face and the candidate identity set together in the same request, either as images or as embeddings returned by an earlier call. We compare them, return the match, and discard both. Your enrolled identities stay in your own database, which means there is no Tatvora-side biometric gallery to breach or to ask us to erase.

It removes a great deal of risk, but no vendor can hand you compliance. Both laws regulate processing, and processing includes operations that store nothing — running inference on a face image is processing biometric data even though the image is discarded moments later. In your integration you are the controller and Tatvora is the processor: you decide what is sent and on what lawful basis. What our design gives you is no data at rest, no retention schedule to police, no erasure backlog and no stored-content breach surface. We sign a Data Processing Agreement on request. We hold no certifications and do not claim any.

Yes. The APIs are plain HTTPS endpoints, so HttpClient is all you need. Every product page includes a C# example, and we recommend registering a typed client through IHttpClientFactory in ASP.NET Core applications. Examples are also provided for cURL, Python, JavaScript and Java.

Yes. Submit an inquiry and our team will issue a time-limited evaluation key so you can run your own documents and images through the models and check the response quality and shape before committing to a plan. Tell us which APIs you want to evaluate and roughly what volume you expect, and we will size the evaluation to match.

Get a key and make your first call

Request an evaluation key and validate the response shape and quality against your own data before committing to a plan.

Questions? Email support@tatvora.com