Angler Fulfilment API

Connect your own system (ERP, OMS or custom shop) to our warehouse. Send orders, read them back, keep products and stock in sync, announce returns, and get told by webhook as every order moves.

Talk to us about an integration Client login
  • REST and JSONHTTPS, one versioned base URL
  • API keys with scopesOrders, stock and products, separately
  • Signed webhooksHMAC-SHA256, retried for about two days
  • Same system as our floorBuilt on Angler's own warehouse software

Overview

The Angler Fulfilment API lets your system work with our warehouse without anyone signing in. With it you can:

  • send orders, read them back and cancel them before picking starts;
  • read live stock levels for every product;
  • add and change products (SKUs, barcodes, weights and sizes);
  • announce returns and read them back.

Separately, we can push order events to your system by webhook: picked, packed, despatched with tracking, delivered, and more.

ItemValue
Base URLhttps://portal.anglerfulfilment.co.uk/api/v1
FormatHTTPS, JSON request and response bodies (Content-Type: application/json)
AuthenticationX-Api-Key header
TimestampsISO 8601 in UTC, for example 2026-11-18T09:41:07.512Z
CountriesISO 3166-1 alpha-2, for example GB, IE, FR
MoneyDecimal strings, for example "14.99". API orders are recorded in GBP
Weights and sizesGrams (weight_g) and millimetres (length_mm, width_mm, height_mm)

The API is available to Angler clients once their account is verified and the warehouse system is switched on for it. If you sell on Shopify, WooCommerce, eBay or TikTok Shop you may not need the API at all: see our platform integrations.

Quick start

KEY="afk_3f9a1c2e_..."
BASE="https://portal.anglerfulfilment.co.uk/api/v1"

# Read stock
curl -s "$BASE/inventory?limit=50" -H "X-Api-Key: $KEY"

# Create an order (safe to retry with the same external_ref)
curl -s -X POST "$BASE/orders" -H "X-Api-Key: $KEY" -H "Content-Type: application/json" -d '{
  "external_ref": "WEB-10023",
  "ship_to": { "name": "Alex Example", "line1": "10 Example Street", "city": "Manchester", "postcode": "M1 1AA", "country": "GB" },
  "lines": [ { "sku": "TSHIRT-BLK-M", "quantity": 2 } ]
}'

# Find it again by your own reference
curl -s "$BASE/orders?search=WEB-10023&exact=true" -H "X-Api-Key: $KEY"

Authentication

Creating a key

A Client Admin creates keys in the client portal under Warehouse > Connect your store > Your own system (API keys). Give the key a name and tick the scopes it needs. Our team can also create one for you.

The full key is shown once, when it is created. We store only a hash of it, so a lost key cannot be recovered: revoke it and make a new one. Keys look like this:

afk_3f9a1c2e_Qm9vS2V5RXhhbXBsZU9ubHlOb3RSZWFsMTIz

The afk_xxxxxxxx part is the key's prefix, shown in the portal so you can tell keys apart, along with when each key was last used. Revoking a key takes effect on the next request.

Sending the key

Send the key in the X-Api-Key header on every request. The Authorization: Bearer header is not used for API keys.

GET /api/v1/orders HTTP/1.1
Host: portal.anglerfulfilment.co.uk
X-Api-Key: afk_3f9a1c2e_Qm9vS2V5RXhhbXBsZU9ubHlOb3RSZWFsMTIz

Scopes

ScopePortal labelLets the key
ordersSend orders and read them backCreate, read and cancel orders; announce and read returns
stockRead stock levelsRead stock and products
productsAdd and change productsRead, create and update products

A key only ever sees your own company's data and never has Angler staff rights. It works only on the endpoints on this page; any other part of the portal (invoices, documents, messages, key and webhook management) refuses it.

Authentication errors

HTTPerror.codeWhen
401AUTH_REQUIREDNo key was sent
401API_KEY_INVALIDThe key is unknown or revoked
401API_KEY_NOT_ALLOWEDThat endpoint needs a person signed in; a key cannot use it
403FORBIDDENThe key does not have the scope the endpoint needs
403WMS_NOT_ENABLEDThe warehouse system is not yet switched on for your account
403ACCOUNT_SUSPENDEDYour account is suspended or closed

Responses and errors

Success

Every successful response has the same envelope. The request_id is also sent in the X-Request-Id header; quote it when you contact us about a request.

