I'm an integrator
If you are new to GipoNext APIs, here are the core concepts to keep in mind before starting development.
REST APIs
GipoNext APIs are REST APIs and cover a subset of features available in the UI. This documentation clarifies the scope of available functions from the start, so you can align client expectations with realistic outcomes.
APIs are exposed over HTTPS with JSON payloads, following a common market model supported by major languages and frameworks. This lets you integrate quickly with libraries, testing tools, and established practices.
⚠️ Note
Webhooks and other integration channels besides REST APIs are not available.
OAuth
Authentication and authorization use OAuth, a market standard for protecting API access.
In practice:
- you do not manage user passwords in your application;
- you work with securely issued tokens;
- data access is tied to user consent and permissions.
To start with the right flow, see OAuth flows and tokens and Register your application.
Cross-cutting operational rules
APIs follow common technical rules (pagination, traffic limits, TLS, non-breaking evolution). To avoid typical production errors, consult:
Where to continue
- Getting started for the full operational path;
- OAuth flows and tokens for supported flows;
- Entities and operations for resources, permissions, and use cases;
- API reference for endpoint and resource mapping.