Skip Navigation
Log In Sign Up

List All Payments

·

Retrieve a paginated list of all payments with optional filtering.

Request

GET https://tupel.com/api/payments/

Authentication

This endpoint requires basic authentication with your Organization ID and API Key.

Query Parameters

  • created_from timestamp Optional
    Filter payments created on or after this timestamp. Format: ISO 8601 (e.g., 2023-01-01T00:00:00Z).

  • created_to timestamp Optional
    Filter payments created on or before this timestamp. Format: ISO 8601 (e.g., 2023-12-31T23:59:59Z).

  • updated_from timestamp Optional
    Filter payments updated on or after this timestamp. Format: ISO 8601 (e.g., 2023-01-01T00:00:00Z).

  • updated_to timestamp Optional
    Filter payments updated on or before this timestamp. Format: ISO 8601 (e.g., 2023-12-31T23:59:59Z).

  • entity string Optional
    Filter payments by entity UID. Only returns payments associated with the specified entity.

  • status string Optional
    Filter payments by status. Possible values: PENDING, SETTLED, FAILED.

  • currency string Optional
    Filter payments by currency. Possible values: USD, EUR, GBP, or other accepted currency codes.

  • order_by string Optional
    Field to sort the results by. Prefix with - for descending order (e.g., -created_at).

  • page integer Optional
    Page number for pagination. Default: 1.

Notes

  • By default, all payments are returned, sorted by creation date (newest first).
  • Use the filtering parameters to narrow down results for better performance with large datasets.
  • For date range filters, both the start and end parameters are inclusive.
  • This endpoint uses page-based pagination with 10 items per page.
  • For more information about working with paginated results, see the pagination documentation.
  • Common use cases include:
  • Retrieving all payments for reconciliation
  • Monitoring the status of recent transactions
  • Generating reports filtered by date ranges
  • Tracking payments for a specific entity

Example Request

curl -X GET "https://tupel.com/api/payments/" \
  -u <YOUR_ORG_ID>:<YOUR_API_KEY>

Response

A successful request returns a 200 OK status code and a paginated list of Payments in the response body.

Response Format

The response follows Tupel's standard pagination format with these fields:

  • count integer
    Total number of payments matching the filter criteria.

  • next string or null
    URL to fetch the next page of results, or null if this is the last page.

  • previous string or null
    URL to fetch the previous page of results, or null if this is the first page.

  • items array
    Array of Payment objects, limited to 10 per page.

Error Responses

Code Description
401 Unauthorized - Authentication failed. Check your Organization ID and API Key.
403 Forbidden - Insufficient permissions to list payments.
422 Unprocessable Entity - Invalid filter parameters provided.

Example Error Response

{
  "detail": [
    {
      "type": "value_error",
      "loc": ["query", "status"],
      "msg": "Invalid status value. Must be one of: PENDING, SETTLED, FAILED."
    }
  ]
}