Push orders in over the API

The inbound order API takes JSON, not files. It expects an order that has already been broken into fields: a purchase-order number, a supplier, and a lines array.

That is the whole distinction, and getting it wrong costs an afternoon:

• Your ERP or procurement tool can emit the order as data → this guide.
• What you have is a CSV, XLSX, PDF, or XML/EDI document → send the document instead, so ProcuLink parses it: by email, from an SFTP folder, from S3 or R2, or by hand. Posting a file to this endpoint will not work.

Open Settings → API keys. That tab is where the credential is made — one per integration, so you can revoke one without breaking the rest.

Press + Create key. A Create new key form opens; give it a name that says where it will be used — the field suggests Production integration or Staging webhook — and press Create key.

The key appears once, under Copy your new API key now, and the dialog says so plainly: it cannot be retrieved again after you close it. Copy it into your secret store before you do anything else.

Above the key list, Your ingress endpoint shows the exact URL for your workspace. It ends in your workspace slug — the same slug as your inbound email address:

https://api.proculink.eu/api/ingress/{slug}/orders

Authentication is a header, not a bearer token in the usual Authorization form:

X-ProcuLink-Key: plk_your_key_here

Test the credential on its own, so that a failure later is unambiguous:

curl -i https://api.proculink.eu/api/ingress/{slug}/ping -H "X-ProcuLink-Key: plk_your_key_here"

A small OK payload means the key is valid and belongs to that workspace slug. Do this first — almost every "the API doesn't work" report turns out to be a slug and key that do not belong together.

Now send an actual order. supplierId and at least one line are required; supplierId accepts either the supplier's GUID or its exact name as spelled in your workspace.

curl -X POST https://api.proculink.eu/api/ingress/{slug}/orders \
  -H "X-ProcuLink-Key: plk_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{
    "orderNumber": "PO-10432",
    "orderDate": "2026-07-04",
    "currency": "EUR",
    "supplierId": "Acme Components",
    "lines": [
      {
        "buyerItemCode": "WIDGET-BLUE-M",
        "description": "Blue widget, medium",
        "quantity": 24,
        "unit": "EA",
        "unitPrice": 4.5
      }
    ]
  }'

Two details that cause most of the 400s: quantity and unitPrice are numbers, not strings, and orderDate is an ISO date (YYYY-MM-DD).

A success returns the created order so you can log it:

{ "id": "6f2a1c9e-1b7a-4d0e-9f3a-2c5b8e0a1d44", "status": "needs_review", "linesCount": 1 }

Automation platforms deliver at-least-once. Sooner or later the same order arrives twice, and you do not want two purchase orders going to the supplier.

Send an Idempotency-Key header with a value that is stable for that order — your own order id is ideal:

Idempotency-Key: erp-order-88213

A repeat within 24 hours returns the original order, marked idempotentReplay: true, instead of creating a second one. If you omit the header entirely, ProcuLink still derives a key from the slug, the PO number, and the line shape, so a verbatim retry is de-duplicated — but an explicit key is better, because it survives a retry that changes an unimportant field.

Neither tool needs a dedicated ProcuLink app — the generic Webhooks action does it:

• Method POST, URL https://api.proculink.eu/api/ingress/{slug}/orders
• Header X-ProcuLink-Key with your key
• Header Idempotency-Key mapped to the trigger's own record id
• The JSON body from step 4 as the raw payload, with your trigger's fields mapped into orderNumber, supplierId, and each line

A 2xx from this endpoint means ProcuLink accepted and stored the order. It does not mean a supplier accepted anything — the order still goes through review and delivery like any other, and delivery reports its own separate result.

So after the first few automated orders, check the Inbox rather than your integration's logs:

• Orders appear with the right purchase-order numbers and line counts.
• Nothing is piling up unreviewed. If lines routinely need fixing, the supplier's catalog is probably missing — see import a supplier catalog.