BBIE Institutional
API Specification
Welcome to the Bharat Business Intelligence Engine (BBIE) Pilot Program API documentation. This specification provides deep architectural, schematic, and cryptographic guidelines for integrating national-scale identity resolution into your institutional workflows.
3072-Dim AI Matching
Advanced vector embeddings resolve fuzzy, fragmented multi-lingual business names instantly.
Sovereignty Buffer
Zero-knowledge matching ensures raw PII is never stored or exposed during verification.
Golden Record Issuance
Generates a permanent, unified Unique Bharat Business ID (UBID) across 15+ registries.
Architectural Vision & Workflow
The BBIE platform operates as an institutional middleware layer sitting between fragmented state/central registries (MCA, GSTN, EPFO, CIN) and consuming entities (Banks, Regulators, Ministries).
The 5-Stage Zero-Trust Resolution Pipeline
Ingestion & Buffer
Unstructured fragments enter the isolated sovereignty buffer.
Cryptographic Hash
Identifiers are converted to SHA-256 tokens instantly.
Vector Search
Semantic matching across 3072-dim AI space.
Spatial Anchor
Geospatial verification using 6-digit PIN codes.
Golden Dossier
Issuance of permanent UBID with full audit timeline.
Authentication & Security Enclave
BBIE requires strict mutual authentication for all institutional access. Vetted pilot participants are issued a high-entropy **Service Role API Key** alongside an Institutional Identifier.
Mandatory HTTP Headers
HMAC Signature Verification (Tier-1 Institutions)
For financial regulators and core banking systems, requests must include an `X-BBIE-SIGNATURE` header containing an HMAC-SHA256 signature of the request body using your institutional private secret.
Rate Limits & Volumetric Tiers
To prevent denial-of-service and guarantee SLA uptime for national infrastructure, volumetric controls are enforced at the API gateway layer using token bucket algorithms.
Suitable for asynchronous batch verification and departmental onboarding.
Assigned to active pilot judges, core fintech partners, and real-time loan origination systems.
Dedicated bare-metal deployment for central intelligence and national security agencies.
Identity Resolution Endpoint
Submits unverified, fragmented business data into the BBIE Confidence Engine. The engine evaluates semantic similarity, cross-references historical registry collisions, and returns a high-confidence UBID match.
Request Body Schema (application/json)
| Parameter | Type | Requirement | Description |
|---|---|---|---|
| entity_name | string | Required | The legal or trade name of the business entity (e.g., `Mphasis Ltd` or `Mphasis`). |
| pincode | string | Recommended | 6-digit Indian Postal Code. Acts as the primary spatial anchor to prevent name collisions. |
| pan | string | Optional | 10-character alphanumeric Permanent Account Number (e.g., `BLRMP1234F`). |
| gstin | string | Optional | 15-character Goods and Services Tax Identification Number. |
| address | string | Optional | Unstructured physical address snippet for fuzzy spatial clustering. |
| cin | string | Optional | 21-character Corporate Identification Number (MCA Registry). |
| fuzzy_threshold | number | Optional | Custom AI matching strictness between `0.0` and `1.0`. Defaults to `0.85`. |
| sovereignty_mask | boolean | Optional | If `true`, returns fully hashed PII tokens to comply with zero-knowledge policies. Defaults to `true`. |
Success Response Payload (200 OK)
Dossier Retrieval Endpoint
Fetches the comprehensive Golden Record and forensic resolution history for a specific Unique Bharat Business ID (UBID). Used for underwriting, regulatory audits, and deep compliance checks.
Query Parameters
| Parameter | Type | Requirement | Description |
|---|---|---|---|
| ubid | string | Required | The Unique Bharat Business ID (e.g., `KA-UBID-SLIY-54321`). Passed in URL path. |
| include_audit | boolean | Optional | If `true`, attaches the full historical timeline of resolution merges and human reviews. |
| depth | enum | Optional | `SUMMARY` | `STANDARD` | `EXHAUSTIVE`. Determines the volume of cross-registry data returned. |
Success Response Payload (200 OK)
Human Arbitration Feedback Endpoint
Allows authorized human reviewers and pilot program judges to submit manual arbitration decisions, overriding AI confidence matches or splitting incorrectly merged clusters.
Request Body Schema (application/json)
| Parameter | Type | Requirement | Description |
|---|---|---|---|
| ubid | string | Required | The target UBID being arbitrated. |
| decision | enum | Required | `APPROVE_MERGE` | `FORCE_SPLIT` | `FLAG_ANOMALY`. |
| justification_notes | string | Required | Mandatory audit reasoning for the override. |
| officer_id | string | Required | Vetted Pilot Judge or Department Officer ID. |
Multi-Language Client SDKs
Integrate BBIE identity resolution directly into your existing tech stack using our official client libraries. Select your preferred language below for fully working pilot snippets.
Error Codes & Troubleshooting Matrix
BBIE uses standardized HTTP status codes paired with detailed JSON error envelopes to ensure fast programmatic remediation during pilot integrations.
| HTTP Code | Error Code | Description | Remediation Action |
|---|---|---|---|
| 400 Bad Request | ERR_SCHEMA_INVALID | Missing required `entity_name` or invalid pincode format. | Check request payload against the official OpenAPI specification. |
| 401 Unauthorized | ERR_TOKEN_EXPIRED | Institutional Bearer Token is missing, expired, or revoked. | Request a fresh session token from the Governance Hub. |
| 403 Forbidden | ERR_SOVEREIGNTY_VIOLATION | Attempted unmasked PII pull without high-security clearance. | Ensure `X-SOVEREIGNTY-MODE` matches your departmental SLA tier. |
| 404 Not Found | ERR_UBID_UNKNOWN | Requested UBID does not exist in the Golden Registry. | Verify the UBID string or run a `POST /resolve` first. |
| 409 Conflict | ERR_COLLISION_DETECTED | Multiple active businesses share identical names and pincodes. | Provide secondary identifiers (PAN, GSTIN) to break the tie. |
| 429 Too Many Requests | ERR_RATE_LIMIT_EXCEEDED | Institutional token bucket quota depleted. | Implement exponential backoff or request a Tier-2 Enclave upgrade. |
| 500 Internal Error | ERR_ENGINE_TIMEOUT | Upstream state registry (e.g., MCA/EPFO) failed to respond. | Retry request after 5 seconds; BBIE will serve cached golden record. |
Sovereignty Shield Architecture
The BBIE platform is built from the ground up to protect institutional data sovereignty. Raw business signals are scrubbed at the memory boundary.
When an institution submits a resolution query, PII strings (PAN, GSTIN) are converted into salted SHA-256 hashes inside an ephemeral enclave. Matching occurs strictly between hashes, guaranteeing that BBIE database administrators cannot reverse-engineer client customer lists.
Every resolution merge, dossier retrieval, and human arbitration override is cryptographically signed and stored in a tamper-evident audit ledger. Pilot judges can verify the precise lineage of any Golden Record back to its raw registry origins.
DPDP Act 2023 Compliance Framework
BBIE strictly adheres to the Digital Personal Data Protection (DPDP) Act 2023 guidelines for institutional data fiduciaries.
Purpose Limitation
Data ingested via API is utilized exclusively for identity deduplication and compliance scoring. It is never monetized, shared with third-party advertisers, or stored beyond the necessary arbitration lifecycle.
Data Minimization
Institutions can configure the `sovereignty_mask` parameter to receive only binary validation flags (e.g., `gst_valid: true`) rather than pulling complete, sensitive tax histories.
Right to Grievance Redressal
Business entities flagged with anomalies or incorrect merges can initiate a formal redressal workflow via the Governance Hub, triggering an immediate human-in-the-loop review by a designated pilot officer.
Pilot Program Onboarding Checklist
Follow this step-by-step checklist to complete your institutional onboarding and verify your API integration before the live pilot demonstration.
Log into the Governance Hub using your departmental credentials to provision a dedicated Tier-2 Service Role API Key.
Set your default `X-SOVEREIGNTY-MODE` header in your API client based on your departmental data-sharing agreement.
Run a test resolution against the known benchmark entity `Mphasis Limited` (Pincode `560001`) to verify 200 OK connectivity.
Check the Review Workspace in the UI to ensure your API call successfully logged an immutable forensic audit trail.
Need Direct Pilot Engineering Support?
As a selected pilot participant, you have direct access to the core Deepmind & BBIE architecture team for custom integration debugging.