Skip to main content
VerifyAll logo
Coming soonInstant answer

LPG Connection Verification API

Send a 17-digit LPG ID and get back who holds the connection, its address and status, the distributor and the last refill booking. Opening soon.

The LPG Connection Verification API is coming soon and not yet open to customers. Request early access and we will tell you as soon as it opens.

Request early access Book a demo View API documentation

The documentation opens in the VerifyAll dashboard after sign-in, for accounts with approved API access. New to the API? Start with the developer guide.

Overview

What the LPG Connection Verification API does

The LPG Connection Verification API will look up a domestic cooking-gas connection by its 17-digit LPG ID and answer with the name the connection is in, the consumer number at the distributor, the connection’s address with city and PIN code, whether it is active or suspended, the distributor’s name, code and address, and the date the last refill was booked. It is coming soon to the Developer API and is not open for calls yet; request early access to be told when it opens.

A domestic LPG connection belongs to a household at an address, which makes it a useful second signal of where a person lives. Send the name and the address you hold along with the LPG ID and the answer compares them for you: name_match grades the name as exact, partial or mismatch, and address_match grades the address as match, partial or mismatch, each with a score from 0 to 100.

Lenders, insurers, rental platforms and field-verification teams can use it where an address has to be confirmed without a visit. Customers find their 17-digit LPG ID on their LPG company’s website, under the option to find or know the 17-digit LPG ID. Once the API opens, a Sandbox key will return sample data and is never charged, and Production key calls will be charged from your prepaid wallet.

How it works

  1. 1

    Your server will send POST /universal/lpg-connection-verification with the lpg_id, a consent object and, if you want them compared, the name and the address you hold. client_ref is optional.

  2. 2

    The request is checked first: an LPG ID that is not 17 digits, or a missing consent object, is refused with a 400 and the list of problems before anything runs or is charged. Spaces and dashes in the LPG ID are removed for you.

  3. 3

    The connection is checked against live records and the answer comes back in the same call, in VerifyAll’s standard JSON envelope, with name_match and address_match filled in when you sent a name or an address.

  4. 4

    The result is stored in your VerifyAll account with a checkResultId, so you can read it again with GET /check-results/{id} and find it by your client_ref.

Request and response

LPG connection verification API endpoints and fields

The main fields; the full reference with every field, error code and a cURL sample is in the dashboard docs.

Endpoints
EndpointWhat it does
POST/universal/lpg-connection-verificationVerify a domestic LPG connection by its 17-digit LPG ID (opening soon)

Request fields

LPG Connection Verification API request fields
FieldWhat it is
lpg_idRequiredThe 17-digit LPG ID of the connection. Spaces and dashes are removed before the check.
consentRequiredobtained (must be true) and purpose (why the check is run, up to 200 characters). Required on every check about a person.
nameOptionalOptional. The name to compare with the name on the connection (2 to 120 characters); sets name_match.
addressOptionalOptional. The address to compare with the connection’s address (up to 500 characters); sets address_match.
client_refOptionalYour own reference, stored with the result (up to 100 characters). The X-Client-Ref header does the same.

What the answer returns

LPG Connection Verification API answer fields
FieldWhat it is
lpg_id / statusThe LPG ID checked, and the connection’s status in lower case, for example active or suspended.
consumer_name / consumer_numberThe name the connection is in, and the consumer number at the distributor.
name_matchresult (exact, partial, mismatch or not_checked) and a score from 0 to 100; not_checked when no name was sent or none is on record.
addressThe connection’s address with city and PIN code.
address_matchresult (match at a score of 75 or more, partial at 50 to 74, mismatch below 50, or not_checked) and the score from 0 to 100.
distributorThe distributor the connection is with: name, code and address.
last_booking_onWhen the last refill was booked, YYYY-MM-DD.

Base URL https://api.verifyall.ai. Authenticate with the X-API-Key header (a va_sandbox_ or va_live_ key). Every answer carries data, status_code, success, message and message_code; checks add outcome, checkResultId, charged and charged_amount.

Key features

LPG Connection Verification API features and capabilities

  • Name and address compared for you

    Send what the customer gave you and read a graded result with a score, instead of building your own fuzzy match.

  • Address with PIN code

    The connection’s address comes with city and PIN code, ready to set beside the address on an application.

  • Status and last booking

    status and last_booking_on show whether the connection is active and when a refill was last booked.

  • Format checked before any charge

    An LPG ID that is not 17 digits is refused with a list of problems before the check runs, so a typing error costs nothing.

Use cases

Where businesses use the LPG Connection Verification API

  • Address confirmation in lending

    Add a connection at the declared address to a borrower’s file where a field visit is not practical.

  • Rental and housing platforms

    Confirm a tenant’s or an owner’s current address during onboarding.

  • Insurance proposals

    Check the residential address given on a home or health insurance proposal.

  • Field verification teams

    Narrow down which applications still need a physical address visit.

Industries

Coverage

Domestic LPG connections in India, looked up by their 17-digit LPG ID.

Limitations to plan for

  • Coming soon: the endpoint is not open for calls yet. Request early access and VerifyAll will tell you when it opens.
  • The check needs the 17-digit LPG ID; it does not search by name, mobile number or address.
  • An LPG ID with no record answers record_not_found. The lookup ran, so it is charged like any completed check.
  • The address returned is the address of the connection. It confirms the connection, not that the person lives there today.

Integration

How to integrate the LPG Connection Verification API

From a business account to your first live call.

  1. Step 1

    Create a business account on VerifyAll and get it approved, as for running checks in the dashboard.

  2. Step 2

    Request Developer API access under Developers in the dashboard: the APIs you need, your expected monthly volume and your use case. The VerifyAll team reviews it and shares the API Services Agreement.

  3. Step 3

    Once the agreement is signed and access is approved, create your Sandbox key and build against sample data. Sandbox calls are never charged.

  4. Step 4

    Create your Production key, recharge your wallet and switch the key in your code: the endpoint and fields stay the same.

Get started

Request early access to the LPG Connection Verification API

Tell us what you want to verify. We reply within one business day with access steps, Sandbox details and your API pricing.

Tell us about your integration

Tell us what you want to verify and how many checks you expect. Our team replies within one business day with access steps, Sandbox details and your API pricing.

We use these details only to reply to your request. See our privacy policy.

  • Contact sales

    Questions on volumes, onboarding or the API agreement.

    Contact sales

  • View API documentation

    The full reference for LPG Connection Verification API (endpoints, fields, errors, cURL) opens in the dashboard once your access is approved.

    Open the docs (sign-in)

  • Create a business account

    API keys are issued to an approved business account. Sign up, then request access under Developers.

    Create account

Pricing

Production calls are charged per check from your prepaid VerifyAll wallet, at your account’s API price; GST is added separately when you recharge. Sandbox calls are never charged. Your API prices are shown in the dashboard once access is approved. How pricing works

Already have a business account? Sign in to request access

LPG Connection Verification API: frequently asked questions

Answers for teams planning an integration.

Still have questions? Our team is happy to help.

Contact Support

All other verifications APIsRun LPG connection verification in the dashboard, without codeBrowse the API Marketplace

Start with the LPG Connection Verification API

Request access, build against the Sandbox, then go live with your Production key.

Request early access