v1

latestOpenAPI 3.0.32026-07-2618073.2 KB
Purchases

Get purchase history

Returns paginated list of user's purchases with optional status filtering.

Chronological Ordering. Purchases are always returned newest first (descending by created_at).

Pagination behavior

  • Results are consistent during session (no duplicates or missing items when paginating).
  • has_next: true indicates more pages available.
  • Maximum page_size is 50 items.

Filtering. Combine status filter with pagination for subset queries (e.g., all successful purchases).

get/v1/purchases/

Query parameters

status'PENDING' | 'SUCCESS' | 'ERROR' | 'REFUND'

Purchase Status Lifecycle. PENDING (initial) → SUCCESS (after code request) or ERROR (provider failure). Any status can transition to REFUND via admin action.

Important. Status is immutable once set to SUCCESS, ERROR, or REFUND.

Filter options

  • PENDING - code not requested.
  • SUCCESS - code ready.
  • ERROR - provider failed.
  • REFUND - money returned.
Example:SUCCESS
pageinteger required

Page number.

Example:1
page_sizeinteger required

Number of items per page.

Example:50

Response

Successful response.

Example response

{
  "items": [
    {
      "id": 12345,
      "country_code": "US",
      "display_name": {
        "ru": "США",
        "en": "United States"
      },
      "phone_number": "+12025550123",
      "price": {
        "amount": "1.50",
        "currency_code": "USD"
      },
      "status": "SUCCESS",
      "purchase_type": "SINGLE",
      "verification": {
        "code": "12345",
        "password": "secret123",
        "received_at": "2024-11-19T07:52:00.000Z"
      },
      "created_at": "2024-11-19T07:50:00.000Z"
    }
  ],
  "pagination": {
    "current_page": 1,
    "page_size": 50,
    "total_items": 150,
    "total_pages": 3,
    "has_next": true
  }
}