Conventions
Motenya ids are ULIDs, 26 characters, such as 01JD3Q8Z4X5Y6W7V8T9S0R1Q2P. Records you sync also keep your own ids; see the sync guide.
Amounts and currencies
Section titled “Amounts and currencies”Amounts are decimal strings, such as "389.90", never floating-point numbers, so nothing is lost in transit. Each amount comes with an ISO 4217 currency code (RON, EUR). Totals are always given per currency: Motenya never converts between currencies.
Instants are ISO 8601 date-times in UTC, such as 2026-11-21T09:30:00.000Z. Send any ISO 8601 date-time with an offset.
Enum values
Section titled “Enum values”CRM values are lowercase, such as on_hold, partially_paid and month, both in what you send and in what you get back. Ticket values are uppercase, such as OPEN and URGENT.
Pagination
Section titled “Pagination”Lists return { "items": [...], "nextCursor": "…" }. Pass nextCursor as after for the next page; it is null on the last page. first sets the page size, from 1 to 100 (default 25).
Partial updates
Section titled “Partial updates”PATCH and sync calls change only the fields you send. Send null to clear an optional field. A list field you send, such as an order’s items, replaces the whole list.
Custom fields
Section titled “Custom fields”Contacts, clients, catalog items, orders and subscriptions can carry custom fields that the account defines. Their values go in custom, keyed by the field’s key (see GET /products/{productId}/custom-fields). Setting a key to null clears that value.
Unknown fields
Section titled “Unknown fields”Responses may gain fields over time. Ignore the ones you do not know.