POST /v1/fulfillments

Creates one or multiple Fulfillment objects. You can also generate invoices or memos for these Fulfillment objects in this API call. The following tutorials demonstrate how to use this operation:

Servers

Request headers

Name Type Required Description
Content-Type String Yes The media type of the request body.

Default value: "application/json"

Content-Encoding String No

Include the Content-Encoding: gzip header to compress a request. With this header specified, you should upload a gzipped file for the request payload instead of sending the JSON payload.

Zuora-Track-Id String No

A custom identifier for tracing the API call. If you set a value for this header, Zuora returns the same value in the response headers. This header enables you to associate your system process identifiers with Zuora API calls, to assist with troubleshooting in the event of an issue.

The value of this field must use the US-ASCII character set and must not include any of the following characters: colon (:), semicolon (;), double quote ("), and quote (').

Authorization String No

The value is in the Bearer {token} format where {token} is a valid OAuth token generated by calling Create an OAuth token.

Idempotency-Key String No

Specify a unique idempotency key if you want to perform an idempotent POST or PATCH request. Do not use this header in other request types.

With this header specified, the Zuora server can identify subsequent retries of the same request using this value, which prevents the same operation from being performed multiple times by accident.

Zuora-Entity-Ids String No

An entity ID. If you have Zuora Multi-entity enabled and the OAuth token is valid for more than one entity, you must use this header to specify which entity to perform the operation in. If the OAuth token is only valid for a single entity, or you do not have Zuora Multi-entity enabled, you do not need to set this header.

Zuora-Org-Ids String No

Comma separated IDs. If you have Zuora Multi-Org enabled, you can use this header to specify which orgs to perform the operation in. If you do not have Zuora Multi-Org enabled, you should not set this header.

The IDs must be a sub-set of the user's accessible orgs. If you specify an org that the user does not have access to, the operation fails.

If the header is not set, the operation is performed in scope of the user's accessible orgs.

Accept-Encoding String No

Include the Accept-Encoding: gzip header to compress responses as a gzipped file. It can significantly reduce the bandwidth required for a response.

If specified, Zuora automatically compresses responses that contain over 1000 bytes of data, and the response contains a Content-Encoding header with the compression algorithm so that your client can decompress it.

Request body fields

Name Type Required Description
processingOptions Object No

Processing options for generating billing documents.

processingOptions.billingOptions Object No
processingOptions.billingOptions.documentDate String No

The invoice date displayed on the billing document.

processingOptions.billingOptions.targetDate String No

Date through which to calculate charges for order line items if a billing document is generated. See What is a Target Date?.

processingOptions.runBilling Boolean No

Indicates if the current request needs to generate a billing document. The billing document will be generated against all Order Line Items included in this order.

fulfillments[] Array No
fulfillments[].fulfillmentItems[] Array No
fulfillments[].fulfillmentItems[].customFields Object No

Container for custom fields of a Fulfillment Item object.

fulfillments[].fulfillmentItems[].description String No

The description of the Fulfillment Item.

fulfillments[].fulfillmentItems[].itemIdentifier String No

The external identifier of the Fulfillment Item.

fulfillments[].description String No

The description of the Fulfillment.

fulfillments[].billTargetDate String No

The target date for the Fulfillment to be picked up by bill run for billing.

fulfillments[].carrier String No

The carrier of the Fulfillment. The available values can be configured in Billing Settings > Fulfillment Settings through Zuora UI.

fulfillments[].quantity Number No

The quantity of the Fulfillment.

fulfillments[].trackingNumber String No

The tracking number of the Fulfillment.

fulfillments[].fulfillmentDate String No

The date of the Fulfillment.

fulfillments[].state String No

The state of the Fulfillment. See State transitions for an order, order line item, and fulfillment for more information.

Possible values:

  • "Booked"
  • "Complete"
  • "Executing"
  • "Cancelled"
  • "SentToBilling"
fulfillments[].excludeItemBookingFromRevenueAccounting Boolean No

The flag to exclude Fulfillment from revenue accounting.

Note: This field is only available if you have the Zuora Billing - Revenue Integration feature enabled.

fulfillments[].fulfillmentLocation String No

The fulfillment location of the Fulfillment. The available values can be configured in Billing Settings > Fulfillment Settings through Zuora UI.

fulfillments[].fulfillmentSystem String No

The fulfillment system of the Fulfillment. The available values can be configured in Billing Settings > Fulfillment Settings through Zuora UI.

fulfillments[].excludeItemBillingFromRevenueAccounting Boolean No

The flag to exclude Fulfillment related invoice items, invoice item adjustments, credit memo items, and debit memo items from revenue accounting.

Note: This field is only available if you have the Zuora Billing - Revenue Integration feature enabled.

fulfillments[].customFields Object No

Container for custom fields of a Fulfillment object.

fulfillments[].externalId String No

The external id of the Fulfillment.

fulfillments[].fulfillmentType String No

The type of the Fulfillment.

Possible values:

  • "Return"
  • "Delivery"
fulfillments[].orderLineItemId String No

The reference id of the related Order Line Item.

How to start integrating

  1. Add HTTP Task to your workflow definition.
  2. Search for the API you want to integrate with and click on the name.
    • This loads the API reference documentation and prepares the Http request settings.
  3. Click Test request to test run your request to the API and see the API's response.