List transactions

GEThttps://api.omise.co/transactions

Returns a paginated list of transactions belonging to your account. Transactions represent the movement of funds between your account and payment sources or transfer destinations.

---

🔑API Credentials

▼

---

Request Parameters

Recommended - 5 fieldsRecommended Parameters

▼

`from`STRING(optional)

Earliest UTC datetime for returned records in ISO 8601 format. Use this to filter transactions created on or after this date.

Example:"2025-01-01T00:00:00Z"

Default:"1970-01-01T00:00:00Z"

`to`STRING(optional)

Latest UTC datetime for returned records in ISO 8601 format. Use this to filter transactions created before this date.

Example:"2025-12-31T23:59:59Z"

`limit`INTEGER(optional)

Number of records to return per page. Useful for controlling response size and performance.

Example:20

Constraints:Minimum: 1, Maximum: 100

Default:20

`offset`INTEGER(optional)

Number of records to skip before returning results. Use with limit for pagination.

Example:0

Default:0

`order`STRING(optional)

Sort order for the results based on creation time.

Example:"chronological"

Values:chronological, reverse_chronological

Default:"chronological"

---

Responses

200

Successful request

Returns a list object containing transaction data in the data array.

Response structure:

• object - String value "list"
• data - Array of transaction objects
• limit - Number of records per page
• offset - Current offset
• total - Total number of transactions
• location - API endpoint path

Each transaction object contains:

• id - Transaction identifier (e.g., trxn_test_5fzo4nqrnop03djdde1)
• amount - Transaction amount in smallest currency unit
• currency - Three-letter ISO 4217 currency code
• direction - Direction of funds (credit or debit)
• key - Related object that triggered the transaction
• origin - Original source of the transaction
• transferable_at - Date when funds become transferable
• created_at - Transaction creation timestamp

401

Unauthorized

Authentication failed. Invalid or missing API key.

Common causes:

• Missing Authorization header
• Invalid secret key
• Using public key instead of secret key
• Incorrect HTTP Basic Auth format

---

Code samples

cURL

curl https://api.omise.co/transactions \
  -u skey_test_5xuy4w91xqz7d1w9u0t:

Ruby

require 'omise'

Omise.api_key = 'skey_test_5xuy4w91xqz7d1w9u0t'

transactions = Omise::Transaction.list

Python

import omise

omise.api_secret = 'skey_test_5xuy4w91xqz7d1w9u0t'

transactions = omise.Transaction.retrieve()

Node.js

const omise = require('omise')({
  secretKey: 'skey_test_5xuy4w91xqz7d1w9u0t'
});

const transactions = await omise.transactions.list();

PHP

<?php
define('OMISE_SECRET_KEY', 'skey_test_5xuy4w91xqz7d1w9u0t');

$transactions = OmiseTransaction::retrieve();

Java

Client client = new Client.Builder()
    .secretKey("skey_test_5xuy4w91xqz7d1w9u0t")
    .build();

ScopedList<Transaction> transactions = client.transactions().list();

C#

var client = new Client("skey_test_5xuy4w91xqz7d1w9u0t");

var transactions = await client.Transactions.List();

Go

client, _ := omise.NewClient(
    "pkey_test_5xuy4w91xqz7d1w9u0t",
    "skey_test_5xuy4w91xqz7d1w9u0t",
)

transactions, _ := client.Transactions().List(&operations.ListTransactions{
    Limit: 20,
})

---

Try it out

Recommended - 5 fields

▼