{
  "success": true,
  "data": { },
  "message": null,
  "request_id": "6b1f3c0e-2d7a-4f43-9a1e-5c2b8d9e0f11"
}

Errors

{
  "success": false,
  "error": { "code": "NOT_FOUND", "message": "Record not found." },
  "request_id": "6b1f3c0e-2d7a-4f43-9a1e-5c2b8d9e0f11"
}
  • Branch on the HTTP status and error.code. error.message is plain English and its wording may change.
  • A request that breaks a field rule answers 400 BAD_REQUEST with the first problem found, for example ship_to.country must match /^[A-Za-z]{2}$/ regular expression.
  • A record that does not exist, or belongs to someone else, answers 404 NOT_FOUND.
  • Fields that are not documented here are ignored, not rejected.
  • An unexpected fault answers 500 INTERNAL_ERROR. Retry later, and tell us the request_id if it repeats.

Pagination

List endpoints take page (from 1) and limit (default 25, at most 50 for an API key) and return:

{ "items": [ ], "pagination": { "page": 1, "limit": 25, "total": 312, "total_pages": 13 } }

Responses can include fields that are not described on this page. They are for our own use and may change, so please build only on the fields documented here.

Orders

Order statuses

StatusMeaning
ALLOCATEDChecked and stock reserved: ready to pick
ON_HOLDStopped by one or more holds (see below)
PICKINGOn a pick list, being picked
PICKEDAll items picked, at the pack bench
PACKEDPacked and checked
DESPATCHEDLeft the warehouse, with a tracking number on the shipment
DELIVEREDDelivered, from courier tracking or confirmed by our team
CANCELLEDCancelled

What happens when you send an order

  1. It gets an Angler order number, for example SO-001042, and a despatch deadline from our cut-off times.
  2. It is checked in the same request: each line's sku is matched to one of your products, the address is checked, and stock is reserved for every line (all or nothing).
  3. It comes back ALLOCATED, ready for our team to pick, or ON_HOLD with the reason in holds.
Hold codeMeaningClears by itself?
INSUFFICIENT_STOCKNot enough stockYes, when stock arrives
UNMAPPED_SKUA line matches none of your productsYes, once you add the product
ADDRESS_INVALIDThe address is incomplete or the postcode is not validYes, once the address is fixed in the portal
MISSING_PRODUCT_DATAA product has no weight or size, so a label cannot be boughtYes, once the product is updated
CREDIT_HOLDThe account is on holdYes
CLIENT_QUERY, MANUAL, SHORT_PICK, LABEL_FAILEDA question, a hold by hand, a short pick or a label problemNo, a person deals with it

Each hold also has a detail (for example Short: TSHIRT-BLK-M (2)) and a plain-English help line.

SKU matching: exact SKU first, then SKU ignoring case, then a product barcode. A case or inner barcode multiplies the line quantity by the units it holds.

Address rules: name, line1 and city are needed; UK postcodes must be valid and are tidied (m11aa becomes M1 1AA); other countries need a postcode except IE, HK and AE. A bad address does not reject the request: the order is created and held.

POST/orders

Create an order. Scope orders. Answers 201 with the full order.

FieldTypeRequiredRules
external_refstringYesYour order reference, 1 to 64 characters. Also the de-duplication key (below)
ship_to.namestringYes1 to 120
ship_to.companystringNoUp to 120
ship_to.emailstringNoUp to 200
ship_to.phonestringNoUp to 40
ship_to.line1stringYes1 to 200
ship_to.line2stringNoUp to 200
ship_to.citystringYes1 to 100
ship_to.regionstringNoUp to 100
ship_to.postcodestringYesUp to 12 (may be empty for IE, HK, AE)
ship_to.countrystringYesTwo letters
linesarrayYes1 to 200 lines
lines[].skustringYes1 to 64
lines[].quantityintegerYes1 to 100000
lines[].unit_pricestringNoDecimal, for example "14.99"
lines[].namestringNoUp to 200, shown to the warehouse
urgentbooleanNoDefault false
requested_servicestringNoUp to 80. The delivery service you would like
gift_messagestringNoUp to 500
packing_instructionsstringNoUp to 500
order_valuestringNoDecimal, recorded in GBP

Safe retries. external_ref is the de-duplication key. Sending the same external_ref again returns the original order (still 201) and changes nothing, even if the body is different. So you can retry after a timeout, and should use a new reference for a genuinely new order.

