List Fulfillments
GET/api/veracore/integration-instances/:integration_instance/fulfillments
List SKU.io sales order fulfillments dispatched to this Veracore integration instance. Only fulfillments of the Veracore fulfillment type are returned, scoped to the warehouse linked to the instance when one is configured.
Any valid API token can call this endpoint — no specific scope required. Manage tokens.
Use this to find the fulfillment a Veracore order shipped against, then link it with the link-fulfillment endpoint. Each row is a full fulfillment record plus a customer_name convenience field.
Filters
filter[search]— matches fulfillment number, tracking number, sales order number, or customer name.filter[status]— exact fulfillment status.filter[requested_shipping_method_id]— exact shipping method id.
Sorting
sort accepts id, fulfillment_number, status, fulfilled_at, created_at, updated_at (prefix with - for descending). Default sort is -id.
Errors
404when the integration instance does not exist or is not a Veracore instance.
Authentication: Requires Bearer token.
Request
Responses
- 200
- 401
- 403
- 404
- 429
OK
Response Headers
Unauthenticated — the bearer token is missing, revoked, expired, or malformed. Never retry automatically; fix the credential. See the Errors guide.
Forbidden — the token lacks a required scope, the endpoint is not available to API tokens, or the user behind the token lacks the permission. A human must adjust the token scopes or user permissions; do not retry.
Not found — no record with the given identifier (or the route does not exist). Verify the ID before retrying.
Rate limited — platform limit is 1,000 requests/min; individual tokens may carry lower limits. Honor the Retry-After header before retrying. See the Rate Limits guide.