Skip to main content
PUT
/
v0
/
transactions
/
{external_id}
/
receipt
Upload Receipt
curl --request PUT \
  --url https://api.sumvin.com/v0/transactions/{external_id}/receipt \
  --header 'Content-Type: multipart/form-data' \
  --header 'x-juno-jwt: <api-key>' \
  --form 'file=<string>'
{
  "_links": {},
  "content_type": "<string>",
  "size": 123,
  "uploaded_at": 123
}

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

external_id
string
required

Body

multipart/form-data
file
string
required

Response

Receipt uploaded successfully

HAL-style hypermedia links for navigation and available actions.

content_type
string
required

MIME type of the uploaded receipt

size
integer
required

Size of the uploaded receipt in bytes

uploaded_at
integer
required

Upload timestamp (epoch ms)