POST /api/v1/orders
X-Api-Key: afk_3f9a1c2e_...
Content-Type: application/json

{
  "external_ref": "WEB-10023",
  "ship_to": {
    "name": "Alex Example",
    "email": "[email protected]",
    "phone": "+447700900123",
    "line1": "10 Example Street",
    "line2": "Flat 2",
    "city": "Manchester",
    "postcode": "m1 1aa",
    "country": "GB"
  },
  "lines": [
    { "sku": "TSHIRT-BLK-M", "quantity": 2, "unit_price": "14.99", "name": "T-shirt, black, M" },
    { "sku": "CAP-NAVY", "quantity": 1, "unit_price": "14.99", "name": "Cap, navy" }
  ],
  "requested_service": "Tracked 48",
  "packing_instructions": "Please include the returns slip.",
  "order_value": "44.97"
}

Response (shortened):

{
  "success": true,
  "data": {
    "order_id": "2d4f8a9e-6b1c-4e7a-9f0d-3c5b7a1e2f40",
    "number": "SO-001042",
    "channel": "API",
    "external_ref": "WEB-10023",
    "status": "ALLOCATED",
    "urgent": false,
    "ordered_at": "2026-11-18T09:41:07.512Z",
    "ship_by": "2026-11-18T15:00:00.000Z",
    "order_value": "44.97",
    "currency": "GBP",
    "ship_to": { "name": "Alex Example", "line1": "10 Example Street", "city": "Manchester", "postcode": "M1 1AA", "country": "GB" },
    "lines": [
      { "channel_sku": "TSHIRT-BLK-M", "quantity": 2, "qty_allocated": 2, "qty_picked": 0, "qty_packed": 0,
        "product": { "sku": "TSHIRT-BLK-M", "name": "Organic T-shirt, black, medium" } }
    ],
    "holds": [],
    "events": [
      { "type": "order.created", "message": "Order received.", "created_at": "2026-11-18T09:41:07.530Z" },
      { "type": "order.allocated", "message": "Checked and stock reserved. Ready to pick.", "created_at": "2026-11-18T09:41:07.700Z" }
    ],
    "shipments": [],
    "despatched_at": null,
    "delivered_at": null,
    "cancelled_at": null
  },
  "message": null,
  "request_id": "9e8d7c6b-5a4f-4e3d-8c2b-1a0f9e8d7c6b"
}
HTTPerror.codeWhen
400BAD_REQUEST or VALIDATIONA field breaks a rule above
409CLIENT_NOT_VERIFIEDYour account is not verified yet

GET/orders

List orders, newest first. Scope orders.

QueryDescription
statusOne of the statuses above
searchMatches the Angler number, your external_ref, a store order number, or an exact tracking number
exact=trueWith search: whole-reference match only. Use this to look up one order by your reference
held_only=trueOnly orders on hold
page, limitSee pagination

Each item has the order fields plus units, customer, the open holds and shipments (status, tracking_number, carrier).

GET /api/v1/orders?search=WEB-10023&exact=true

GET/orders/{order_id}

One order by its order_id (a UUID, not the order number). Scope orders. Returns the same object as the create response, with every hold the order has had, its timeline in events, and one entry in shipments per parcel: parcel_no, status, carrier, service_code, tracking_number, tracking_url, despatched_at, tracking_state (IN_TRANSIT, DELIVERED, PROBLEM or UNKNOWN) and delivered_at.

POST/orders/{order_id}/cancel

Cancel an order before picking starts. Scope orders. Body: { "reason": "Customer cancelled on our website" } (1 to 500 characters). Reserved stock is released. Answers 201 with the cancelled order.

HTTPerror.codeWhen
409CANCEL_NEEDS_ANGLERPicking has started. Send us a message and we will stop it
409INVALID_TRANSITIONThe order has already gone, or was already cancelled

Changing an address, holding or releasing an order are done in the client portal.

Products

GET/products

Your active products, sorted by SKU, each with its barcodes and stock (on_hand, allocated, available). Scope products or stock. Query: search (SKU, name, barcode or FNSKU), include_inactive=true, missing_data=true (products with no weight or size), page, limit.

GET/products/{product_id}

One product. Scope products or stock.

POST/products

Add a product. Scope products. Answers 201.

