VulCode

Apaczka integration through the Web API

Shipment pricing across several couriers, point selection, a label and a batch handover document from your panel. Apaczka signs every request, so the integration is simple but demands precision.

Couriers and shipping
The delivery step of a store checkout: prices of several couriers calculated for the parcel in the cart, the chosen courier and the order summary

From pricing to tracking

The order of Web API v2 calls in a typical shipment. Each step is a separate endpoint.

  1. Service structure

    service_structure/

    Which services, options and point types your account has.

    In the storea courier list for checkout

  2. Pricing

    order_valuation/

    The shipment cost for the chosen services.

    In the storea delivery price at checkout

  3. Order

    order_send/

    The shipment with the parcel data and the point.

    In the storean Apaczka order number

  4. Label

    waybill/:order_id/

    The waybill for printing.

    In the storea parcel label

  5. Handover and tracking

    turn_in/tracking/:waybill_number/

    A batch handover document and the shipment statuses.

    In the storea status on the order

Signing every request

Apaczka uses no session tokens. Every request carries an HMAC signature and an expiry, and the signature is computed from the same data the body carries.

The Apaczka request log in a store panel: the list of Web API v2 requests and the signature details of one of them
The signature of an order_valuation/ request up close: app_id, route, data and expires, the HMAC-SHA256 signature and the validity window
  • Four parts, one string

    The app id, the endpoint name, the JSON data and the expiry, in that order. We build the JSON once, as re-serialising it after signing changes characters.

  • HMAC-SHA256 with the App Secret

    We compute the signature with the App Secret key, which stays in the server settings and never reaches the browser.

  • At most 30 minutes

    The expiry must be in the future and at most 30 minutes ahead. It counts from server time, so we keep the clock synced to the network.

A plugin or an API integration

On popular platforms a ready connection usually does. We write code for custom stores and systems.

Step
The service list
The delivery price at checkout
Ordering the shipment
The label and the handover document
The shipment status
A ready platform connection
WooCommerce, Shoper, Shopify and other platforms on Apaczka's list
The service list

You switch services on in the platform integration's settings.

The delivery price at checkout

The price comes from whatever the platform's ready integration offers.

When the price must be calculated live for each parcel, you need an API integration.

Ordering the shipment

You order the shipment in the Apaczka panel.

The label and the handover document

You download the label and handover document in the Apaczka panel.

The documents live in the Apaczka panel, not on the order in your panel.

The shipment status

You check statuses in the Apaczka panel.

An integration through the Web API
A module in your code, with signatures and error handling
www.apaczka.pl/api/v2/
The service listPOST service_structure/

Services, options and whether a courier pickup is needed, straight from the account.

The delivery price at checkoutPOST order_valuation/

The price for the parcel built at checkout.

The price is calculated live from the weight and dimensions of the products in the cart.

Ordering the shipmentPOST order_send/

The shipment with the parcel data and point, from your panel.

The label and the handover documentPOST waybill/:order_id/

The waybill while packing, and turn_in/ at the end of the day.

Labels and the handover document sit on the order in your panel.

The shipment statusPOST tracking/:waybill_number/

Tracking reaches the order and the client panel.

A ready platform connectionAn integration through the Web API
WhenA ready platform connection: The store runs on WooCommerce, Shoper or Shopify. You handle shipping in the Apaczka panel.An integration through the Web API: The store or warehouse is custom-built. Delivery prices should be calculated live at checkout. Labels and documents should live in your panel.
What we doA ready platform connection: Configure the platform integration. No code needed.An integration through the Web API: A Web API v2 module in your code, with signatures and error handling.

What flows between the store and Apaczka

The store sends shipment data; Apaczka returns prices, documents and statuses.

Your store
Web API v2 endpoint
Apaczka
  1. Your storeThe delivery price at checkout
    ←order_valuation/
    ApaczkaPricing of the services for this parcel
  2. Your storeThe point the customer picks
    ←points/:type
    ApaczkaDispatch and pickup points of a given type
  3. Your storeA packed order
    →order_send/
    ApaczkaA shipment order
  4. Your storeThe label while packing
    ←waybill/:order_id/
    ApaczkaThe waybill for printing
  5. Your storeThe handover document at the end of the day
    ←turn_in/
    ApaczkaA batch handover confirmation as PDF
  6. Your storeThe status on the order
    ←tracking/:waybill_number/
    ApaczkaShipment statuses, checked periodically
Endpoints per the Apaczka Web API v2 documentation, checked on 6 October 2026.

Services and pickup hours

We take the list of services, options and point types from your Apaczka account and the pickup hours from a separate endpoint, so checkout and the dispatch screen always show what you actually have.

Apaczka services at checkout in a store panel: the account's service list, the dispatch type, pickup hours and Web API access
  1. Services from the account, not the code

    service_structure/

    Service and option ids come from this endpoint at every sync, never hard-coded.

  2. A courier possible or required

    service_structure/

    The service structure says whether a courier pickup is possible or required. The dispatch screen depends on it.

  3. Pickup hours

    pickup_hours/

    The hours a courier can pick parcels up come from Apaczka, and the warehouse sees them when dispatching.

Common questions about Apaczka

Answers about delivery prices, labels, picking an aggregator and the quote.

How do you price delivery today?

Tell us what your store runs on and which couriers you use. We will reply within an hour with questions and a quote.