TAN Adv AI Agent / LLM

Business
POST /api/v1/tan/fetch_adv Bearer

Everything an AI coding assistant needs to write a working TAN Adv integration without opening another page: endpoint, authentication, parameters, a real request, both response shapes and the platform rules it cannot infer from a single example. Copy the brief below and paste it into Claude, Cursor, GitHub Copilot, ChatGPT or any other agent.

Machine-readable spec — Markdown

# TAN Adv API — Way2API®

- **Endpoint:** `POST https://app.way2api.com/api/v1/tan/fetch_adv`
- **Auth:** `Authorization: Bearer YOUR_API_KEY` (or `X-API-Key: YOUR_API_KEY`)
- **Content-Type:** `application/json`
- **Category:** Business
- **Availability:** Available in India
- **Docs:** https://app.way2api.com/documentation/tan-advanced

## What it does

TAN Advanced Verification API — Verify any 10-character TAN (Tax Deduction Account Number) issued by the Income Tax Department. Returns the deductor's full name, allotment date, registered address, email, and phone number. Useful for employer/deductor KYC, TDS compliance, and business verification workflows.

## Request body (application/json)

| Parameter | Type | Required | Description |
| --- | --- | --- | --- |
| `tan_number` | string | yes | 10-character TAN number (e.g. ABCT12345E). |

## Example request

```bash
curl -X POST https://app.way2api.com/api/v1/tan/fetch_adv \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"tan_number":"ABKT12345E"}'
```

## Success response — 200

```json
{
    "status": "SUCCESS",
    "status_code": 200,
    "charged": true,
    "success": true,
    "message": "",
    "message_code": "OK",
    "order_id": "W2A1739512345abcdef01",
    "data": {
        "order_id": "W2A1739512345abcdef01",
        "result": {
            "tan": "ABKT12345E",
            "details": {
                "full_name": "SOLUTIONS PRIVATE LIMITED",
                "first_name": "",
                "middle_name": "",
                "last_name": "",
                "tan_allotment_date": "2050-12-18",
                "address": {
                    "line_1": "H.NO 123 ,SHIV COLONY",
                    "line_2": ",",
                    "line_3": "",
                    "line_4": "",
                    "line_5": "PANCHKULA",
                    "state_code": 99,
                    "zip": "123456",
                    "full": "H.NO.123 SHIV COLONY , PANCHKULA 123456"
                },
                "email_1": "[email protected]",
                "email_2": "",
                "phone_number": "1234567890"
            }
        }
    }
}
```

## Error response — 422

```json
{
    "status": "SUCCESS",
    "status_code": 422,
    "charged": true,
    "success": false,
    "message": "Verification Failed.",
    "message_code": "VERIFICATION_FAILED",
    "order_id": "W2A1739512345abcdef01",
    "data": {
        "order_id": "W2A1739512345abcdef01",
        "error_code": "verification_failed",
        "result": {
            "tan": "RTKT12345",
            "details": []
        }
    }
}
```

## Integration rules

- Every response is JSON carrying `status`, `status_code`, `charged`, `success`, `message`, `message_code` and (once a call reaches the provider) `order_id`. The verification payload is under `data.result`.
- `charged` (boolean) is the authority on billing. Do NOT infer it from the HTTP status: `422` is returned both for input we rejected (not charged) and for a lookup the provider ran and billed us for that returned a negative result (charged).
- `message_code` is a fixed vocabulary — branch on it instead of parsing `message`. Values: `OK`, `ACCEPTED`, `PROVIDER_NO_RESPONSE`, `VERIFICATION_FAILED`, `NO_RECORD_FOUND`, `INVALID_INPUT`, `REQUEST_FAILED`, `MISSING_API_KEY`, `INVALID_API_KEY`, `INSUFFICIENT_BALANCE`, `NO_API_ACCESS`, `NOT_FOUND`, `RATE_LIMITED`, `INTERNAL_ERROR`, `PROVIDER_UNAVAILABLE`.
- `success` reports the verification outcome; `status` reports the ORDER lifecycle (`SUCCESS`/`PENDING`/`FAILED`). They differ on a charged negative result: the order completed and was billed while the verification did not pass.
- A failed verification is still a successful HTTP call — the outcome lives in the response body, so do not treat `200` as "verified".
- Status codes: `200` result returned, `202` pending or provider did not respond (both charged — quote the `order_id`), `401` missing/invalid key, `402` insufficient balance, `403` no access to this service, `422` see `charged`, `429` rate limited (honour the `Retry-After` header), `503` temporarily unavailable.
- Rate limits are per API key, per service, on a 1-minute sliding window.
- Load the API key from an environment variable or secret store. Never hard-code it, never commit it, and never ship it in client-side code — calls must be made from your backend.

Prompts to pair it with

  • Write a production-ready TAN Adv integration in PHP using this spec, with error handling and retries.
  • Given this spec, generate typed request/response models and a client class.
  • Review my existing TAN Adv integration against this spec and list what I handle incorrectly.
⚠ Before you paste generated code

Never let an assistant hard-code your API key — load it from an environment variable or a secret store, and call this endpoint from your backend only. A failed verification is still a successful HTTP call, so check the success field in the body rather than treating 200 as verified.

Prefer to read it yourself?

Overview What this API does, availability, and a quick start. Request Endpoint, authentication headers, every request parameter with its type, and a sample request body. Response The full success response payload, field by field. Error Codes HTTP status codes, error payload shape, and how to handle failures. Code Examples Ready-to-run examples in cURL, PHP, JavaScript and Python. Rate Limits Per-minute and per-day request limits, and what happens on breach.