Unified Services API reference
This is the complete API reference for the Nets Unified Services API.
Environments and base addresses
All communication between your site and Nets Unified Services is managed over HTTPS. The Unified Services REST APIs are collected under the following base addresses:
| Environment | Base address |
|---|---|
| Test | https://sandbox.unifiedapi.nets.eu |
| Live | https://unifiedapi.nets.eu |
Paths
Unified Services provides the following APIs:
| API | Path |
|---|---|
| Payment | /api/v1/Payments |
| Tokenization | /api/v1/Tokens |
Requests and responses
The Nets Unified Services APIs follow the RESTful architectural style. A set of resources can be accessed using some of the endpoints provided by the APIs. To retrieve, add, or update resources, you use the associated HTTP methods for these actions:
| Method | Description |
|---|---|
| GET | Retrieves a resource (idempotent, will never mutate a resource) |
| POST | Creates a new resource. A JSON object, provided by you, describes the resource. |
| PUT | Updates an existing resource. A JSON object, provided by you, describes the changes. |
Parameters
You can pass parameters to the Unified Services APIs using:
- Header parameters. For example, the
Authorizationheader specifying the private API key is always sent as an HTTP header. - Path parameters. For example, the numerical payment identifier
paymentIdin the path/v1/payment/{paymentId}. - JSON objects. Some requests, typically POST and PUT, expect you to pass JSON objects to the Unified Services APIs (as a request body).