Skip to main content
GET
/
v0
/
ramp
/
transactions
/
{transaction_id}
Get a ramp transaction
curl --request GET \
  --url https://api.sumvin.com/v0/ramp/transactions/{transaction_id} \
  --header 'x-juno-jwt: <api-key>'
{
  "_links": {},
  "transaction": {
    "id": "<string>",
    "meld_status": "<string>",
    "transaction_type": "<string>",
    "from_asset": "<string>",
    "to_asset": "<string>",
    "chain_id": 123,
    "source_amount": "<string>",
    "destination_amount": "<string>",
    "service_provider": "<string>",
    "payment_method_type": "<string>",
    "created_at": "<string>",
    "updated_at": "<string>",
    "is_swap": false
  }
}

Authorizations

​
x-juno-jwt
string
header
required

JWT issued by Dynamic Labs or Privy. Sent in the x-juno-jwt header on every authenticated request.

Headers

​
x-juno-orgid
string | null

Tenant org ID for multi-tenant auth

​
x-juno-jwt
string | null
​
x-sumvin-token
string | null
​
x-sumvin-pat
string | null
​
X-Timestamp-Format
string

Controls how timestamp fields are serialized in JSON response bodies.

Default (header omitted or any other value): epoch milliseconds as integers. iso8601: UTC ISO 8601 strings of the form YYYY-MM-DDTHH:MM:SSZ.

Example: with X-Timestamp-Format: iso8601, the field value 1704067200000 becomes "2024-01-01T00:00:00Z".

Affected fields (recursively, in dicts and arrays): any field whose name ends in _at, plus the literal field names timestamp, period_start, and period_end. All other fields are passed through unchanged.

Only iso8601 is recognized. Any other value (or omitting the header) yields the default epoch-ms representation; the server does not reject unknown values, so this is documented as an example rather than an enum to keep generated clients permissive.

Example:

"iso8601"

Path Parameters

​
transaction_id
string
required

Response

Successful Response

​
_links
Links · object
required

HAL-style hypermedia links for navigation and available actions.

​
transaction
TransactionData · object
required

A ramp transaction.

status is the canonical Sumvin transaction status; meld_status is the raw provider status preserved for traceability and one-off mappings the canonical translation does not yet cover.