Skip to main content
Every Novatrade24 Integration API transaction flows through the same five modules. Each module is a distinct resource (or sub-resource) with its own endpoints, and they share a single compliance rollup that tells you, at any point, whether the transaction is ready for pickup, closed, or blocked on a specific missing artifact.

​
The five modules

1

Buyer / KYC

Upsert a buyer by VAT number. Choose a KYC mode:
  • MARKETPLACE_LED (Mode A, not available yet), You provide KYC data. NT24 stores it and runs VIES validation only. Until Mode A is available, every organization gets 403 for it and allowMarketplaceLedKyc reads false.
  • NT24_LED (Mode B), NT24 runs full verification (iDenfy + AML) and generates a signed KYC profile PDF.
Upload KYC documents, trigger VIES, and optionally generate a buyer-facing self-service invitation so the buyer uploads their own documents via an emailed link. See Buyer onboarding.
2

Order

Register a VIN-based transaction linked to the buyer. Orders carry one or more VINs (single-VIN by default; allowMultiVinOrders gates N-VIN orders). Each order gets an UUID and your externalOrderId is the natural key for idempotent upsert.VIN is not globally unique, the same VIN may appear in multiple orders over time (resale, buyback). Look up orders by VIN with GET /orders?vin={vin}.See Order creation.
3

Invoice

Submit the buyer’s VAT-compliance invoice data and PDF. One VAT security deposit invoice (PRELIMINARY) per order. The final invoice goes to the same operation with type: FINAL once the amounts are settled.See Invoice & Payment.
4

Payment

Submit proof-of-payment data (date, bank amount, cash amount, source IBAN) and the supporting document. That is the whole step — pickup readiness is derived from what you submit, not signalled by a separate call. Recording the payment runs a VIES check on the buyer and, until pickup is recorded, NT24 re-checks the buyer’s VAT number daily. See VIES revalidation.
5

Transport

Confirm pickup and (later) delivery. Both calls are repeatable: a second one with a corrected date replaces the recorded one, and there is no revoke — NT24 records steps that have already happened, so a pickup that happened cannot be reversed.Upload transport documents as you go: TRANSPORT_CMR, TRANSPORT_CMR_DELIVERY, TRANSPORT_PICTURE_OF_TRANSPORT, TRANSPORT_CONFIRMATION_OF_ARRIVAL, and one of CONTACT_ID_CARD / CONTACT_PASSPORT / CONTACT_DRIVERS_LICENSE to identify the driver.See Transport.
6

Compliance rollup

Poll GET /orders/{uuid}/compliance for the rollup, or subscribe to the compliance.status_changed webhook. blockers[] names what each module is still waiting for, and the code on each entry tells you which upload or correction clears it.There is no sixth step. NT24 staff close the order once the artifacts are on file, and the rollup reports that as complianceStatus: VALID.See Compliance rollup.

​
Compliance rollup

GET /orders/{uuid}/compliance returns the authoritative state of every module plus a list of blockers:
This single endpoint is what you poll (or what your webhook handler fetches after compliance.status_changed) to know exactly what’s blocking progress. See Compliance rollup.

​
Two synchronization styles

​
Poll the rollup

Simple, stateless. Poll GET /orders/{uuid}/compliance every 30s for orders in flight. Use If-None-Match with the previous ETag to get 304 Not Modified when nothing changed, cheap.

​
Subscribe to webhooks

Real-time, event-driven. Register a webhook endpoint via POST /v1/webhooks and subscribe to the events you care about. NT24 delivers signed HTTP POSTs on state transitions. See Webhooks setup. Most integrations use both: webhooks for real-time react + polling as a reconciliation fallback.

​
Manual fallback

Everything that can be done via API can also be done in the Novatrade24 web app. API-created orders are visible to your NT24 staff users. Staff edits show up in API responses. Use the web app for exceptional cases the API doesn’t cover. The compliance rollup is the source of truth either way.

​
Next

Buyer onboarding

Start the workflow, create a buyer, run KYC.

Compliance rollup

One call for all five module states, plus what is still missing.