Custom Order Creation History

The public API reference does not list POST /orders/custom. Its availability is unconfirmed; do not rely on this route without confirmation from your API provider.

The public API reference does not list this operation. If it becomes available, it is expected to accept either products or total, not both, and to require customer JSON, one source of business identity, and one payment-method representation. Product entries use name, price, quantity, and optional detail; supplied customer and business snapshots are stored as order history rather than newly registered canonical resources.

The described total behavior creates a translated synthetic total item when product detail is unavailable. X-APP-X records the originating channel. Field formats differ between the legacy and optional version=v2 branches; public availability is unconfirmed.

Examples must not contain API keys, customer data, or credentials. The public API reference does not document this operation.