Skip to content

katana_public_api_client.api.serial_number.create_serial_numbers

katana_public_api_client.api.serial_number.create_serial_numbers

Classes

Functions

asyncio(*, client, body) async

Attach serial numbers

Attaches pre-existing serial-number strings to a resource. This endpoint did not mint a new string for any tested resource type or manufacturing- order state. Serial identities are created by inventory-producing workflows such as production and goods receipt.

Error cases (verified live 2026-07-14, #980): a non-existent resource_id returns 404 NotFoundError with a type-specific message (e.g. manufacturing order <id> not found / production <id> not found). A resource_type outside the CreateSerialNumberResourceType enum returns 422 with an Ajv-style validation detail. Unknown, duplicate, and mixed valid/invalid strings hard-fail the whole request with 422; the legacy failed array was never observed. A completed manufacturing order can instead reject because it has no remaining quantity and direct callers to update completed production traceability.

Manual attachment to valid standalone and make-to-order manufacturing orders returned 404 in September 2026, before and after production. Production and fulfillment can use their unified traceability contracts without a successful call to this endpoint.

Transfer response quirks: on a successful transfer the moved record's transaction_id may be the literal string undefined and resource_id may be null — re-fetch via GET /serial_numbers to confirm the landing state.

Parameters:

  • body (CreateSerialNumbersRequest) –

    Attach existing serial-number strings to a resource. Only resource_id is required by the gateway. Omitting resource_type is accepted as a no-op (204 No Content); supply resource_type and serial_numbers to attempt an attachment (#830,

    983). Unknown strings abort with 422; this endpoint did not mint new strings in current

    live probes.

Raises:

  • UnexpectedStatus –

    If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.

  • TimeoutException –

    If the request takes longer than Client.timeout.

Returns:

Source code in katana_public_api_client/api/serial_number/create_serial_numbers.py 
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
async def asyncio(
    *,
    client: AuthenticatedClient | Client,
    body: CreateSerialNumbersRequest,
) -> Any | CreateSerialNumbersResponse | DetailedErrorResponse | ErrorResponse | None:
    """Attach serial numbers

     Attaches pre-existing serial-number strings to a resource. This endpoint
    did not mint a new string for any tested resource type or manufacturing-
    order state. Serial identities are created by inventory-producing
    workflows such as production and goods receipt.

    **Error cases** (verified live 2026-07-14, #980): a non-existent
    ``resource_id`` returns ``404 NotFoundError`` with a type-specific
    message (e.g. ``manufacturing order <id> not found`` /
    ``production <id> not found``). A ``resource_type`` outside the
    ``CreateSerialNumberResourceType`` enum returns ``422`` with an
    Ajv-style validation detail. Unknown, duplicate, and mixed
    valid/invalid strings hard-fail the whole request with ``422``; the
    legacy ``failed`` array was never observed. A completed manufacturing
    order can instead reject because it has no remaining quantity and
    direct callers to update completed production traceability.

    Manual attachment to valid standalone and make-to-order manufacturing
    orders returned ``404`` in September 2026, before and after production.
    Production and fulfillment can use their unified ``traceability``
    contracts without a successful call to this endpoint.

    **Transfer response quirks:** on a successful transfer the moved
    record's ``transaction_id`` may be the literal string
    ``undefined`` and ``resource_id`` may be ``null`` — re-fetch via
    ``GET /serial_numbers`` to confirm the landing state.

    Args:
        body (CreateSerialNumbersRequest): Attach existing serial-number strings to a resource.
            Only resource_id is required by the gateway. Omitting resource_type is accepted as a no-op
            (204 No Content); supply resource_type and serial_numbers to attempt an attachment (#830,
            #983). Unknown strings abort with 422; this endpoint did not mint new strings in current
            live probes.

    Raises:
        errors.UnexpectedStatus: If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.
        httpx.TimeoutException: If the request takes longer than Client.timeout.


    Returns:
        Any | CreateSerialNumbersResponse | DetailedErrorResponse | ErrorResponse
    """

    return (
        await asyncio_detailed(
            client=client,
            body=body,
        )
    ).parsed

asyncio_detailed(*, client, body) async

Attach serial numbers

Attaches pre-existing serial-number strings to a resource. This endpoint did not mint a new string for any tested resource type or manufacturing- order state. Serial identities are created by inventory-producing workflows such as production and goods receipt.

Error cases (verified live 2026-07-14, #980): a non-existent resource_id returns 404 NotFoundError with a type-specific message (e.g. manufacturing order <id> not found / production <id> not found). A resource_type outside the CreateSerialNumberResourceType enum returns 422 with an Ajv-style validation detail. Unknown, duplicate, and mixed valid/invalid strings hard-fail the whole request with 422; the legacy failed array was never observed. A completed manufacturing order can instead reject because it has no remaining quantity and direct callers to update completed production traceability.

Manual attachment to valid standalone and make-to-order manufacturing orders returned 404 in September 2026, before and after production. Production and fulfillment can use their unified traceability contracts without a successful call to this endpoint.

Transfer response quirks: on a successful transfer the moved record's transaction_id may be the literal string undefined and resource_id may be null — re-fetch via GET /serial_numbers to confirm the landing state.

Parameters:

  • body (CreateSerialNumbersRequest) –

    Attach existing serial-number strings to a resource. Only resource_id is required by the gateway. Omitting resource_type is accepted as a no-op (204 No Content); supply resource_type and serial_numbers to attempt an attachment (#830,

    983). Unknown strings abort with 422; this endpoint did not mint new strings in current

    live probes.

Raises:

  • UnexpectedStatus –

    If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.

  • TimeoutException –

    If the request takes longer than Client.timeout.

Returns:

Source code in katana_public_api_client/api/serial_number/create_serial_numbers.py 
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
async def asyncio_detailed(
    *,
    client: AuthenticatedClient | Client,
    body: CreateSerialNumbersRequest,
) -> Response[
    Any | CreateSerialNumbersResponse | DetailedErrorResponse | ErrorResponse
]:
    """Attach serial numbers

     Attaches pre-existing serial-number strings to a resource. This endpoint
    did not mint a new string for any tested resource type or manufacturing-
    order state. Serial identities are created by inventory-producing
    workflows such as production and goods receipt.

    **Error cases** (verified live 2026-07-14, #980): a non-existent
    ``resource_id`` returns ``404 NotFoundError`` with a type-specific
    message (e.g. ``manufacturing order <id> not found`` /
    ``production <id> not found``). A ``resource_type`` outside the
    ``CreateSerialNumberResourceType`` enum returns ``422`` with an
    Ajv-style validation detail. Unknown, duplicate, and mixed
    valid/invalid strings hard-fail the whole request with ``422``; the
    legacy ``failed`` array was never observed. A completed manufacturing
    order can instead reject because it has no remaining quantity and
    direct callers to update completed production traceability.

    Manual attachment to valid standalone and make-to-order manufacturing
    orders returned ``404`` in September 2026, before and after production.
    Production and fulfillment can use their unified ``traceability``
    contracts without a successful call to this endpoint.

    **Transfer response quirks:** on a successful transfer the moved
    record's ``transaction_id`` may be the literal string
    ``undefined`` and ``resource_id`` may be ``null`` — re-fetch via
    ``GET /serial_numbers`` to confirm the landing state.

    Args:
        body (CreateSerialNumbersRequest): Attach existing serial-number strings to a resource.
            Only resource_id is required by the gateway. Omitting resource_type is accepted as a no-op
            (204 No Content); supply resource_type and serial_numbers to attempt an attachment (#830,
            #983). Unknown strings abort with 422; this endpoint did not mint new strings in current
            live probes.

    Raises:
        errors.UnexpectedStatus: If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.
        httpx.TimeoutException: If the request takes longer than Client.timeout.


    Returns:
        Response[Any | CreateSerialNumbersResponse | DetailedErrorResponse | ErrorResponse]
    """

    kwargs = _get_kwargs(
        body=body,
    )

    response = await client.get_async_httpx_client().request(**kwargs)

    return _build_response(client=client, response=response)

sync(*, client, body)

Attach serial numbers

Attaches pre-existing serial-number strings to a resource. This endpoint did not mint a new string for any tested resource type or manufacturing- order state. Serial identities are created by inventory-producing workflows such as production and goods receipt.

Error cases (verified live 2026-07-14, #980): a non-existent resource_id returns 404 NotFoundError with a type-specific message (e.g. manufacturing order <id> not found / production <id> not found). A resource_type outside the CreateSerialNumberResourceType enum returns 422 with an Ajv-style validation detail. Unknown, duplicate, and mixed valid/invalid strings hard-fail the whole request with 422; the legacy failed array was never observed. A completed manufacturing order can instead reject because it has no remaining quantity and direct callers to update completed production traceability.

Manual attachment to valid standalone and make-to-order manufacturing orders returned 404 in September 2026, before and after production. Production and fulfillment can use their unified traceability contracts without a successful call to this endpoint.

Transfer response quirks: on a successful transfer the moved record's transaction_id may be the literal string undefined and resource_id may be null — re-fetch via GET /serial_numbers to confirm the landing state.

Parameters:

  • body (CreateSerialNumbersRequest) –

    Attach existing serial-number strings to a resource. Only resource_id is required by the gateway. Omitting resource_type is accepted as a no-op (204 No Content); supply resource_type and serial_numbers to attempt an attachment (#830,

    983). Unknown strings abort with 422; this endpoint did not mint new strings in current

    live probes.

Raises:

  • UnexpectedStatus –

    If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.

  • TimeoutException –

    If the request takes longer than Client.timeout.

Returns:

Source code in katana_public_api_client/api/serial_number/create_serial_numbers.py 
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
def sync(
    *,
    client: AuthenticatedClient | Client,
    body: CreateSerialNumbersRequest,
) -> Any | CreateSerialNumbersResponse | DetailedErrorResponse | ErrorResponse | None:
    """Attach serial numbers

     Attaches pre-existing serial-number strings to a resource. This endpoint
    did not mint a new string for any tested resource type or manufacturing-
    order state. Serial identities are created by inventory-producing
    workflows such as production and goods receipt.

    **Error cases** (verified live 2026-07-14, #980): a non-existent
    ``resource_id`` returns ``404 NotFoundError`` with a type-specific
    message (e.g. ``manufacturing order <id> not found`` /
    ``production <id> not found``). A ``resource_type`` outside the
    ``CreateSerialNumberResourceType`` enum returns ``422`` with an
    Ajv-style validation detail. Unknown, duplicate, and mixed
    valid/invalid strings hard-fail the whole request with ``422``; the
    legacy ``failed`` array was never observed. A completed manufacturing
    order can instead reject because it has no remaining quantity and
    direct callers to update completed production traceability.

    Manual attachment to valid standalone and make-to-order manufacturing
    orders returned ``404`` in September 2026, before and after production.
    Production and fulfillment can use their unified ``traceability``
    contracts without a successful call to this endpoint.

    **Transfer response quirks:** on a successful transfer the moved
    record's ``transaction_id`` may be the literal string
    ``undefined`` and ``resource_id`` may be ``null`` — re-fetch via
    ``GET /serial_numbers`` to confirm the landing state.

    Args:
        body (CreateSerialNumbersRequest): Attach existing serial-number strings to a resource.
            Only resource_id is required by the gateway. Omitting resource_type is accepted as a no-op
            (204 No Content); supply resource_type and serial_numbers to attempt an attachment (#830,
            #983). Unknown strings abort with 422; this endpoint did not mint new strings in current
            live probes.

    Raises:
        errors.UnexpectedStatus: If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.
        httpx.TimeoutException: If the request takes longer than Client.timeout.


    Returns:
        Any | CreateSerialNumbersResponse | DetailedErrorResponse | ErrorResponse
    """

    return sync_detailed(
        client=client,
        body=body,
    ).parsed

sync_detailed(*, client, body)

Attach serial numbers

Attaches pre-existing serial-number strings to a resource. This endpoint did not mint a new string for any tested resource type or manufacturing- order state. Serial identities are created by inventory-producing workflows such as production and goods receipt.

Error cases (verified live 2026-07-14, #980): a non-existent resource_id returns 404 NotFoundError with a type-specific message (e.g. manufacturing order <id> not found / production <id> not found). A resource_type outside the CreateSerialNumberResourceType enum returns 422 with an Ajv-style validation detail. Unknown, duplicate, and mixed valid/invalid strings hard-fail the whole request with 422; the legacy failed array was never observed. A completed manufacturing order can instead reject because it has no remaining quantity and direct callers to update completed production traceability.

Manual attachment to valid standalone and make-to-order manufacturing orders returned 404 in September 2026, before and after production. Production and fulfillment can use their unified traceability contracts without a successful call to this endpoint.

Transfer response quirks: on a successful transfer the moved record's transaction_id may be the literal string undefined and resource_id may be null — re-fetch via GET /serial_numbers to confirm the landing state.

Parameters:

  • body (CreateSerialNumbersRequest) –

    Attach existing serial-number strings to a resource. Only resource_id is required by the gateway. Omitting resource_type is accepted as a no-op (204 No Content); supply resource_type and serial_numbers to attempt an attachment (#830,

    983). Unknown strings abort with 422; this endpoint did not mint new strings in current

    live probes.

Raises:

  • UnexpectedStatus –

    If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.

  • TimeoutException –

    If the request takes longer than Client.timeout.

Returns:

Source code in katana_public_api_client/api/serial_number/create_serial_numbers.py 
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
def sync_detailed(
    *,
    client: AuthenticatedClient | Client,
    body: CreateSerialNumbersRequest,
) -> Response[
    Any | CreateSerialNumbersResponse | DetailedErrorResponse | ErrorResponse
]:
    """Attach serial numbers

     Attaches pre-existing serial-number strings to a resource. This endpoint
    did not mint a new string for any tested resource type or manufacturing-
    order state. Serial identities are created by inventory-producing
    workflows such as production and goods receipt.

    **Error cases** (verified live 2026-07-14, #980): a non-existent
    ``resource_id`` returns ``404 NotFoundError`` with a type-specific
    message (e.g. ``manufacturing order <id> not found`` /
    ``production <id> not found``). A ``resource_type`` outside the
    ``CreateSerialNumberResourceType`` enum returns ``422`` with an
    Ajv-style validation detail. Unknown, duplicate, and mixed
    valid/invalid strings hard-fail the whole request with ``422``; the
    legacy ``failed`` array was never observed. A completed manufacturing
    order can instead reject because it has no remaining quantity and
    direct callers to update completed production traceability.

    Manual attachment to valid standalone and make-to-order manufacturing
    orders returned ``404`` in September 2026, before and after production.
    Production and fulfillment can use their unified ``traceability``
    contracts without a successful call to this endpoint.

    **Transfer response quirks:** on a successful transfer the moved
    record's ``transaction_id`` may be the literal string
    ``undefined`` and ``resource_id`` may be ``null`` — re-fetch via
    ``GET /serial_numbers`` to confirm the landing state.

    Args:
        body (CreateSerialNumbersRequest): Attach existing serial-number strings to a resource.
            Only resource_id is required by the gateway. Omitting resource_type is accepted as a no-op
            (204 No Content); supply resource_type and serial_numbers to attempt an attachment (#830,
            #983). Unknown strings abort with 422; this endpoint did not mint new strings in current
            live probes.

    Raises:
        errors.UnexpectedStatus: If the server returns an undocumented status code and Client.raise_on_unexpected_status is True.
        httpx.TimeoutException: If the request takes longer than Client.timeout.


    Returns:
        Response[Any | CreateSerialNumbersResponse | DetailedErrorResponse | ErrorResponse]
    """

    kwargs = _get_kwargs(
        body=body,
    )

    response = client.get_httpx_client().request(
        **kwargs,
    )

    return _build_response(client=client, response=response)