01.software Docs

updateFulfillment

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

All HTTP operations
POST
/api/orders/update-fulfillment

Tenant-editor write; quantity/lifecycle admission and same-tenant document; carrier/tracking and status refinements remain mandatory.

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
fulfillmentId*string|number
status?string
Value in"shipped""delivered""failed"
carrier?string
Length1 <= length
trackingNumber?string
Length1 <= length

Response Body

Actual shaped success body

application/json
  1. response

Actual authenticated Payload Fulfillment 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|
status?string
carrier?string|null
trackingNumber?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/orders/update-fulfillment' \  -H 'Content-Type: application/json' \  -d '{  "fulfillmentId": "string"}'
Example Response
{  "id": "string",  "createdAt": "string",  "updatedAt": "string",  "order": "string",  "status": "string",  "carrier": "string",  "trackingNumber": "string"}