FieldTypeRequiredRules
skustringYes1 to 64, no spaces at either end, unique for you
namestringYes1 to 200
descriptionstringNoUp to 2000
weight_gintegerNo0 to 1000000. Needed before a courier label can be bought
length_mm, width_mm, height_mmintegerNo0 to 10000
declared_valuestringNoDecimal. Value of one unit, for customs
hs_codestringNo6 to 10 digits
country_of_originstringNoTwo letters
kindstringNoSIMPLE (default), VIRTUAL_BUNDLE or KIT
fnskustringNo10 letters or digits (Amazon FBA)
batch_tracked, expiry_tracked, serial_tracked, fragile, dangerous_goodsbooleanNoDefault false
reorder_levelintegerNoYou are alerted when available stock falls to this level
tagsstring[]NoUp to 20, each up to 40 characters
barcodesarrayNoUp to 20: { "barcode", "uom", "quantity" }. uom is EACH (default), INNER, CASE or PALLET; quantity is needed for anything but EACH
{
  "sku": "TSHIRT-BLK-M",
  "name": "Organic T-shirt, black, medium",
  "weight_g": 180,
  "length_mm": 300, "width_mm": 250, "height_mm": 20,
  "declared_value": "14.99",
  "hs_code": "610910",
  "country_of_origin": "PT",
  "reorder_level": 50,
  "barcodes": [
    { "barcode": "5012345678900" },
    { "barcode": "15012345678907", "uom": "CASE", "quantity": 24 }
  ]
}

A repeated SKU or a barcode already on another of your products answers 409 DUPLICATE. Adding a product re-checks any orders held for that SKU.

PATCH/products/{product_id}

Change a product. Scope products. Send only the fields that change; null clears a field. barcodes and tags, when sent, replace the whole list. "active": false retires a product. The SKU cannot change once the product has stock history (409 SKU_IN_USE), and a product with stock in the warehouse cannot be made inactive (409 PRODUCT_HAS_STOCK).

Stock

GET/inventory

Live stock for each active product, sorted by SKU. Scope stock. Query: search, in_stock_only=true, low_only=true, page, limit.

FieldMeaning
on_handAll units in the warehouse
allocatedUnits reserved for orders
availableSellable units not reserved. For a virtual bundle, the number of whole sets its scarcest part allows
receivingReceived but not yet put away
quarantined, damaged, suspectUnits held back, damaged, or waiting for a recount
lowtrue when available is at or below your reorder_level
{
  "product_id": "c3d4e5f6-a7b8-4c9d-8e0f-1a2b3c4d5e6f",
  "sku": "TSHIRT-BLK-M",
  "name": "Organic T-shirt, black, medium",
  "reorder_level": 50,
  "on_hand": 140,
  "allocated": 12,
  "available": 128,
  "quarantined": 0,
  "damaged": 0,
  "receiving": 0,
  "suspect": 0,
  "low": false
}

Returns

GET/returns

Your returns, newest first. Scope orders. Query: status (EXPECTED, RECEIVED, CLOSED, CANCELLED), search (return number, tracking or order number), page, limit.

POST/returns

Tell us a return is on its way. Scope orders. Answers 201 with the return, for example RT-000318, status EXPECTED.

FieldTypeRules
order_idUUIDThe Angler order it came from (optional)
store_order_refstringUp to 60. Your order number, if we did not send the order
reasonstringUp to 500
tracking_numberstringUp to 64. The return parcel's tracking
client_notestringUp to 1000, for example "Restock if unopened"
linesarrayUp to 200: { "product_id", "quantity" }
exchangeobjectOptional: { "lines": [...], "ship_to": {...} } to send a replacement once the return is booked in. ship_to is needed only without order_id

This endpoint does not de-duplicate. Before retrying after a timeout, check GET /returns?search=<tracking or order number>.

Webhooks

Webhooks tell your system when an order moves, so you do not have to poll.

Setting one up

A Client Admin adds a webhook in the client portal under Warehouse > Connect your store > Tell your system as orders move (webhooks): an https:// URL on a public host, and the events you want (or all of them). The signing secret (whsec_...) is shown once. In the portal you can also switch a webhook off and on, change it, rotate the secret, send a test, and see the delivery log for the last 30 days with a button to send any failed message again. A webhook receives events that happen after it was created.

Events

