01.software Docs

updateLegacyTransaction

Use the SDK for application integration. This read-only reference covers Commerce, Customer Auth, Membership and Events.

All HTTP operations
POST
/api/transactions/update

Tenant-admin write; provider confirmation returns {transactionId,orderId,status}, checkout transition returns {checkoutId,status}, legacy transaction returns its document. These branches do not grant browser finality authority.

Authorization

bearerAuth
headerAuthorizationBearer <token>

Public integration credentials: verified opaque sk01_ secret key or pat01_ personal access token; operation policy and read/write scopes still apply. These credentials are not Customer JWTs.

Request Body

application/json
  1. body
pgPaymentId*string
Length1 <= length
status*string
Value in"pending""paid""failed""error""canceled""refunded"
paymentMethod?string
receiptUrl?string
paymentKey?string
Length1 <= length
amount?integer
Range0 < value <= 9007199254740991

Response Body

Actual shaped success body

application/json
  1. response

Actual authenticated Payload Transaction document. Relationship depth and field access vary. This is server-only legacy wire, not the canonical public DTO or a browser discovery promise.

id*string
createdAt?string
updatedAt?string
order?string|number|||
amount?number|null
status?string
type?string
pgPaymentId?string|null
pgProvider?string|null
[key: string]?any

Examples may be generated from schemas; they are illustrative, not recorded successful API calls. Example snippets may omit required authentication headers.

Example Request
curl -X POST 'https://api.01.software/api/transactions/update' \  -H 'Content-Type: application/json' \  -d '{  "pgPaymentId": "string",  "status": "pending"}'
Example Response
{  "id": "string",  "createdAt": "string",  "updatedAt": "string",  "order": "string",  "amount": 0,  "status": "string",  "type": "string",  "pgPaymentId": "string",  "pgProvider": "string"}