Requests a kitting run: Hive assembles quantity kits in the given warehouse, exactly as when a kit is requested in the Hive app. Name the kit in one of two ways, never both:
kit_definition_id: an existing kit definition, fromGET /kit_definitionsor a kitting request returned by this API, to request the same kit again.kit_definition: a new kit definition, created with the request, with the same fields and rules asPOST /kit_definitions.
A body with both or neither is rejected with a 400. The new request starts in requested and waits for Hive's review. It is refused with a 422 when fulfillment is paused for the merchant, when the kit definition or the warehouse is not the merchant's, when the inline kit definition is refused for any reason POST /kit_definitions gives, or when production_date_required is true for a kit SKU without batch tracking; nothing is created then, not even the definition.
Requests another run of an existing kit definition.
The kit definition to assemble, from GET /kit_definitions or kit_definition_id of a kitting request; it must belong to one of the merchant's SKUs
Whether the warehouse records a production date for the produced kits; may only be true when the kit SKU has batch tracking enabled
- Mock serverhttps://hive-merchant-api.redocly.app/_mock/merchant-api-v2/mapi_v2_oas31/kitting_requests
- Production APIhttps://app.hive.app/merchant_api/v2/kitting_requests
- Staging APIhttps://staging.app.hive.app/merchant_api/v2/kitting_requests
curl -i -X POST \
https://hive-merchant-api.redocly.app/_mock/merchant-api-v2/mapi_v2_oas31/kitting_requests \
-H 'Authorization: Bearer <YOUR_token_HERE>' \
-H 'Content-Type: application/json' \
-d '{
"kit_definition_id": 9311,
"warehouse_id": 4,
"quantity": 500
}'Kitting request created successfully
When the produced kits were restocked and the request completed; null until then
The component SKUs one kit is assembled from, in the order of the kit definition
The kit definition (components and assembly instructions) this request uses; pass it to POST /kitting_requests to request the same kit again
Number of kits produced and restocked; null until the request is completed
Whether the warehouse records a production date for the produced kits (only for kit SKUs with batch tracking)
The restocking shipment, created with the request, that brings the produced kits back into stock and is readable through GET /restocking_shipments/{id}; null for requests created before November 2025
Status of the kitting request. Possible values:
- requested: Created and waiting for Hive's review of the kit
- approved: Reviewed by Hive and waiting for the components to be picked
- processing: The components are being picked and assembled, or the kits are being restocked
- completed: The produced kits are back in stock;
produced_quantityholds their number - cancelled: The request was cancelled
{ "id": 11842, "status": "completed", "quantity": 500, "produced_quantity": 498, "production_date_required": false, "warehouse_id": 4, "sku_id": 586004, "sku_code": "GIFTBOX-XMAS", "kit_definition_id": 9311, "components": [ { … }, { … } ], "restocking_shipment_id": 66241, "created_at": "2026-09-01T09:12:44.512+02:00", "updated_at": "2026-09-04T16:03:10.871+02:00", "completed_at": "2026-09-04T16:03:10.000+02:00" }