EventSent when
order.createdAn order arrived
order.allocatedChecked and stock reserved: ready to pick. Also sent when a held order goes ahead by itself, for example when stock arrives
order.pickingPicking started
order.pickedAll items picked
order.packedPacked
order.despatchedDespatched, with the tracking number
order.deliveredDelivered (courier tracking, or confirmed by our team)
order.cancelledCancelled
order.heldAn order was held: not enough stock, an unknown SKU, a bad address, a label problem, or held by our team
order.releasedA held order was released by our team or once its problem was fixed
order.address_changedThe delivery address was changed
order.short_pickFewer items were found than ordered
order.claim_openedA claim was opened with the courier
pingOnly from "Send a test" in the portal

An order held straight away when it is checked sends order.held, and its holds are also in the POST /orders response itself. When the problem clears (stock arrives, the product is added) it sends order.allocated.

What we send

Each message is a POST to your URL with these headers:

HeaderValue
Angler-EventThe event, for example order.despatched
Angler-DeliveryAn id for this message, the same on every retry
Angler-Signaturet=<unix seconds>,v1=<hex HMAC-SHA256>
User-AgentAnglerFulfilment-Webhooks/1
{
  "id": "evt_884301",
  "type": "order.despatched",
  "created_at": "2026-11-18T16:05:41.207Z",
  "data": {
    "message": "Despatched with Royal Mail, tracking RM987654321GB.",
    "details": {},
    "order": {
      "order_id": "2d4f8a9e-6b1c-4e7a-9f0d-3c5b7a1e2f40",
      "number": "SO-001042",
      "channel": "API",
      "channel_order_number": null,
      "external_ref": "WEB-10023",
      "status": "DESPATCHED",
      "shipments": [
        {
          "parcel_no": 1,
          "carrier": "Royal Mail",
          "service_code": "TPS48",
          "tracking_number": "RM987654321GB",
          "tracking_url": "https://www.royalmail.com/track-your-item#/tracking-results/RM987654321GB",
          "despatched_at": "2026-11-18T16:05:40.950Z"
        }
      ]
    }
  }
}

data.order is a snapshot of the order when the message was queued. Carrier names, service codes and tracking links depend on the courier.

Delivery and retries

  • Messages go out within about a minute of the event.
  • Success is any 2xx answer within 10 seconds. Redirects are not followed and count as a failure.
  • A failed message is retried after 1, 5, 15, 60, 180, 360, 720 and 1440 minutes: 9 attempts over about two days.
  • Delivery is at least once and order is not guaranteed. De-duplicate on id, and use created_at and the order's status to decide what is current.
  • After 50 failed attempts in a row a webhook switches itself off, with the reason shown in the portal. Events that happen while it is off are not queued.

Verifying the signature

The signature is the lowercase hex HMAC-SHA256 of <t>.<raw request body>, keyed with your whole signing secret including the whsec_ prefix. Each retry is signed again with a new t. Verify against the raw body bytes, before parsing the JSON, compare in constant time, and reject messages whose t is more than five minutes from your clock. Rotating the secret retires the old one at once.

Node.js (Express)

const crypto = require('crypto');
const express = require('express');

function verifyAnglerSignature(rawBody, header, secret, toleranceSeconds = 300) {
  if (!header) return false;
  const parts = {};
  for (const piece of header.split(',')) {
    const i = piece.indexOf('=');
    if (i > 0) parts[piece.slice(0, i).trim()] = piece.slice(i + 1).trim();
  }
  const { t, v1 } = parts;
  if (!t || !v1 || !/^\d+$/.test(t) || !/^[0-9a-f]{64}$/.test(v1)) return false;
  if (Math.abs(Math.floor(Date.now() / 1000) - Number(t)) > toleranceSeconds) return false;
  const expected = crypto
    .createHmac('sha256', secret)      // the whole "whsec_..." string
    .update(`${t}.`, 'utf8')
    .update(rawBody)                   // the exact bytes received
    .digest();
  const given = Buffer.from(v1, 'hex');
  return given.length === expected.length && crypto.timingSafeEqual(given, expected);
}

const app = express();
app.post('/angler-webhook', express.raw({ type: 'application/json' }), (req, res) => {
  if (!verifyAnglerSignature(req.body, req.get('Angler-Signature'), process.env.ANGLER_WEBHOOK_SECRET)) {
    return res.status(400).send('bad signature');
  }
  const event = JSON.parse(req.body.toString('utf8'));
  res.sendStatus(204);               // answer first, then do the work
  // handle event.type and event.data.order, de-duplicating on event.id
});
app.listen(3000);

Python (Flask)

import hashlib
import hmac
import os
import time

from flask import Flask, request, abort

