Skip to main content
POST
Create load reference
Adds a custom reference to a load that already exists. Creating a reference does not take an If-Match header; the server retries bounded concurrency conflicts internally. The response includes a refreshed load ETag you can carry into a later update. Requires load:update. See Updating records safely for how create and update differ on this surface.

Path parameters

Request body

Example

Status codes

Free-form creates (no ReferenceId) are not idempotent. Do not automatically replay a POST unless you have confirmed the first request did not commit. Use Update load reference with the returned instance id to overwrite.

Authorizations

Authorization
string
header
required

OAuth 2.0 client-credentials access token. Obtain one from https://auth.alvys.com/oauth/token (grant_type=client_credentials, audience=https://api.alvys.com/public/), then paste it here. The playground sends it as Authorization: Bearer <token>.

Path Parameters

loadNumber
string
required
version
string
default:2.0
required

API version (e.g., 2.0)

Example:

"2.0"

Body

Name
string
required

Reference name. Must be 50 characters or fewer. For catalog-backed writes, must match the configured definition name.

Maximum string length: 50
Value
string
required

Reference value. Must be 40 characters or fewer — enough for a 36-character CFDI folio UUID. OrderNumber and PONumber stay at the X12 30-character bound and are unchanged by this field.

Maximum string length: 40
ReferenceId
string | null

Optional tenant catalog definition id from List custom reference definitions. When set, the value is validated against that definition.

Response

OK

Name
string
required
Value
string
required
Id
string | null
ReferenceId
string | null
Type
string | null
Access
string | null
Origin
string | null