Getting started
Nexta API is using HTTP 1.1 as communication protocol & JSON as data-exchange format. All dates used in endpoints are presented in ISO 8601 format, most values are using UTC as time zone.
Base path to the API is: https://api.nexta.io/NextAdvertising.V3
Path to the OpenAPI Specification: https://api.nexta.io/NextAdvertising.V3/swagger/index.html
Public Nexta microservices are available via REST API that is located behind a gateway. Requests made to any Nexta endpoint are first received on the gateway and then processed differently depending on the type of the service receiving the request.
There are 2 types of services in Nexta:
- Synchronous services: Requests are passed directly to the services as HTTP requests from the gateway. Synchronous services return the result of the operation straight away.
- Asynchronous services: Requests are first received on the gateway, and then the message is emitted to a queue that a specified service listens to. The message is subsequently processed by the microservice. In case of errors, the message ends up in the error queue, and therefore nothing gets lost. Asynchronous services will always return a successful response if the request is valid. After this, the API consumer needs to keep polling to get the status of the asynchronous process being executed on the background.