Skip to main content
GET
List Partners

Overview

Returns the availability of every supported biller. Call it before a discovery so you can hide an unavailable partner from your customers instead of letting them hit a 503 at the end of a form. The response is a map keyed by the exact partner value you send to Discover Bills — including the accents in Algérie Télécom.
A PRODUCTION key sees live availability. A SANDBOX key sees a fixed map, because a sandbox request never reaches a partner and live availability would be misleading there.

Response

boolean
required
true when the map was returned.
object
required
One entry per partner. The key set is fixed.
Each entry has a single field:
string
required
ACTIVE — discovery and payment are accepted.UNAVAILABLE — discovery and payment for this partner answer 503 PARTNER_UNAVAILABLE.
object
required
string
required
Correlation identifier, also sent as the X-Request-Id response header.

Examples

Success Response

Error Responses

The X-Access-Token header was not sent.
What to do: add the header and retry.
The key was rejected.
What to do: verify the key with Validate API Key.
We could not verify your key in time.
What to do: retry after the Retry-After header. Serve the last cached map in the meantime.
The Bill Payment API is in planned maintenance.
What to do: honour Retry-After and retry.

Current availability

SEAAL and AADL are currently UNAVAILABLE in both sandbox and production, and discovery or payment for them answers 503 PARTNER_UNAVAILABLE. This is the operator’s current setting, not a permanent limitation — keep both partners in your code and let this endpoint decide what to show.
Do not hard-code the availability of any partner. Read this map, and treat 503 PARTNER_UNAVAILABLE on a discovery as a partner that went unavailable between your last refresh and the request.

Caching the map

Availability changes rarely. Refresh it on a timer rather than before every discovery, and keep serving the last good copy when a refresh fails.

Best Practices

Cache for a few minutes

A 5-minute cache is enough. Calling this before every discovery adds a round trip and buys nothing.

Fail soft on refresh

If the refresh fails, keep the previous map. An empty partner list is worse than a slightly stale one.

Use the exact partner value

Send Algérie Télécom with its accents. The value is the key of this map, character for character.

Handle the race

A partner can become unavailable after you cached it. Handle 503 PARTNER_UNAVAILABLE on discovery too.

Validate API Key

Confirm your key and environment

Discover Bills

Look up what an account owes

Partners and Accounts

Identifiers for each partner

Bill Payment Overview

How the whole flow fits together