BrandKwikID Documentation
API SuiteUtility Bills

Electricity Bill Details

Fetch electricity bill metadata for a consumer and provider. Server-side GET with Bearer auth; consumer and provider are path segments.

API reference

Try itLoading playground…
Loading…
AuthorizationBearer <token>

JWT Bearer token authentication. Obtain a token from the KwikID dashboard.

In: header

Path Parameters

consumer_number_inunknown

The consumer number.

Default""
Formatstring
provider_inunknown

The name of the provider (mahavitran/ adani)

Default""
Formatstring

Response Body

curl -X GET "https://__mock__/verification/v2/electricity/getbill//"
{
  "message": "string"
}
{
  "detail": {
    "<location>": {
      "<field_name>": [
        "string"
      ]
    }
  },
  "message": "string"
}
{
  "detail": {},
  "message": "string"
}

Overview

Call GET /verification/v2/electricity/getbill/{consumer_number_in}/{provider_in} from your backend with Authorization: Bearer <token>. Replace consumer_number_in with the utility consumer number and provider_in with the provider slug your KwikID account supports (see OpenAPI parameter hints such as mahavitran or adani).

Key features

  • Address or identity corroboration using a recent bill snapshot.
  • No JSON body: Path-only GET after you map the provider slug in your product config.

Implementation

Step 1: Call from your backend

GET /verification/v2/electricity/getbill/<consumer_number>/<provider_slug> HTTP/1.1
Host: <verification-api-base-url>
Authorization: Bearer <token>

URL-encode segments if they contain reserved characters.

Error handling

HTTP statusWhen
400Unknown provider or bad consumer id.
401Invalid token.

Security notes

  • Bill payloads can include PII; store under your data policy.

Benefits

  • Automates utility proof checks without manual PDF review.

Next steps