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.
This endpoint currently requires session authentication; Personal Access Token scope support is in progress.
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 customer_name and sales_order_number convenience fields lifted from the related sales order.
Search
filter[search] runs a fuzzy LIKE across fulfillment_number, tracking_number, the related sales order's sales_order_number, and the customer's name. Narrow it with the top-level search_columns parameter, or force exact matching on specific columns with search_strict_columns.
Filters
Every filterable column accepts an operator suffix, e.g. filter[status.is]=fulfilled or filter[fulfillment_number.contains]=F-51. The bare form (filter[status]=fulfilled) is equivalent to .is.
- Text columns (
fulfillment_number,status,tracking_number,sales_order_number,customer_name,requested_shipping_method_name):is,is_not,contains,does_not_contain,is_one_of,is_not_one_of,starts_with,does_not_start_with,ends_with,does_not_end_with,is_empty,is_not_empty. - Numeric columns (
id,requested_shipping_method_id):is,is_not,is_one_of,is_not_one_of,greater_than,less_than,greater_than_or_equal,less_than_or_equal,between,is_empty,is_not_empty. - Datetime columns (
fulfilled_at,created_at,updated_at):is,is_not,before,after,on_or_before,on_or_after,between,is_empty,is_not_empty, plus the relative operatorstoday,yesterday,tomorrow,past_week,past_month,past_year,next_week,next_month,next_year.
sales_order_number, customer_name and requested_shipping_method_name filter through their relationships; negative operators resolve via whereDoesntHave.
Advanced filter groups
Instead of flat keys, clients may send a base64-encoded filter_groups tree, allowing nested AND/OR groups over the same columns. Unregistered columns inside the tree are silently ignored.
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.