Data Types

Understand the required data types for integrating with Bamboo, including formats for strings, numbers, amounts, dates, and transaction fields.

This page describes the main data types used across Bamboo’s API for request and response parameters.

📘

These definitions apply primarily to Payins. Some data types (e.g. Amount, Timestamp) may differ in Payout operations. Always refer to the respective API guide for each product.


String

Represents a sequence of characters. Strings must be encoded in UTF-8. Maximum length is defined per field in the API reference.

Example values:

  • "Juan"
  • "Compra 001"
  • "USD"

Numeric

Represents a positive integer. Length can be restricted using square brackets (e.g. Numeric[3] = max 3 digits).

Examples:

  • 123 → ✅ Valid for Numeric[3]
  • 1004 → ❌ Invalid for Numeric[3]

Amount

Special type of Numeric used to express monetary values.

Amounts must be sent without punctuation and include exactly two decimal places, even when zero.

Value (human-readable)Coded as
10010000
1,237.52123752
3,200.5320050
0.011

Always express the amount in minor currency units (e.g. cents).


Timestamp

Represents a full date and time with milliseconds.

"YYYY-MM-DDTHH:mm:ss.ttt"

Where:

  • YYYY indicates the year
  • MM indicates the month
  • DD indicates the day
  • T indicates the beginning of the required time section
  • hh indicates the hour (from 0 to 23)
  • mm indicates the minutes
  • ss indicates the seconds
  • ttt indicates the milliseconds

Below are examples of how values should be codified:

ValueCoded as
2016/01/12 13:21:48.3542016-01-12T13:21:48.354
2016/03/31 05:17:00.0002016-03-31T05:17:00.000
2016/11/28 22:59:59.9702016-11-28T22:59:59.970

Date

This data type contains an exact date. Unlike the TimeStamp data type, it does not include hours and is in the following format:

yyyyMMdd


Boolean

This data type is a logical value (true or false).


Enum

Represents a field with a restricted set of string values.

Example:

  • Status: "APPROVED", "REJECTED", "PENDING"

Each enum is documented in the field description or API reference.


Object

Complex field containing nested subfields. Objects follow JSON structure and may contain other types (e.g. strings, booleans, or arrays).

Example:

"Customer": {
  "FirstName": "María",
  "Email": "[email protected]"
}



What’s Next?