Data Format

Understanding the specific data formats expected for various parameters and request payloads is essential for effectively interacting with the Braid API. This section outlines the required formats for several key parameters and provides specific examples to illustrate their usage.

  1. updatedEnd:
  • Description: The end date/time for the search, formatted according to the ISO 8601 standard.
  • Format: YYYY-MM-DDTHH:MM:SS.sssZ (e.g., 2022-09-30T19:35:01.058Z)
  • Example: updatedEnd=2022-09-30T19:35:01.058Z
  1. updatedStart:
  • Description: The start date/time for the search, formatted according to the ISO 8601 standard.
  • Format: YYYY-MM-DDTHH:MM:SS.sssZ (e.g., 2022-09-01T19:35:01.058Z)
  • Example: updatedStart=2022-09-01T19:35:01.058Z
  1. amount:
  • Description: The amount to be transacted must be greater than 0 and can use decimal points with xx.xx as the required format.
  • Format: Decimal number with two decimal places (e.g., 100.50)
  • Example: amount=100.50
  1. ACH transaction:
  • Description: Indicates whether the ACH transaction is inbound (true) or outbound (false).
  • Format: Boolean value (true/false)
  • Example: ACH transaction=true

These examples demonstrate the expected format for key parameters when making requests to the Braid API. It is important to adhere to these formats to ensure successful communication with the API and accurate processing of requests. Additionally, developers should refer to the API documentation for specific endpoints to determine any additional parameters or formatting requirements relevant to their use cases.