Skip to main content
GET
/
order
/
{id}
Get order details
curl --request GET \
  --url https://playground.runa.io/v2/order/{id} \
  --header 'X-Api-Key: <api-key>'
{
  "id": "O-01H5WQGHKCBB85MQFM68S9KJ5Q",
  "status": "PROCESSING",
  "created_at": "2023-11-07T05:31:56Z",
  "completed_at": "2023-11-07T05:31:56Z",
  "description": "Your own reference text",
  "payment_method": {
    "type": "ACCOUNT_BALANCE",
    "currency": "USD"
  },
  "currency": "USD",
  "total_price": "10",
  "total_discount": "1",
  "items": [
    {
      "id": "E-NWPEKW4VL",
      "distribution_method": {
        "type": "EMAIL",
        "email_address": "fred@example.com",
        "template_id": "DT-01HPSF51G0ZWHJ3JTNWRH0WDYK"
      },
      "products": {
        "type": "MULTIPLE",
        "values": [
          "AMZ-US",
          "AIRBNB-US"
        ]
      },
      "face_value": "10",
      "price": "10",
      "payout": {
        "status": "ACTIVE",
        "status_updated_at": "2023-11-07T05:31:56Z",
        "url": "<string>",
        "expiry_date": "2023-11-07T05:31:56Z"
      },
      "currency": "USD"
    }
  ],
  "transaction_detail": {
    "USD": {
      "value": "10.00",
      "fx": null
    }
  },
  "metadata": {
    "internal_id": "12345",
    "department": "marketing",
    "campaign": "summer_2024"
  }
}
This endpoint can return both complete and incomplete orders. The types of these responses differ, you should use the status field to determine which type of response you are receiving.
  • Completed orders will have a status of COMPLETED or FAILED and have a full response body.
  • Incomplete orders will have a status of PROCESSING and have a partial response body.

Authorizations

​
X-Api-Key
string
header
required

Your API key. See the API key page on details of how to generate and store your keys.

Headers

​
X-Api-Version
string

The dated version of the API, if not specified a default is used. See API versioning for more information.

Path Parameters

​
id
string
required

The ID of the order.

Response

OK

  • Completed order
  • Incomplete order

Used for an order that has completed. This class is typically used when returning a single order to the client. Used for orders that have completed. This class is typically used when returning a list of orders to the client.

​
id
string
required

The ID of the order.

Example:

"O-01H5WQGHKCBB85MQFM68S9KJ5Q"

​
status
enum<string>
required

Status of the order. The status of the order.

Available options:
COMPLETED,
FAILED,
PROCESSING
Example:

"PROCESSING"

​
created_at
string<date-time>
required

UTC timestamp, in ISO 8601 format, when the order was submitted.

​
payment_method
object
required

The payment method used for the order. Account balance payment.

​
currency
string
required

The currency of the order, represented by ISO 4217 currency codes. Please check the currency section in the guidelines for how to use this field.

Example:

"USD"

​
total_price
string
required

The total price of the order. This includes any applicable fees.

Example:

"10"

​
total_discount
string
required

The total discount of the order.

Example:

"1"

​
items
CompletedOrderItem · object[]
required

The list of items that were included in the order. Each item represents a single payout link.

​
completed_at
string<date-time>

UTC timestamp, in ISO 8601 format, when the order was completed.

​
description
string | null

Free format text reference for the order. The order description will not be visible to the end user. You will see this description in the Runa web portal.

This field is optional and can be omitted if not needed. If not provided, the field will be set to null in the response.

Maximum length: 128
Example:

"Your own reference text"

​
transaction_detail
object

A mapping of the subtotal of the order using the payout currency as a key.

Example:
{ "USD": { "value": "10.00", "fx": null } }
​
metadata
object | null

A flexible field for you to attach additional, customer-specific data to the order. This is for your internal use, the information stored here will not be exposed to the end user.

  • All keys and their corresponding values must be strings
  • Each order supports up to 20 key-value pairs
  • Keys have a maximum length of 40 characters
  • Values can be up to 200 characters long.

This field is optional and can be omitted if not needed. If not provided, the field will be set to null in the response.

Example:
{
  "internal_id": "12345",
  "department": "marketing",
  "campaign": "summer_2024"
}
⌘I