Skip to main content
POST
Generate codes

Partial success

Every item of a batch is validated on its own, so a rejected item does not fail the request. The status stays 200 OK even when every item was rejected and codes comes back empty, which means you should check failures rather than the status code. Each request item may include a string reference of your choice. The API echoes it unchanged in either codes or failures. If omitted or null, the reference is the item’s zero-based position in the original request, returned as a string: "0", "1", and so on. Empty strings are preserved. Use distinct references and avoid collisions with generated references within a batch. References do not provide deduplication or idempotency.

Validation codes

path matches the part of the definition at fault, so ais.2 is the third entry of ais.

Authorizations

Authorization
string
header
required

The access_token from POST /oauth/token.

Body

codes
object[]
required

The definitions to generate. Items are processed in order and each one is validated on its own.

Response

Generated codes in codes, rejected definitions in failures. Both carry reference, which ties an entry back to the item you sent.

codes
object[]
required
failures
object[]
required