Partners and Accounts - OneClickDz Flexy API

Availability

GET /v3/bills/partners returns one entry per biller with a single status: ACTIVE or UNAVAILABLE.

curl https://api.oneclickdz.com/v3/bills/partners \
  -H "X-Access-Token: YOUR_API_KEY"

{
  "success": true,
  "data": {
    "ADE": { "status": "ACTIVE" },
    "AADL": { "status": "ACTIVE" },
    "SONELGAZ": { "status": "ACTIVE" },
    "SEAAL": { "status": "ACTIVE" },
    "SEOR": { "status": "ACTIVE" },
    "Algérie Télécom": { "status": "UNAVAILABLE" }
  },
  "meta": { "timestamp": "2026-09-20T10:15:32.194Z" },
  "requestId": "req_9f3a1c72e0b84d51aB3xZq07"
}

An UNAVAILABLE biller answers 503 PARTNER_UNAVAILABLE on discover and pay. Read this map when you build your biller picker and hide what is unavailable; availability changes without notice.

A production key sees live availability. A sandbox key sees every biller ACTIVE, because sandbox requests never reach a biller.

The partner name

partner is the exact key from the map above. Algérie Télécom is written with its accents and a space; any other spelling is rejected with 400 ERR_VALIDATION.

The account object

account contains exactly one identifier, and the identifier must be the one the biller understands. The table below is the complete list.

Partner	`account`	Where the customer finds it
`ADE`	`{ "electronic_payment_key": "…" }`	Clé de paiement électronique on the water bill, 25 characters
`SONELGAZ`	`{ "sonelgaz": { "invoice_number", "amount_without_stamp", "ebb_key" } }`	Numéro de facture, montant hors timbre and clé EBB on the electricity/gas bill
`SEAAL`	`{ "seaal": { "code_client", "code_contrat" } }`	Code client and code contrat on the SEAAL water bill
`AADL`	`{ "aadl": { "codeloc" } }`	Code logement of the AADL housing file
`SEOR`	`{ "seor": { "contrat", "facture" } }`	N° Contrat and N° Facture on the SEOR water bill
`Algérie Télécom`	`{ "phone_number": "…" }`	The landline number

ADE

{
  "partner": "ADE",
  "account": { "electronic_payment_key": "0123456789012345678901234" },
  "ref": "disc-20260920-0001"
}

electronic_payment_key is exactly 25 characters. Each key identifies one bill.

SONELGAZ

{
  "partner": "SONELGAZ",
  "account": {
    "sonelgaz": {
      "invoice_number": "313260119713",
      "amount_without_stamp": "28491.72",
      "ebb_key": "169"
    }
  },
  "ref": "disc-20260920-0002"
}

All three fields are required strings, copied as printed on the bill. amount_without_stamp is the amount before the fiscal stamp, with a dot as decimal separator. The biller validates the three values together; a mismatch ends the discovery with INVALID_ACCOUNT.

SEAAL

{
  "partner": "SEAAL",
  "account": { "seaal": { "code_client": "100001", "code_contrat": "446563" } },
  "ref": "disc-20260920-0003"
}

code_client is 2 to 6 alphanumeric characters, code_contrat is 2 to 10 digits. Both are required. A SEAAL account can carry several unpaid quarterly bills; discovery returns all of them.

AADL

{
  "partner": "AADL",
  "account": { "aadl": { "codeloc": "1112223334" } },
  "ref": "disc-20260920-0004"
}

codeloc is 6 to 20 digits. AADL issues one aggregate notice per housing file. Arrears are included in that single amount and cannot be paid separately.

SEOR

{
  "partner": "SEOR",
  "account": { "seor": { "contrat": "100001", "facture": "00102026S000000001" } },
  "ref": "disc-20260920-0006"
}

contrat is 1 to 6 digits; bills print it with a space (284 932) and spaces are ignored. facture is 18 letters or digits. Both are required. SEOR (Oran water) is single-bill: discovery returns exactly the facture you sent. SEOR cannot tell a wrong pair from a facture already paid at an agency, so INVALID_ACCOUNT for SEOR means “invalid information or bill already paid”.

Algérie Télécom

{
  "partner": "Algérie Télécom",
  "account": { "phone_number": "023456789" },
  "ref": "disc-20260920-0005"
}

phone_number is a 9-digit landline: 0, then 2, 3 or 4, then 7 digits. Mobile numbers are not accepted.

What the API echoes back

Every transaction returns the identifier under account, flat, with a key that depends on the partner:

Partner	`account` in responses
`ADE`	`{ "reference": "<electronic_payment_key>" }`
`SONELGAZ`	`{ "contractNumber": "<invoice_number>" }`
`SEAAL`	`{ "codeClient": "<code_client>" }`
`AADL`	`{ "codeloc": "<codeloc>" }`
`SEOR`	`{ "facture": "<facture>" }`
`Algérie Télécom`	`{ "phoneNumber": "<phone_number>" }`

These keys are output only. Use the request shapes above when you send.

Integrations built before this page send reference (ADE) or phoneNumber (Algérie Télécom) as the identifier. Both are still accepted and mapped to electronic_payment_key and phone_number; new integrations should use the shapes above.

Validation errors

Error	HTTP	Cause
`ERR_VALIDATION`	400	Unknown partner, missing field, wrong format, or more than one identifier. `details` lists each problem.
`INVALID_ACCOUNT`	400	Sandbox only: the invalid-account test accounts answer immediately. In production a rejected identifier surfaces on the transaction.

A 400 never creates a transaction. When the identifier is well formed but the biller does not recognise it, the discovery is accepted and later ends FAILED with error.code = INVALID_ACCOUNT (see Discovering bills).

Next: Discovering bills

Start a discovery and read the bills

​Availability

​The partner name

​The account object

​ADE

​SONELGAZ

​SEAAL

​AADL

​SEOR

​Algérie Télécom

​What the API echoes back

​Validation errors

Next: Discovering bills

Availability

The partner name

The account object

ADE

SONELGAZ

SEAAL

AADL

SEOR

Algérie Télécom

What the API echoes back

Validation errors