Returns a specific kitting request.
- Mock serverhttps://hive-merchant-api.redocly.app/_mock/merchant-api-v2/mapi_v2_oas31/kitting_requests/{id}
- Production APIhttps://app.hive.app/merchant_api/v2/kitting_requests/{id}
- Staging APIhttps://staging.app.hive.app/merchant_api/v2/kitting_requests/{id}
curl -i -X GET \
'https://hive-merchant-api.redocly.app/_mock/merchant-api-v2/mapi_v2_oas31/kitting_requests/{id}' \
-H 'Authorization: Bearer <YOUR_token_HERE>'A kitting request
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" }