Delivery

Feeef ships COD orders through carrier integrations — one config per carrier under store.integrations.{carrier} (see Integrations for the config API). Once a carrier is configured, you can quote fees, create shipments from orders, print labels, and receive status updates pushed back by the carrier.

All merchant operations require a Bearer token unless marked Public. Inbound carrier webhook receivers are public by design — the carrier calls them, authenticated by store id + payload semantics.

Carrier catalog

Carriers are credential-required integrations: subscribing never stubs a config — write credentials first, then set active: true.

Generic carrier bridge

The bridge exposes one canonical surface over eight carriers (ecotrack, yalidine, zrexpress, mdmExpress, feeefDelivery, maystroDelivery, noest, procolis), so you don't need per-carrier request shapes. Aliases maystro, zr, and mdm are accepted for {carrierCode}.

A ParcelCreate needs at minimum reference, items[], and total (the COD amount; legacy codAmount is normalized). Useful optional fields: contact (firstName, phones[]), address (street, cityCode, stateCode), shippingType (home | pickup | store), freeShipping, pickupId (stop-desk id), fromStock, package (weight/dimensions), and carrier-specific extensions.

Send an order to a carrier

# From an existing order (parcel is derived from the order, body patches it)
curl -X POST "https://api.feeef.org/v1/stores/{storeId}/orders/{orderId}/carriers/yalidine/send" \
  -H "Authorization: Bearer $FEEEF_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "shippingType": "pickup", "pickupId": "163" }'

# Or standalone from a ParcelCreate
curl -X POST "https://api.feeef.org/v1/stores/{storeId}/integrations/ecotrack/parcels/send" \
  -H "Authorization: Bearer $FEEEF_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "reference": "ORD-1042",
    "total": 4500,
    "items": [{ "name": "Montre X", "quantity": 1 }],
    "contact": { "firstName": "Amine", "phones": ["0550000000"] },
    "address": { "street": "Cité 20 Août", "stateCode": "16", "cityCode": "1601", "country": "DZ" }
  }'

Common per-carrier operations

Carrier-native routes live under /v1/stores/{storeId}/integrations/{carrier}/…. Not every carrier implements every operation — the accordions below list exact support.

Inbound carrier webhooks

yalidine, zimou, ecotrack, zrexpress, maystroDelivery, feeefDelivery, and ecomanager accept inbound webhooks. They update the order's deliveryStatus / paymentStatus (and customStatus rules) from carrier events — parcel status changes, payments, deletions. Yalidine additionally answers the CRC subscription challenge (subscribe + crc_token). For ZR Express and Maystro, use webhook/url + webhook/setup to register; EcoManager uses POST …/ecomanager/setup.

Get a carrier fee matrix

curl -H "Authorization: Bearer $FEEEF_TOKEN" \
  "https://api.feeef.org/v1/stores/{storeId}/integrations/ecotrack/fees"

Ecotrack sync

Ecotrack has a server-side sync engine (rate-limited to one run per ~2 hours per store) that pulls parcel statuses and COD cash-in history back into orders, and posts customer payments into Finance when active. A push notification is sent when a run finishes.

Ecotrack also exposes extra reads: GET …/ecotrack/orders (parcel list), GET …/ecotrack/finance, GET …/ecotrack/statistics, GET …/ecotrack/stock/products, POST …/ecotrack/orders/{tracking}/validate, and POST …/ecotrack/scoring.

Trigger a sync

curl -X POST "https://api.feeef.org/v1/stores/{storeId}/integrations/ecotrack/sync" \
  -H "Authorization: Bearer $FEEEF_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{ "startDate": "2026-08-01T00:00:00Z" }'

Per-carrier specifics

Dispatcher

Related to fulfillment ops: POST /v1/stores/{storeId}/integrations/dispatcher/dispatch (Bearer) manually assigns orders to confirmers — body { "orderIds": [...], "strategy": "roundRobin" } with strategies random, weightedRandom, roundRobin, priority.

Shipping prices

Structured, geo-aware shipping pricing (per country/state/city, home vs desk) — the successor to the legacy per-store rate arrays. Storefronts read a single price document to compute shipping at checkout; the store references it via shippingPriceId.

Legacy shipping methods (/v1/shipping_methods resource + POST /v1/shipping_methods/{id}/fork) remain for older stores — wilaya-indexed [desk, home] arrays, same shape as the carrier fees endpoints.

List a store's shipping prices

curl -H "Authorization: Bearer $FEEEF_TOKEN" \
  "https://api.feeef.org/v1/shipping_prices?store_id={storeId}"

Related

• Integrations — configure carrier credentials, billing/entitlement
• Webhooks — outbound order and product events (Feeef → your server)
• API conventions — errors, pagination, batch envelopes