Ankorstore Fulfillment API
ℹ️ Here you can find the information and endpoint specification related to fulfillment of the orders.## 💡 About Fulfillment_Fulfillment_ is the process of preparing and shipping orders to customers via Ankorstore Fulfillment Centers.Brands that use fulfillment send their inventory to a warehouse in advance, and when orders come in, the warehousepicks, packs, and ships on the brand's behalf.### What does "fulfillable" mean?The concept of a "fulfillable" is _that which is required to prepare and ship a product (variant)_.While a Fulfillment Centre deals exclusively with items, which represents a single item that an employee can pick up and prepare for shipping.A fulfillable is simply a set of one or more items, that together represent a product as ordered.Use the [List Fulfillables](#tag/Fulfillment/operation/fulfillment-list-fulfillable) endpoint to check stockavailability for specific product variants before creating orders. For more detailed stock information —including quantities by location, status, and lot — use the[Stock State endpoint](/api/astral/v1/stock/state) from the Ankorstore Stock Tracking and Logistics API (ASTRAL).### FulfillmentsWhen a _Master Order_ has fulfillment requested, one or more _Fulfillments_ are created. Multiple fulfillmentscan be associated with a single master order (many-to-one). You can retrieve their details and track progressthrough the following statuses:| Status | Description || --- | --- || `requested` | Fulfillment has been requested for the order || `created` | Fulfillment has been created in the warehouse system || `scheduled` | Fulfillment is scheduled for picking || `released` | Fulfillment has been released for picking || `shipped` | Fulfillment has been shipped from the warehouse || `cancelled` | Fulfillment has been cancelled || `cancellation_requested` | A cancellation has been requested but not yet processed |Pass `?include=statusUpdates` when retrieving a fulfillment to see the full history of status transitions.### LotsIf your products are lot-tracked or expiry-tracked, the [List Lots](#tag/Fulfillment/operation/fulfillment-list-lots)endpoint shows the current lot inventory in the warehouse, including lot numbers, available quantities, andexpiry/sell-by dates. You can filter and sort by available quantity, sell-by date range, and product name.### Fulfillment CostsUse the [Get Fulfillment Costs](#tag/Fulfillment/operation/fulfillment-costs-get-specifications) endpoint to estimatefulfillment costs before committing to an order. Provide the destination country, parcel dimensions, and pickingquantity to receive a cost breakdown by category (shipping, pick fees by quantity tier).> ⚠️ The cost estimation does **not** include packing consumables. The actual invoiced amount may differ.## ReplenishmentsReplenishments are required to send inventory to the warehouse. They follow a specific workflow:### Replenishment WorkflowstateDiagram-v2 direction LR [*] --> created created --> confirmed : Brand confirms confirmed --> sent : Sent to warehouse sent --> delivered : Arrives at warehouse delivered --> received : Items put into stock received --> [*]* **Created**: When a replenishment is initially created, it will be at status `created` and is considered a draft. In this state, it can be edited via PATCH requests or deleted.* **Confirmed**: Once editing is complete, the status should be updated to `confirmed` as part of a PATCH request. At this point, the replenishment information will be sent to the warehouse (asynchronously).* **Sent**: Once the replenishment information is sent to the warehouse, the status changes to `sent`. The replenishment will remain in this status while waiting for delivery.* **Delivered**: When the replenishment physically arrives at the warehouse, its status will be automatically updated to `delivered`.* **Received**: Once the items are put into stock at the warehouse, the status will be updated to `received`. At this stage, receipts are added with the received stock quantities and lots.### Creating a ReplenishmentEach replenishment requires a carrier name, shipment type, and a list of items with their fulfillment item IDsand quantities:```json5// POST /api/v1/fulfillment/replenishments{ "fulfillmentBrandId": "a1b2c3d4-e5f6-7890-abcd-ef1234567890", "warehouseId": "98765432-abcd-ef01-2345-678901234567", "shippingCarrierName": "DHL", "shipmentType": "PARCEL", // "LTL", "FTL", or "PARCEL" "items": [ { "fulfillmentItemId": "d290f1ee-6c54-4b01-90e6-d701748f0851", "quantity": 100 } ]}```After creating a replenishment, update its status to `confirmed` via PATCH when you are ready to notify the warehouse.### How Fulfillment Connects to OrdersThe diagram below shows how fulfillment fits into the order lifecycle:graph LR A[Master Order] --> D[Fulfillment 1] A --> E[Fulfillment 2] F[Replenishment] --> G[Warehouse Stock] G --> D G --> E1. Brands send inventory to the warehouse via _Replenishments_2. When fulfillment is requested for a _Master Order_, one or more _Fulfillments_ are created3. The warehouse picks items from stock and ships each fulfillment4. Use the fulfillment endpoints to track both your inventory and fulfillment status
Ankorstore Fulfillment API is one of 21 APIs that Ankorstore publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Fulfillment. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 18 operations across 14 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.
Requests are made against 2 base URLs: https://www.public.ankorstore-sandbox.com, https://www.ankorstore.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Ankorstore Fulfillment API declares
2 security schemes
for authenticating requests.
It supports OAuth 2.0 (ProductionOAuth2ClientCredentials) using the clientCredentials flow.
It supports OAuth 2.0 (TestOauth2ClientCredentials) using the clientCredentials flow.
By default, every request must be authenticated.
Paths & Operations 18
Across 14 paths, the API surfaces 18 operations — 1 DELETE, 11 GET, 1 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.
ℹ️ Here you can find the information and endpoint specification related to fulfillment of the orders. 💡 About Fulfillment Fulfillment is the process of preparing and shipping orde…
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Ankorstore 12
Other APIs Ankorstore publishes across the network.
This is an independent, third-party profile of Ankorstore Fulfillment API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.