reserved-customers
Operations addressed under /reserved-customers — 3 operations.
aurax-bff-dynamic-get-customer-reserved-list
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Request and response fields are declared on the routing target get-customer-reserved-list; this entry declares none of its own.
query Parameters
orderByorderSortaurax-bff-dynamic-get-customer-reserved-list › Responses
Success. Returns a page of records: the collection under data, with total carrying the unpaged count.
Response records carried by this page.
totalTotal matching records, ignoring paging.
Create Customer Number Reserved
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Invokes the aurax-bff-dynamic-create-customer-reserved-bpm service definition through POST /reserved-customers.
Request and response fields are declared on the routing target create-customer-reserved-bpm; this entry declares none of its own.
Create Customer Number Reserved › Responses
Success. The schema is an anyOf over three envelopes: the record, a bare array of it, and a page {total, data[]} carrying the same record.
Decision Table
| Variant | Matching Criteria |
|---|---|
| type = object | |
| type = array | |
| type = object · requires: data |
Delete Customer Number Reserved
Add Authorization: Bearer <token> yourself — generated samples and Try it do not attach a credential.
Invokes the aurax-bff-dynamic-delete-customer-reserved-bpm service definition through DELETE /reserved-customers/{id}.
Request and response fields are declared on the routing target delete-customer-reserved-bpm; this entry declares none of its own.
Request body description
The catalog declares Body-bound fields on this DELETE operation. Request bodies on DELETE have no defined semantics in HTTP; this documents the catalog, not a recommendation. Not every field below is accepted: the platform selects which of them this operation admits and drops the rest. Of the fields below, the binder does not admit id, which this document nevertheless marks required because the catalog declares it so.
path Parameters
idPresent in this route template but not among the Route-bound fields of the routing target delete-customer-reserved-bpm, whose own path is decoupled from this one.
Delete Customer Number Reserved › Responses
Success. The catalog declares no response fields for this operation. The body is UNKNOWN CONTENT.