Skip to main content
POST
cURL

Authorizations

Authorization
string
header
required

Access token JWT. Use as Authorization: Bearer . In the API playground, paste the JWT only.

X-Fluide-Api-Key
string
header
default:fl_dev_your_key
required

Developer API key (fl_dev_...). Required on every API call with a machine access token.

X-Fluide-Client-Id
string
header
default:fluide-developer
required

First-party client audience. Must match the fluide_client_id claim on the JWT. Use fluide-developer for Connect.

Headers

X-Workspace-Id
string<uuid>

Partner / ISV only: UUID of the workspace that owns the client company. Required together with X-Acting-Company-Id when scoping product APIs to a merchant. See /getting-started/multi-tenancy.

X-Acting-Company-Id
string<uuid>

Partner / ISV only: UUID of the client company to act on. Must belong to the workspace in X-Workspace-Id.

Body

application/json
request_id
string
required

Unique request identifier

Example:

"2323V"

request_type
string
required

Type of remittance

Example:

"ECOBANKAFRICA"

receiverLastName
string
required

Receiver last name

Example:

"Kasumu"

sourceCountry
string
required

Source country

Example:

"NG"

senderNationality
string
required

Sender nationality

Example:

"GH"

senderPhoneNumber
string
required

Sender phone number

Example:

"07066690519"

destinationBank
string
required

Destination bank

Example:

"NG"

purpose
string
required

Purpose of transfer

Example:

"Travel"

receiverCcy
string
required

Receiver currency

Example:

"USD"

secureHash
string
required

Secure hash for request validation

Response

Remittance result

success
boolean
required

Whether the request succeeded

Example:

true

message
string
required

Human-readable outcome message (localized when i18n is configured)

Example:

"Operation completed successfully"

data
object

Endpoint-specific payload