> ## Documentation Index > Fetch the complete documentation index at: https://docs.kibocommerce.com/llms.txt > Use this file to discover all available pages before exploring further. # log > log ## OpenAPI ````yaml /openapi/openapi_fulfillment.json post /commerce/fulfillment/rebalancer/audit/runs/{runId}/log openapi: 3.0.0 info: description: |-

FULFILLMENT

The Fulfillment APIs support order management and fulfillment workflows based on the Shipment API and its packages, including supporting needs such as pick waves and manifests. Once an order has been placed, it generally cannot be edited at the order-level. Instead, changes to the items, pricing, and other information must be done at the shipment level with the Shipment API. See the Fulfillment user guides for more information about fulfillment in UCP.

When using the Shipment API to transition a shipment through each stage of its fulfillment process, it can be difficult to remember how to format the next step's endpoint and the expected parameters on-the-fly. Additionally, if a call such as cancellation, adding tracking information, or marking the shipment as fulfilled needs to be performed outside of the usual fulfillment flow, it may be confusing to determine how to perform the action without referring to the documentation. To assist with this, the Shipment API provides guidelines within the response body. This response includes two objects, workflowState and _links, that detail the shipment's next step in the workflow as well as all possible actions currently available to the shipment. Use this walkthrough to better understand how to work with this response data.

Use the Customer Survey resource to create surveys and gather data from your customers.

Use the Manifests resource to create shipping manifests for fulfillment partners such as Canada Post that require manifests for groups of shipments.

Use the Pick Wave resource to generate and process pick waves for picking groups of items at a fulfillment locations.

Use the Shipment, Shipment Attributes, Shipment Data, and Shipment Notification resources to manage the actual shipments being fulfilled and perform actions on them.

Use the Shipment Packages resource to create, update, and delete the individual packages within a shipment.

Use the Storefront resource to retrieve shipment information for the storefront.

Use the Workflow Process resource to retrieve BPM configurations and the fulfillment steps based on shipment type.

title: Fulfillment - Production Profile version: 0.0.1 servers: - description: Kibo Base URL url: '{baseUrl}/api' variables: baseUrl: default: https://t1000000.sb.usc1.gcp.kibocommerce.com description: Base URL security: - bearerAuth: [] tags: - name: CustomerSurvey - name: Fulfillment - name: FutureShipment - name: GiftReceipt - name: Manifest - name: PickWave - name: Rendition - name: ShipmentAttributes - name: ShipmentContact - name: Shipment - name: ShipmentData - name: ShipmentHold - name: ShipmentNotes - name: ShipmentPackages - name: ShipmentResendEmail - name: ShippingNotification - name: Storefront - name: Substitutions - name: WorkflowProcess paths: /commerce/fulfillment/rebalancer/audit/runs/{runId}/log: post: tags: - RunHistoryLog summary: log description: log parameters: - description: runId in: path name: runId required: true schema: type: string - in: header name: x-vol-site required: false schema: format: int32 type: integer - in: header name: x-vol-tenant required: true schema: format: int32 type: integer requestBody: content: application/json: schema: $ref: '#/components/schemas/LogBatchRequestDto' description: request required: true responses: '200': content: '*/*': schema: $ref: '#/components/schemas/LogBatchResponseDto' description: OK '201': description: Created '401': description: Unauthorized '403': description: Forbidden '404': description: Not Found deprecated: false components: schemas: LogBatchRequestDto: properties: entries: items: $ref: '#/components/schemas/LogEntryRequestDto' type: array title: LogBatchRequestDto type: object LogBatchResponseDto: properties: accepted: format: int32 type: integer duplicates: format: int32 type: integer title: LogBatchResponseDto type: object LogEntryRequestDto: properties: accountNumber: format: int32 type: integer assignedPriority: format: int32 type: integer childShipmentNumbers: items: format: int32 type: integer type: array distinctProductCount: format: int32 type: integer entityId: type: string entityType: type: string fulfillmentType: type: string inventoryRef: type: string lineItemCount: format: int32 type: integer lines: items: $ref: '#/components/schemas/Line' type: array locationFromCode: type: string locationToCode: type: string newPriority: format: int32 type: integer newStatus: type: string occurredAt: format: date-time type: string orderId: type: string originShipmentNumber: format: int32 type: integer outcome: type: string phase: type: string previousPriority: format: int32 type: integer priorStatus: type: string reason: type: string ruleCode: type: string ruleDescription: type: string ruleName: type: string ruleRank: format: int32 type: integer ruleVersionHash: type: string sequenceId: format: int64 type: integer serviceOrigin: type: string shipWindowEnd: format: date-time type: string shipWindowStart: format: date-time type: string splitGroupId: type: string totalUnits: format: int32 type: integer triggeringEventIds: items: type: string type: array title: LogEntryRequestDto type: object Line: properties: inventoryId: format: int32 type: integer lineId: format: int32 type: integer movement: type: string productCode: type: string productDescription: type: string qty: format: int32 type: integer sku: type: string supplyDate: type: string supplySource: type: string unitsChanged: format: int32 type: integer upc: type: string title: Line type: object securitySchemes: bearerAuth: bearerFormat: JWT description: JWT Authorization header using the Bearer scheme. scheme: bearer type: http ````