Quantities drift, holds need to be set or cleared, and product sometimes gets recategorized. All of it goes through the same endpoint.
Adjust quantity
curl -X PATCH https://api.seedlink.dev/v1/connections/8f9ab02c-78c2-4292-a43d-79a327a4efd5/facilities/fac_C11-0000123-LIC/packages/pkg_2385762 \
-H "Authorization: Bearer sl_at_..." \
-H "Content-Type: application/json" \
-d '{ "quantity": 428.1 }'
Put a package on or off hold
curl -X PATCH https://api.seedlink.dev/v1/connections/8f9ab02c-78c2-4292-a43d-79a327a4efd5/facilities/fac_C11-0000123-LIC/packages/pkg_2385762 \
-H "Authorization: Bearer sl_at_..." \
-H "Content-Type: application/json" \
-d '{ "is_on_hold": true }'
Recategorize it
curl -X PATCH https://api.seedlink.dev/v1/connections/8f9ab02c-78c2-4292-a43d-79a327a4efd5/facilities/fac_C11-0000123-LIC/packages/pkg_2385762 \
-H "Authorization: Bearer sl_at_..." \
-H "Content-Type: application/json" \
-d '{
"item_name": "Blue Dream Shake",
"item_category": "Shake/Trim"
}'
Every field on the update is optional. Send only what's changing.
Gotchas
Package writes only work against sandbox connections. There's no dedicated "waste" or "destroy" endpoint either; zeroing out quantity is the pattern for recording a package that's been fully used up or destroyed.
Last modified on August 2, 2026