curl --silent --show-error --fail-with-body --request POST \
--url 'https://api.edi.stateset.com/v1/sscc/allocate' \
--header "Authorization: Bearer $EDI_API_TOKEN" \
--header 'Content-Type: application/json' \
--data '{
"company_prefix": "Acme Outdoors",
"count": 2
}'
Allocates fresh SSCC-18 codes from the tenant's durable, monotonic serial…
Allocated SSCC-18 codes
POST
/
v1
/
sscc
/
allocate
curl --silent --show-error --fail-with-body --request POST \
--url 'https://api.edi.stateset.com/v1/sscc/allocate' \
--header "Authorization: Bearer $EDI_API_TOKEN" \
--header 'Content-Type: application/json' \
--data '{
"company_prefix": "Acme Outdoors",
"count": 2
}'
Request body
SsccAllocateRequest
string,null
GS1 company prefix to allocate under. Defaults to the configured
EDI_GS1_COMPANY_PREFIX; each (tenant, prefix) has its own counter.integer (int32)
required
How many SSCC-18s to allocate (1–1000). Minimum:
0.Response
No response body. Allocated SSCC-18 codes.Status codes
| Code | Meaning |
|---|---|
200 | Allocated SSCC-18 codes |
422 | Invalid count, no GS1 company prefix, or serial space exhausted |
Using this contract
Read the source OpenAPI document for declared schemas and alternatives. This page also includes documented corrections from the spec overlays. Example IDs and values are illustrative; replace them with records from your workspace.curl --silent --show-error --fail-with-body --request POST \
--url 'https://api.edi.stateset.com/v1/sscc/allocate' \
--header "Authorization: Bearer $EDI_API_TOKEN" \
--header 'Content-Type: application/json' \
--data '{
"company_prefix": "Acme Outdoors",
"count": 2
}'
Last modified on October 20, 2026