Create Appeasement


This documentation is for translated APIs and intended only for some implementations who have upgraded from a previous version of Order Management. Verify whether your implementation uses translated APIs before making this call, as you will experience errors if your tenant is not configured to use these. If your implementation is not configured to do so, then refer to the standard API documentation instead.

If an order requires appeasement for any reason, that progress should begin with the Create Order Appeasement. This will allow the merchant to confirm details about who is responsible for the appeasement, how much credit they will pay, and other important information.

There are two cases in which this call is made; one in which a retailer pays the appeasement credit, and one in which a manufacturer pays the appeasement credit. The relevant case determines which of the below endpoint templates is used.

Note that the request body and parameter schemas outlined in this guide are the exact same as in the previous version of OMS, as the Unified Commerce platform supports backwards compatibility for this API. The only change to this request is the format of the base endpoint, as shown in the below table. Remember to provide the x-vol-tenant key for authentication in the headers.

Production URLhttps://{tenantId}{orderId}&{retailerId_or_manufacturerId}={id}
Sandbox URLhttps://{tenantId}{orderId}&{retailerId_or_manufacturerId}={id}
Supported FormatsJSON

The ID of the order that this appeasement is being created for should be specified in the endpoint, by appending a “/?” to the call followed by the orderID. Following the orderID, either a retailerID or a manufacturerID should also be provided depending on which entity will be paying the credit. As explained later in this guide, this parameter must match the creditPayee in the request body as well as be provided again in the body.

  • Retailer Call: https://{tenantId}{orderId}&retailerID={retailerId}
  • Manufacturer Call: https://{tenantId}{orderId}&manufacturerId={manufacturerId}


The example case creates an API call for an appeasement that has the following properties:

  • $2 refund on Order 012345, paid by Manufacturer 543210
  • From merchant’s catalog 0
  • User ID 123456

This guide will demonstrate how to put together each section of the request to build this appeasement.

Required Parameters

The minimum required parameters are those that apply to the refund that will be awarded, specifically the person who will be paying it and the amount the customer will receive.

While the retailerID or manufacturerID is specified in the endpoint, it should still be provided in the body as well. Only one of these two parameters is required at a time, based on the appropriate creditPayee case – if a manufacturer is set as the payee but a retailerID is provided, then an error will be returned.

creditPayeeenumThe entity who will pay for the credit (this should be set to “MANUFACTURER” or “RETAILER”, unless otherwise advised by Kibo).
creditAmountnumberThe amount to be credited.
creditDescriptionstringThe reason for the credit.
manufacterIDintegerA unique identifier for the manufacturer paying the credit. The minimum value is “0”. This parameter is required when creditPayee is set to “MANUFACTURER”.
retailerIDintegerA unique identifier for the retailer paying the credit. The minimum value is “0”. This parameter is only required when creditPayee is set to “RETAILER”.
rectifyOrderbooleanShould the order be rectified? The default is “TRUE” so that even if this is not provided in the request, the parameter will be automatically set to the suggested best practice of rectification.

Optional Parameters

Other possible parameters can be provided to specify other details about the appeasement. These variables are:

orderAppeasementIDintegerA unique identifier for the appeasement. This ID is set by OMS when created in the system, so it is best to treat it as read-only and not try to set this parameter. The minimum value is “1”.
orderIDintegerA unique identifier for the existing order that the appeasement is tied to; this must be specified in the endpoint but can also be included in the request body. The minimum value is “1”.
externalOrderIDstringA client-generated unique identifier for the order.
creditCreationTimestampstringThe creation time of the credit. Supports date-time format.
catalogIDintegerThe catalog number for the manufacturer. This is also a read-only parameter utilized by OMS internally.
emailConsumerbooleanIndicates whether the consumer should be emailed when the credit is created.
userIDintegerA unique identifier for a user. The minimum value is “0”.
needToRectifybooleanWhether rectification is appropriate for the order. This is a ready-only parameter, so do not attempt to set it – use rectifyOrder instead.
rectifyAmountnumberThe amount to charge or refund for the order to be financially settled .

The Full Request

This is the entire request that will create an appeasement for Order 012345. The order and manufacturer is identified in the endpoint:


The body of the request includes the basic appeasement information:

    "creditPayee": "MANUFACTURER",
    "creditAmount": 2,
    "creditDescription": "No Inventory",
    "manufacturerID": 543210,
    "catalogID": 0,

If this example were the case of a retailer payee instead of manufacturer, then the manufacturerID parameters in the above endpoint and body would be replaced by retailerID parameters instead.

The returned response follows the same structure as the Get Appeasement API, providing information about the appeasement that was created.