# List loan transactions

Lists the transactions (installments) of a loan. Each transaction represents an
installment with due date (due_date), original amount, paid amount, and payment
status (pending, paid, overdue). This is a read-only endpoint —
payments are processed outside the API. Track payments in real time via
webhook loan.payment_received.

Endpoint: GET /loans/{loan_id}/transactions
Version: 2026-03-01
Security: bearerAuth

## Path parameters:

  - `loan_id` (string, required)
    Example: "ln_550e8400e29b41d4a716446655440000"

## Query parameters:

  - `starting_after` (string)
    Prefixed ID of the last item from the previous page.

  - `limit` (integer)
    Number of items to return. Min: 1, Max: 100.

## Response 200 fields (application/json):

  - `data` (array, required)

  - `data.id` (string, required)

  - `data.loan_id` (string, required)

  - `data.type` (string, required)
    Enum: "installment"

  - `data.due_date` (string, required)
    Example: "2026-04-03"

  - `data.status` (string, required)
    Enum: "pending", "paid", "overdue", "partially_paid"

  - `data.amount_due` (string, required)
    Decimal encoded as a string with exactly 2 decimal places (BRL).

  - `data.amount_paid` (string, required)
    Decimal encoded as a string with exactly 2 decimal places (BRL).

  - `data.amount_remaining` (string, required)
    Decimal encoded as a string with exactly 2 decimal places (BRL).

  - `data.principal` (string, required)
    Decimal encoded as a string with exactly 2 decimal places (BRL).

  - `data.interest` (string, required)
    Decimal encoded as a string with exactly 2 decimal places (BRL).

  - `data.fees` (string, required)
    Decimal encoded as a string with exactly 2 decimal places (BRL).

  - `data.days_overdue` (integer, required)

  - `data.paid_at` (string,null, required)

  - `data.created_at` (string, required)

  - `data.updated_at` (string, required)

  - `has_more` (boolean, required)

## Response 400 fields (application/problem+json):

  - `type` (string, required)
    URI identifying the error type

  - `title` (string, required)
    Short, human-readable summary of the problem type

  - `status` (integer, required)
    HTTP status code

  - `detail` (string, required)
    Human-readable explanation specific to this occurrence

  - `instance` (string)
    URI identifying this specific occurrence

  - `code` (string)
    Machine-readable subtype code

  - `param` (string)
    The request parameter that caused the error

  - `errors` (array)
    Field-level validation errors

  - `errors.param` (string, required)

  - `errors.detail` (string, required)

  - `errors.code` (string)

## Response 401 fields (application/problem+json):

  - `type` (string, required)
    URI identifying the error type

  - `title` (string, required)
    Short, human-readable summary of the problem type

  - `status` (integer, required)
    HTTP status code

  - `detail` (string, required)
    Human-readable explanation specific to this occurrence

  - `instance` (string)
    URI identifying this specific occurrence

  - `code` (string)
    Machine-readable subtype code

  - `param` (string)
    The request parameter that caused the error

  - `errors` (array)
    Field-level validation errors

  - `errors.param` (string, required)

  - `errors.detail` (string, required)

  - `errors.code` (string)

## Response 404 fields (application/problem+json):

  - `type` (string, required)
    URI identifying the error type

  - `title` (string, required)
    Short, human-readable summary of the problem type

  - `status` (integer, required)
    HTTP status code

  - `detail` (string, required)
    Human-readable explanation specific to this occurrence

  - `instance` (string)
    URI identifying this specific occurrence

  - `code` (string)
    Machine-readable subtype code

  - `param` (string)
    The request parameter that caused the error

  - `errors` (array)
    Field-level validation errors

  - `errors.param` (string, required)

  - `errors.detail` (string, required)

  - `errors.code` (string)

## Response 429 fields (application/problem+json):

  - `type` (string, required)
    URI identifying the error type

  - `title` (string, required)
    Short, human-readable summary of the problem type

  - `status` (integer, required)
    HTTP status code

  - `detail` (string, required)
    Human-readable explanation specific to this occurrence

  - `instance` (string)
    URI identifying this specific occurrence

  - `code` (string)
    Machine-readable subtype code

  - `param` (string)
    The request parameter that caused the error

  - `errors` (array)
    Field-level validation errors

  - `errors.param` (string, required)

  - `errors.detail` (string, required)

  - `errors.code` (string)

## Response 500 fields (application/problem+json):

  - `type` (string, required)
    URI identifying the error type

  - `title` (string, required)
    Short, human-readable summary of the problem type

  - `status` (integer, required)
    HTTP status code

  - `detail` (string, required)
    Human-readable explanation specific to this occurrence

  - `instance` (string)
    URI identifying this specific occurrence

  - `code` (string)
    Machine-readable subtype code

  - `param` (string)
    The request parameter that caused the error

  - `errors` (array)
    Field-level validation errors

  - `errors.param` (string, required)

  - `errors.detail` (string, required)

  - `errors.code` (string)