logo
ReferenceData dictionary

Data dictionary

Detailed description of entities, fields, and enumerations in the API

Overview

This dictionary documents the entities returned by the API, their fields, types, and allowed values. Use it as a reference when building your integration.


Main entities

CardTransaction

Represents a credit card purchase or related operation.

FieldTypeRequiredDescription
idstringYesUnique transaction id
operationenumYesOperation type (see values)
transactionDatestringYesTransaction time (ISO 8601)
statusenumYesStatus (see values)
typeenumYesTransaction type (see values)
merchantstringYesMerchant name
amountBrlnumberYesAmount in Brazilian Reais (BRL)
exchangeRateUsdnumberYesUSD rate (for international)
isCanceledbooleanYesCanceled or not
isConciledbooleanYesReconciled or not
installmentnumberYesInstallment number (1 = paid in full)
cardCardYesCard used for the purchase
categoryCategoryYesExpense category
costCenterCostCenterYesCost center
attachmentsarray[Attachment]YesLinked receipts and documents

Example

{
  "id": "txn_abc123",
  "operation": "CASH_OUT",
  "transactionDate": "2025-01-15T14:30:00.000Z",
  "status": "PROCESSED",
  "type": "PURCHASE",
  "merchant": "UBER *TRIP",
  "amountBrl": 45.90,
  "exchangeRateUsd": 0,
  "isCanceled": false,
  "isConciled": true,
  "installment": 1,
  "card": {
    "id": "card_xyz789",
    "maskedNumber": "**** **** **** 1234",
    "responsibleName": "John Smith",
    "responsibleEmail": "john@company.com",
    "type": "VIRTUAL"
  },
  "category": {
    "id": "cat_001",
    "name": "Transport"
  },
  "costCenter": {
    "id": "cc_001",
    "name": "Sales"
  },
  "attachments": []
}

Card

A physical or virtual credit card.

FieldTypeRequiredDescription
idstringYesCard id
maskedNumberstringYesMasked PAN (e.g. **** **** **** 1234)
responsibleNamestringYesPerson responsible for the card
responsibleEmailstringYesThat person’s email
typeenumYesCard type

Example

{
  "id": "card_xyz789",
  "maskedNumber": "**** **** **** 1234",
  "responsibleName": "Jane Doe",
  "responsibleEmail": "jane@company.com",
  "type": "PHYSICAL"
}

Category

Expense category for classification.

FieldTypeRequiredDescription
idstringYesCategory id
namestringYesCategory name

Example

{
  "id": "cat_001",
  "name": "Meals"
}

CostCenter

Cost center for expense allocation.

FieldTypeRequiredDescription
idstringYesCost center id
namestringYesCost center name

Example

{
  "id": "cc_001",
  "name": "Marketing"
}

Attachment

A file linked to a transaction (receipt, invoice, etc.).

FieldTypeRequiredDescription
idstringYesAttachment id
namestringYesFile name
_linksobjectNoHATEOAS links to the content

Example

{
  "id": "att_001",
  "name": "receipt.pdf",
  "_links": {
    "content": {
      "href": "/attachments/v1/content/att_001",
      "rel": "GET"
    }
  }
}

Download binary content with GET /attachments/v1/content/{attachmentId} in the API Reference.


Enumerations

operation

Direction of the financial movement.

ValueDescription
CASH_INMoney in (credit, refund)
CASH_OUTMoney out (purchase, cash advance)

status

Processing state.

ValueDescription
PENDINGPending
PROCESSEDSettled or processed
CANCELEDCanceled

type

Detailed transaction classification.

ValueDescription
PURCHASEDomestic purchase
PURCHASE_INTERNATIONALInternational purchase
PURCHASE_BNPLInstallment / BNPL purchase
WITHDRAWDomestic cash advance
WITHDRAW_INTERNATIONALInternational cash advance
WITHDRAW_FUNDSFunds withdrawal
BALANCE_INQUIRYBalance inquiry
PAYMENT_PLAN_INQUIRYInstallment plan inquiry
REFUNDDomestic refund
REFUND_INTERNATIONALInternational refund
REFUND_CREDIT_ADJUSTMENTCredit adjustment (refund)
REVERSAL_CREDIT_ADJUSTMENTReversal of credit adjustment
REFUND_IOFIOF refund
REFUND_PURCHASE_BNPLBNPL refund
IOFIOF tax
LIMITLimit change (debit)
LIMIT_CREDITLimit change (credit)
SUMMARYSummary or consolidation
BILL_TARIFFStatement fee
REFUND_BILL_TARIFFStatement fee refund
INVOICE_PAYMENTInvoice payment

card.type

ValueDescription
VIRTUALVirtual card (online)
PHYSICALPhysical (plastic) card

Request objects

CardsTransactionRequest

Parameters to query the card statement.

FieldTypeRequiredDescription
startDatestringYesStart of range (YYYY-MM-DD)
endDatestringYesEnd of range (YYYY-MM-DD)
limitintegerYesPage size (5–100)
nextPageStartKeystringNoPagination cursor

The queried range (endDate minus startDate) cannot exceed 62 days.

Example

{
  "startDate": "2025-01-01",
  "endDate": "2025-01-31",
  "limit": 50
}

Response objects

CardsTransactionResponse

Response for the card statement: list of transactions and optional next page.

FieldTypeDescription
transactionsarray[CardTransaction]Transactions
nextPageStartKeystringNext page token if more data exists

Example

{
  "transactions": [
    {
      "id": "txn_001",
      "operation": "CASH_OUT",
      "transactionDate": "2025-01-15T14:30:00.000Z",
      "status": "PROCESSED",
      "type": "PURCHASE",
      "merchant": "RESTAURANT XYZ",
      "amountBrl": 89.90
    }
  ],
  "nextPageStartKey": "eyJsYXN0SWQiOiJ0eG5fMDAxIn0="
}

Global rules

Dates and ranges

  • Input format: YYYY-MM-DD (e.g. 2025-01-15)
  • Output format: full ISO 8601 in UTC (e.g. 2025-01-15T14:30:00.000Z)
  • Maximum range: 62 days per request
  • Timezone: UTC

Pagination

  • Minimum page size: 5
  • Maximum page size: 100
  • Cursor: nextPageStartKey is opaque — do not parse or change it
  • Attachments can include HATEOAS _links for the download URL
  • Use GET /attachments/v1/content/{attachmentId} to download the file
  • Supported: image/png, image/jpeg, application/pdf

Next steps