Taxi-Sahbi API actions

Connect first, then click each action separately. Each result appears below its button.

Private UAT test file — contains your client secret. Keep it private. No API runs until you click a button. Local proxy connected. API requests go through this local server to UAT. Keep the launcher running.

1. Connect to UAT

API base URL

Client IDClient secret

Not connected. Token stays in memory until you close or reload this page.

2. Onboard a merchant driver

Enter firstName and lastName once in Driver JSON; personal details fill automatically. Use the driver's details. The server links the driver to the configured main merchant. Complete the steps in order; IDs and the OTP reference fill automatically.

Device IDOnboarding ID

2.1 Create / find driver

Driver JSON

2.2 Send OTP

2.3 Verify OTP

OTP referenceDriver's OTP

2.4 Generate PIN

Driver's chosen PIN (4–6 digits)

2.5 Save business details

Replace empty fields with actual reference IDs and bank details. Save once, upload business documents below, then add professionalAddress and license-specific fields and save again.

License typeMonthly volume

Select the license, monthly volume and bank. Activity and sub-activity use the fixed settings.

Moroccan bankBusiness JSON

2.6 Upload documents (repeat per file)

Upload business documents before the second business save. Upload identity documents after saving personal details.

Document typeShareholder ID (optional)

Document file

2.7 Save personal details

Personal details JSON

Dates use dd-MM-yyyy. Use the driver's actual nationality ID and identity details. Wallet provisioning and applicable document checks still depend on the backend.

2.8 Upload CNIE front

Upload the driver’s CNIE front after saving personal details. Uses the current onboarding ID.

CNIE front file

2.9 Upload CNIE back

Upload the driver’s CNIE back after saving personal details. Uses the current onboarding ID.

CNIE back file

3. Get drivers list

Page (starts at 0)Page size (1–100)

4. Main merchant → MerchAgent

Moves MAD between the server-configured wallets. Keep the same reference and amount when retrying. Click “New reference” only for a separate transfer.

Reference IDAmount (MAD)

5. MerchAgent → drivers

Enter 1–100 driver user IDs from the list and their amounts. This sends one atomic batch. Keep the same reference and payload when retrying.

Reference IDDriver payments JSON

6. Generate QR for main merchant

Enter the main merchant name and city. Receiver number and MCC come from the fixed settings. This generates a dynamic QR; it does not make a payment.

Main merchant receiver numberAmount (MAD)Main merchant name (max 25)City (max 15)Assigned MCC (4 digits)Reference ID (max 25)