Skip to main content

Content types and data formats

Overview​

This article describes the common data formats used in the API and how to parse them correctly. Using consistent parsing ensures your application processes data reliably across regions and systems.

Content types​

Content type refers to the media type of the data being sent in a request or returned in a response. It tells the client and server how to interpret the body of the message.

The primary content type supported by the Akkuro Lending REST API is application/json. The server only accepts and returns data in JSON format. To specify the content type for requests and responses, use the following headers:

  • Content-Type: Indicates that the request body format is JSON.
  • Accept: Indicates that the response format is JSON.
Note

For most API requests that have a request body, the server only accepts JSON. Make sure you specify the content type as application/json and do not use any other format, or the request will fail.

We also support two additional content types specifically for streaming data responses:

  • application/jsonl: Indicates that the response format is JSON Lines.
  • application/json-seq: Indicates that the response format is JSON Text Sequences.

Refer to Streaming data for further information.

Data formats​

Property names​

All property names use lower camel case (lowerCamelCase). This means each name first starts with a lowercase letter, and each subsequent word starts with an uppercase letter. Words are not separated by underscores.

Examples of the correct format:

  • firstName
  • dateOfBirth
  • preferredCommunicationLanguage
  • frequency

Example of the incorrect format:

  • date_of_birth

Dates and times​

Date and time values follow the ISO 8601 standard as implemented in RFC 3339.

Date only​

Format: yyyy-MM-dd

Each component has the following meaning:

  • yyyy: Four-digit calendar year.
  • MM: Two-digit month.
  • dd: Two-digit day of the month.

For example:

{
    "dateOfBirth": "1968-11-19"
}

Datetime​

Format: yyyy-MM-ddTHH:mm:ss.SSSZ

Each component has the following meaning:

  • T: Acts as a separator between the date and time components, indicating that the following characters represent the time.
  • HH: Two-digit hour in 24-hour format.
  • mm: Two-digit minute.
  • ss: Two-digit second.
  • SSS (optional): The milliseconds portion.
  • Z: UTC indicator.

For example:

This value indicates July 22, 2025, at 3:30 AM UTC.

{
    "updatedOn": "2025-07-22T03:30:00.955Z"
}

Countries​

Country codes follow the ISO_3166-1_alpha-2 standard. Each country is represented by a two-letter uppercase code.

See the official ISO 3166-1 alpha-2 code table for a full list of country codes.

For example:

  • NL: Netherlands
  • CH: Switzerland
  • GB: United Kingdom
  • US: United States

Languages​

Language tags follow the BCP 47 standard. A langIn addition to language subtags, tags may include a region subtag, separated by a hyphen (-).

For example:

  • en: English
  • nl: Dutch
  • en-US: American English
  • en-GB: British English
  • nl-NL: Standard Dutch

Currencies​

Currency codes use the ISO 4217 three-letter standard.

For example:

  • USD: United States Dollar
  • EUR: Euro
  • CHF: Swiss franc

Enumerations​

An enumeration (enum) restricts a property to a predefined set of string values. Enumeration values are case-sensitive.

For example:

{ 
    "status": "APPROVED" 
}

Valid values might include: "APPROVED", "REJECTED", "PENDING". Therefore, if you send "ACTIVE" or "Approved", the API will reject the request because the value is not part of the enumeration.

Money objects​

A money object represents an amount in the main currency unit. The minor unit (such as cents) appears after the decimal point. Negative values indicate refunds or deductions. Thousands separators are not used. For example:

  • 42.20 represents 42 euros and 20 cents
  • 0.23 represents 23 cents
  • 42.00 represents 42 euros
  • 1024.42 represents 1,024 euros and 42 cents
  • 1024.4225 represents 1,024 euros and 42.25 cents (with fractional cents)

Percentages​

Percentages are represented as decimal numbers between 0 and 1. Values must be sent as decimals, not percentages. For example:

  • 0.25 represents 25%
  • 0.0575 represents 5.75%
  • 1 represents 100%

See also​

See Status codes and responses for details on error formats.