def verify_angler_signature(raw_body: bytes, header: str, secret: str, tolerance_seconds: int = 300) -> bool:
    if not header:
        return False
    parts = {}
    for piece in header.split(","):
        key, sep, value = piece.partition("=")
        if sep:
            parts[key.strip()] = value.strip()
    t, v1 = parts.get("t"), parts.get("v1")
    if not t or not v1 or not t.isdigit():
        return False
    if abs(int(time.time()) - int(t)) > tolerance_seconds:
        return False
    expected = hmac.new(
        secret.encode("utf-8"),                     # the whole "whsec_..." string
        t.encode("ascii") + b"." + raw_body,
        hashlib.sha256,
    ).hexdigest()
    return hmac.compare_digest(expected, v1)

app = Flask(__name__)

@app.post("/angler-webhook")
def angler_webhook():
    raw = request.get_data()                        # exact bytes, before JSON parsing
    if not verify_angler_signature(raw, request.headers.get("Angler-Signature", ""), os.environ["ANGLER_WEBHOOK_SECRET"]):
        abort(400)
    event = request.get_json()
    # handle event["type"], de-duplicating on event["id"]
    return "", 204

Rate limits

Each endpoint allows 100 requests per minute from one IP address. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Over the limit you get HTTP 429 with a Retry-After header in seconds: wait that long, then try again. Please check the HTTP status for this case rather than the error code.

For stock, one paged read of /inventory every few minutes is plenty; webhooks tell you about orders as they happen.

Testing and sandbox

We can give your team a sandbox account to build and test against. It uses the same base URL, API keys and webhooks as a live account, but its orders are never worked by the warehouse:

  • no stock is reserved and no courier label is bought;
  • orders never reach our warehouse floor and are never charged;
  • SKU matching, address checks and holds work exactly as they do live, so you can test those too;
  • you move a test order through the warehouse steps yourself, and every step sends the normal webhook.

Ask us for a sandbox account. Add your test products with POST /products, create a key, then send orders as you would live.

POST/orders/{order_id}/sandbox/advance

Sandbox accounts only. Moves a test order to its next step, or through every step up to to. Scope orders. Answers 201.

FieldTypeRequiredRules
tostringNoPICKING, PICKED, PACKED, DESPATCHED or DELIVERED. Left out, the next step
POST /api/v1/orders/2d4f8a9e-6b1c-4e7a-9f0d-3c5b7a1e2f40/sandbox/advance
X-Api-Key: afk_3f9a1c2e_...
Content-Type: application/json

{ "to": "DELIVERED" }
{
  "success": true,
  "data": {
    "order_id": "2d4f8a9e-6b1c-4e7a-9f0d-3c5b7a1e2f40",
    "number": "SO-001042",
    "status": "DELIVERED",
    "steps": ["PICKING", "PICKED", "PACKED", "DESPATCHED", "DELIVERED"]
  },
  "message": null,
  "request_id": "..."
}

Each step writes the same event a live order does (order.picking, order.picked, order.packed, order.despatched, order.delivered), with "sandbox": true in data.details. At despatch the order gets a parcel with carrier Sandbox and a made-up tracking number starting ANGLERTEST.

HTTPerror.codeWhen
403SANDBOX_ONLYThe order is in a live account
409ORDER_ON_HOLDThe order is on hold. Fix what holds it first
409INVALID_TRANSITIONThe order is already at or past that step, or cancelled

Testing on a live account

On a live account everything is real: an order created through the API is checked, has stock reserved and goes to our warehouse floor. Use the read endpoints and the portal's "Send a test" webhook button freely, agree a plan with us before sending test orders, and cancel them straight away with POST /orders/{order_id}/cancel. During onboarding we set up your account and keys with you.

All endpoints

All paths are relative to https://portal.anglerfulfilment.co.uk/api/v1.

MethodPathScopeSuccess
GET/ordersorders200
POST/ordersorders201
GET/orders/{order_id}orders200
POST/orders/{order_id}/cancelorders201
POST/orders/{order_id}/sandbox/advanceorders (sandbox accounts)201
GET/productsproducts or stock200
POST/productsproducts201
GET/products/{product_id}products or stock200
PATCH/products/{product_id}products200
GET/inventorystock200
GET/returnsorders200
POST/returnsorders201

Planning an integration?

Tell us about your system and order volumes. We are happy to set up a call with your integration lead.

Contact us support@anglerfulfilment.co.uk
Chat on WhatsApp