Skip to main content
GET
/
api
/
v1
/
transactions
/
{txn_id}
Retrieve Transaction
curl --request GET \
  --url https://sandbox-b2b.ripio.com/api/v1/transactions/{txn_id}/ \
  --header 'Authorization: Bearer <token>'
{
  "id": "497f6eca-6276-4993-bfeb-53cbbbba6f08",
  "created_at": "2019-08-24T14:15:22Z",
  "end_user": "string",
  "op_type": "BUY",
  "operation": {
    "id": "636ed595-714b-4785-8d36-3dcac7d2567d",
    "external_ref": "71736720-4d62-473b-9916-015e59986e69",
    "quote_id": "02642013-9310-47c4-8e85-67cba34d60a5",
    "txn_id": "39402e8a-0f0e-49dc-928f-c72cf973383e",
    "end_user_id": "73aa41e6-8a97-45f8-8d20-b2bd0cc91193",
    "rate": "140.00000000",
    "market_rate": "140.00000000",
    "charged_fee": "0E-8",
    "fee_charged_in_fiat": true,
    "deferred_charged_fee": true,
    "crypto_charged_fee": "0E-20",
    "base_amount": "11.13622013",
    "quote_amount": "1559.07081820",
    "base_asset": "RTEST",
    "quote_asset": "ARS",
    "created_at": "2025-01-22T20:20:26.218009Z"
  }
}

Authorizations

​
Authorization
string
header
required

B2B’s White Label API uses OAuth2. Currently there is only one supported authentication flow:

  • clientCredentials allows you to access your own B2B account (First-Party Integration) and performs transactions against the public API. This oauth2 flow is well suited for this API, as it allows machine-to-machine communication.

Every call to the API has to be authenticated with an OAuth2 Token. In order to request this token, you will need to have sandbox or production API Keys (client id and client secret) that will be needed to generate a credential in order to negotiate an ephemeral access token.

Every request must be accompianed by an Authorization header with a value that follows the following schema: Bearer ACCESS_TOKEN

Path Parameters

​
txn_id
string
required

Response

200 - application/json

Successful response

​
id
string<uuid>
required

UUID used as txn identifier.

​
created_at
string<date-time>
required

ISO DateTime indicating creation date of txn.

​
end_user
string
required

Indicates which end user was involved in the transaction.

​
op_type
enum<string>
required

Indicates whether the transaction is for BUY, SELL, SWAP, DEPOSIT, WITHDRAWAL, PEER_TO_PEER, COIN_EARN, COIN_BURN, FIAT_DEPOSIT, FIAT_WITHDRAWAL.

Available options:
BUY,
SELL,
SWAP,
DEPOSIT,
WITHDRAWAL,
PEER_TO_PEER,
COIN_EARN,
COIN_BURN,
FIAT_DEPOSIT,
FIAT_WITHDRAWAL
​
operation
object

If the transaction represents a BUY or SELL operation, this object will detail the information of the trade.

​
status
string

Indicates the status of the transaction.

Example:

"COMPLETED"