---
title: Geo Intelligence API - Initiate request
slug: api-marketplace/geo-intelligence-api-initiate-request
createdAt: 2026-10-27T07:33:19.576Z
---

# Overview

The **Geo Intelligence API** is a powerful data aggregation and ranking engine that enables lenders, collections teams, and fraud-risk functions to programmatically discover and verify customer addresses using a mobile.

The API processes the retrieved records to deliver a clean, actionable output. The results are:

- **Structured:** Raw address strings are parsed into standardized fields (Full address, City, State, Pincode).
- **Ranked & Deduplicated:** Duplicate entries are merged, and addresses are sorted based on a proprietary ranking logic.
- **Scored for Confidence:** Each address is assigned a confidenceScore (0–100) and a confidenceBand (HIGH, MEDIUM, LOW) based on source, recency, completeness, and multi-source corroboration.
- **Tagged for Provenance:** Every address includes the reported date and source type (e.g., PRIMARY, DELIVERY) so downstream systems can weight the freshness appropriately.

### Key Use Cases

**1. Skip Tracing & Debt Collections** When a borrower defaults and becomes unreachable, collections teams can input the user's phone number to retrieve a ranked list of all known historical and current addresses.

**2. Planning CPV (Customer Physical Verification) ** Financial institutions spend significant time and money conducting manual field visits to verify customer addresses. By utilizing this API alongside risk decisioning logic, lenders can automatically validate a customer-declared address against high-trust government and bureau records.

**3. Spotting address mismatches and fraud**

During onboardings, compare the declared address with the addresses linked to the customer's phone number. A declared address that never appears, or appears only in a different state, is a useful risk signal for underwriting.

**4. E-Commerce Address Recovery (Digital Footprint)** Standard credit bureaus often lack data on users who are "new to credit." Through integrated, authorized e-commerce checkout networks, the API can fetch recently used delivery addresses along with their exact delivery timestamps.

## API details:

## Endpoint

**POST** /api/v3/address-intelligence/phone-to-address-advance

## Headers

| Header        | Required | Description                          |
| ------------- | -------- | ------------------------------------ |
| Authorization | Yes      | Bearer token/API authorization token |
| Content-Type  | Yes      | application/json                     |

## Request Body

| Field       | Type    | Required | Description                                                                    |
| ----------- | ------- | -------- | ------------------------------------------------------------------------------ |
| phoneNumber | String  | Yes      | 10-digit Indian mobile number whose associated addresses need to be retrieved. |
| callbackUrl | String  | No       | The callback URL where response will be received                               |
| consent     | Boolean | Yes      | Consent to fetch addresses                                                     |

### Sample Request

:::BlockQuote
\{
    "phoneNumber": "90012345678",
    "callbackUrl": "",
    "consent": true
}
:::

## Response

| Field     | Type   | Description                                                |
| --------- | ------ | ---------------------------------------------------------- |
| result    | Object | API result object                                          |
| requestId | String | Request ID to use in the Fetch Result API.                 |
| status    | String | Indicates whether address data exists for the phone number |

### Sample Response

:::CodeblockTabs
200 Response

```json
{
    "result": {
        "requestId": "64c9e525-e42f-41a2-9761-e3ff4c56ea87",
        "status": "processing"
    }
}
```

400 Responses

```none
{
    "result": {},
    "reason": "Bad Request: \"phoneNumber\" must be a valid 10-digit Indian mobile number starting with 6-9",
    "code": "E001"
}

{
    "result": {},
    "reason": "Bad Request: \"callbackUrl\" must be a valid uri with a scheme matching the https pattern",
    "code": "E001"
}

{
    "result": {},
    "reason": "Bad Request: \"consent must always be true\"",
    "code": "E001"
}
```
:::

## Notes

- This API is **supported only for Indian mobile numbers**.