Partners

Partners are one and the same for both directions. There is no list for outbound and another for inbound: one company is one record, and both paths use it.

That is not internal tidiness — it is the real order of things. An inbound invoice arrives without you having any code for that company, because the sender chose you, not the other way round. So the partner exists in eArhiva.mk before it exists in your software.

Registration happens on its own

A recipient or a sender that is not registered is registered from the document itself — from the name, tax number and address the document carries — and the processing goes on.

Direction	Who gets registered	When
outbound invoice	the recipient	while resolving the recipient, before submission to UJP
inbound invoice	the sender	when the document is received

⛔ You do not have to register anything beforehand to send your first invoice. Until now a document for an unregistered recipient ended at 250 with EARH-4005 — the usual outcome of a first attempt for every new integrator.

⚠️ Registration does not overwrite existing data. It fills in only what is empty: a partner registered by hand with an e-mail address and an exact name keeps its own, and what it was missing is filled in from the document.

Pulling the list into your software — `GET /partners`

GET /api/integration/v1/partners?changedSince=2026-09-01&page=1&pageSize=200

The answer carries items, totalCount and nextFrom:

{
  "items": [
    {
      "edb": "4002002113498",
      "name": "Alkaloid AD Skopje",
      "address": "bul. Aleksandar Makedonski 12",
      "city": "Skopje",
      "postalCode": "1000",
      "country": "MK",
      "email": "info@alkaloid.com.mk",
      "origin": "Unknown",
      "changedAt": "2026-07-06T23:50:11.001807"
    }
  ],
  "totalCount": 13,
  "nextFrom": "2026-07-06T23:50:11.001807"
}

Field	What it is
`edb`	the tax number as it is stored — with or without the `MK` prefix. Normalize before comparing: `MK4030995155258` and `4030995155258` are the same taxpayer
`origin`	where the record came from — `OutboundInvoice`, `InboundInvoice`, `Manual`, `Erp`, or `Unknown` for a record older than the field itself
`changedAt`	the last change to the record; the ordering follows it

Incrementally, not the whole list

changedSince returns only what changed, and nextFrom in the answer is the starting point for the next call — the same pattern as on the document lists.

GET /api/integration/v1/partners?changedSince=2026-07-06T23:50:11.001807

changedSince takes a calendar date (yyyy-MM-dd) or a full timestamp. ⛔ It is read strictly as ISO: 10.09.2026 is refused with EARH-2020, not interpreted as 10 September.

Paging is page and pageSize. The largest allowed page is 500; a larger one is refused with EARH-3005, and the answer carries the allowed value.