Requests and responses - Mojo Payments Knowledge Base

Send and receive JSON (Content-Type: application/json). Field names are camelCase.
Every request needs Authorization: Bearer <token> (Authentication), except POST /oauth/token.
A request acts for the organization the API key belongs to. You don’t name the organization in the request.

Values

Kind	Format	Example
Ids	GUIDs, as strings; deposits and card payments have whole-number ids	`"a3c5e7f9-1b2d-4c6e-8f0a-2b4d6f8a0c1e"`, `48213`
Amounts	Dollars as JSON numbers, two decimals	`50.00`
Dates you send	`YYYY-MM-DD`	`"2026-10-31"`
Dates in responses	Midnight of that day, as a time	`"2026-10-31T00:00:00"`
Times	ISO 8601 in UTC, without an offset	`"2026-10-05T21:45:54.151"`
MIDs	Strings of digits	`"496100000000"`

A value that isn’t set comes back as null.

Status codes

Code	Means
`200`	OK, with the result.
`201`	Created. The `Location` header gives the new record’s address.
`204`	Done, with nothing to return.
`400`, `422`	The request can’t be done as sent: see Errors.
`401`	No token, or it expired: get a new one.
`403`	The key doesn’t have the permission this needs.
`404`	No such record, or not one your key can see.
`429`	Too many requests: see Rate limits.

Changes

Mojo Payments adds to the API without breaking it: new endpoints, and new fields in responses. Read responses so that a field you don’t know is ignored. A change that would break integrations will be announced first.