DEWA Bank and Agencies API

Name: DEWA Bank and Agencies API API
Brand: DEWA Bank and Agencies API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingnone2 EndpointsREST

For Agents

Look up outstanding DEWA utility-bill amounts by contract account or bill reference number for partner bank and agency integrations.

Connect the DEWA Bank and Agencies API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DEWA Bank and Agencies API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DEWA Bank and Agencies API API.

Fetch outstanding bill details by DEWA contract account number via /bill/enquiry/contractaccount

Fetch outstanding bill details by reference number via /bill/enquiry/referencenumber

Surface bill amount, currency, and due date for partner-bank pay-bill flows

Validate that a contract account or reference number is currently billable

GET STARTED

Start building with DEWA Bank and Agencies API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for DEWA Bank and Agencies API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for DEWA Bank and Agencies API, keeping it validated and agent-ready. The DEWA Bank and Agencies API lets banks and collection agencies integrated with Dubai Electricity and Water Authority retrieve outstanding utility-bill information for their customers. Two read-only endpoints expose the same data — one keyed on the DEWA contract account number, one on the bill reference number — and both return the outstanding amount, due date, and bill reference details so the calling system can present a payable bill. This is the integration surface partner banks and government agencies use to power 'pay your DEWA bill' flows inside their own apps.

Use Cases

Patterns agents use DEWA Bank and Agencies API API for, with concrete tasks.

★ Pay-Your-DEWA-Bill in a Bank App

Partner banks expose a 'pay DEWA' tile in their mobile app so customers can settle utility bills without leaving the bank. The flow calls /bill/enquiry/contractaccount with the customer's DEWA contract number, displays the outstanding amount and due date, and then routes the payment through the bank's existing rails. Two endpoints, no authentication, sub-second response times.

Call GET /bill/enquiry/contractaccount with the customer's contract account number, display the outstanding amount and due date, and confirm with the user before initiating payment

Collection-Agency Bill Verification

Authorised collection agencies verify outstanding DEWA bills before pursuing a customer for payment. /bill/enquiry/referencenumber accepts the bill reference, returns the current outstanding amount, and confirms the bill has not been paid since the agency last polled. This avoids the embarrassment of chasing a bill that is already settled.

Call GET /bill/enquiry/referencenumber with reference 1234567890, confirm the bill is still outstanding, and update the agency's collection record

Customer-Service Bill Lookup

Customer-service reps at partner banks pull up a customer's DEWA bill while on the phone so they can answer 'how much do I owe?' without bouncing the call to DEWA. Both endpoints respond with the outstanding amount and due date. The two-endpoint design covers both common identifiers customers carry: the long-lived contract account number printed on the meter, and the per-bill reference number on the most recent invoice.

Look up the outstanding bill for contract account 200012345 via GET /bill/enquiry/contractaccount and read the amount due to the customer

AI Agent Bill Concierge

An AI agent embedded in a bank's chat experience uses DEWA via Jentic to answer 'what's my electricity bill?' without holding any DEWA-specific configuration. The agent searches Jentic by intent, loads the schema, and executes the lookup using the contract account the user supplies. Because the API is unauthenticated, the agent can begin returning bill data without any credential management.

Search Jentic for 'look up DEWA outstanding bill', load the contract-account schema, and report the amount due for the user's contract number

Key Endpoints

2 endpoints — jentic publishes the only available openapi specification for dewa bank and agencies api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/bill/enquiry/contractaccount

Outstanding bill enquiry by contract account number

GET

/bill/enquiry/referencenumber

Outstanding bill enquiry by bill reference number

GET

/bill/enquiry/contractaccount

Outstanding bill enquiry by contract account number

GET

/bill/enquiry/referencenumber

Outstanding bill enquiry by bill reference number

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The DEWA Bank and Agencies endpoints declared in this spec carry no authentication header — Jentic still routes calls through its execution layer so agents inherit consistent retry, timeout, and observability behaviour. Any partner-network allow-listing is handled at the deployment edge, not in agent code.

Intent-based discovery

Agents search Jentic by intent — for example 'look up DEWA outstanding bill' — and Jentic returns the matching enquiry endpoint with its parameter schema, so the agent only needs to supply the contract account or reference number.

Time to first call

Direct DEWA integration: a half-day for partner-network onboarding and request shaping. Through Jentic: under an hour — search, load, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Qonto API

Qonto is a banking API that pairs with utility-bill lookups when partner banks build pay-bill flows.

Use Qonto as the payment-rail side of a 'look up bill, then pay' flow once the DEWA outstanding amount is known.

Complementary

Xero Accounting API

Xero accounting can ingest utility-bill amounts as expense entries once they are settled.

Use Xero to record the paid DEWA invoice in the customer's accounting ledger after settlement.

Complementary

Sage API

Sage is an enterprise accounting platform that businesses use to log utility expenses.

Use Sage when the bill payer is a corporate customer that books utility expenses centrally.

FAQs

Specific to using DEWA Bank and Agencies API API through Jentic.

Why is there no official OpenAPI spec for DEWA Bank and Agencies API?

DEWA does not publish an OpenAPI specification on its developer portal. Jentic generates and maintains this spec so that AI agents and developers can call DEWA Bank and Agencies API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the DEWA Bank and Agencies API use?

The Bank and Agencies surface declared in this OpenAPI spec does not include a security scheme — the two enquiry endpoints are accessed over the DEWA partner network without an explicit Authorization header. In production, partner banks and agencies are typically allow-listed at the network level by DEWA. Confirm any onboarding requirements with DEWA before going live.

Can I look up a DEWA bill by reference number?

Yes — GET /bill/enquiry/referencenumber accepts the bill reference number printed on the most recent DEWA invoice and returns the outstanding amount and due date. Use it when the customer has the bill in hand. For long-lived lookups keyed on the meter contract, use /bill/enquiry/contractaccount instead.

What are the rate limits for the DEWA Bank and Agencies API?

Public DEWA documentation does not publish per-partner rate limits. The endpoints are intended for transactional pay-bill flows, not bulk data extraction — call them on demand inside a customer-driven payment journey rather than scraping all contracts. If you receive a throttled response, back off and retry with exponential delay.

How do I look up a DEWA bill in a banking workflow through Jentic?

Run `pip install jentic`, search for 'look up DEWA outstanding bill', load the GET /bill/enquiry/contractaccount schema, and execute with the customer's contract account number. The response carries the outstanding amount and due date which the bank app can render and pass to its payment rail.

Does this API let me actually pay a DEWA bill?

No. The two endpoints are read-only enquiries — they tell you what is outstanding, not how to settle it. Payment is executed through the partner bank or agency's own rails, with the DEWA-issued reference number used to mark the bill paid. Pair this enquiry with your bank's payment API to complete the transaction.