Skip to main content
Migo Docs

Process Requests

RESTRICTED API

Requires partner / operator authorization. See CMS → Home.

A process request is a partner balance top-up (balance increase) request. An operator submits the requested amount together with an evidence file (PDF or image); another operator then approves or rejects it. Once approved, the partner's available balance is credited.

All paths use the partner/client identifier in the URL. Every call requires both auth headers (Authorization: Bearer <app-access-token> and x-user-token: Bearer <cms-user-token>).

Create a balance process request​

multipart/form-data with a single evidence file (PDF, JPEG, PNG, or WEBP, max 10 MB). OTP is required when the operator is subject to OTP elevation.

curl -X POST "https://api.ali.app/cms/rest/app/partners/{partnerId}/process-request" \
  -H "Authorization: Bearer <token>" \
  -H "x-user-token: Bearer <cms-user-token>" \
  -F "evidence=@deposit-receipt.pdf" \
  -F "requestedAmount=10000" \
  -F "observations=Wire transfer received on 2026-03-01" \
  -F "otp=123456"

Body fields:

  • requestedAmount (number, required) — amount of the balance increase.
  • observations (string) — notes describing the request.
  • otp (string, optional) — 6-digit code, required only when the operator is subject to OTP.
  • evidence (file, required) — the supporting document.

Get partner available balance​

curl "https://api.ali.app/cms/rest/app/partners/{clientId}/balance" \
  -H "Authorization: Bearer <token>" \
  -H "x-user-token: Bearer <cms-user-token>"

Returns { id, clientId, available, currency, updatedAt, createdAt }.

List process requests (paginated)​

curl "https://api.ali.app/cms/rest/app/partners/{clientId}/process-requests?page=1&limit=10" \
  -H "Authorization: Bearer <token>" \
  -H "x-user-token: Bearer <cms-user-token>"

Query params: page (default 1), limit (default 10).

A non-paginated listing is also available:

curl "https://api.ali.app/cms/rest/app/partners/{clientId}/process-request" \
  -H "Authorization: Bearer <token>" \
  -H "x-user-token: Bearer <cms-user-token>"

Each request item exposes { id, processTypeId, clientBalanceId, requestedAmount, evidenceUrl, status, ... }, where status is one of PENDING, APPROVED, REJECTED.

Download evidence​

Returns a pre-signed download URL for the request's evidence file.

curl "https://api.ali.app/cms/rest/app/partners/{clientId}/process-request/{processRequestId}/evidence/download" \
  -H "Authorization: Bearer <token>" \
  -H "x-user-token: Bearer <cms-user-token>"

Approve or reject a request​

The action path parameter is either approve or reject. Returns 204 No Content on success.

curl -X PATCH "https://api.ali.app/cms/rest/app/partners/{partnerId}/process-request/{processRequestId}/approve" \
  -H "Authorization: Bearer <token>" \
  -H "x-user-token: Bearer <cms-user-token>"

curl -X PATCH "https://api.ali.app/cms/rest/app/partners/{partnerId}/process-request/{processRequestId}/reject" \
  -H "Authorization: Bearer <token>" \
  -H "x-user-token: Bearer <cms-user-token>"

A request that is not pending review returns 409 Conflict.

Cancel a request​

curl -X PATCH "https://api.ali.app/cms/rest/app/partners/{partnerId}/process-request/{processRequestId}/cancel" \
  -H "Authorization: Bearer <token>" \
  -H "x-user-token: Bearer <cms-user-token>"

Progress stream (SSE)​

Subscribe to real-time progress while a request is being processed. Like the bulk upload stream, the connection emits unnamed data: frames and is in-memory / single-pod.

curl "https://api.ali.app/cms/rest/app/partners/{clientId}/process-request/progress" \
  -H "Authorization: Bearer <token>" \
  -H "x-user-token: Bearer <cms-user-token>" \
  -H "Accept: text/event-stream" \
  --no-buffer