Public API
The complete reference for every public endpoint, generated from the services' own OpenAPI documents, with a console to call any of them from your browser. JSON over HTTPS, bearer tokens, RFC 7807 problem details on every error.
- Bazinis URLhttps://marketplace-api.paysera.com
- AutentifikacijaBearer prieigos raktas (OAuth 2.0)
- Klaidosapplication/problem+json
- Apimtis7 paslaugos · 297 operacijos
Šis puslapis dar neišverstas — skaitote versiją anglų kalba.
How authentication worksNuoroda į šį skyrių:
Every request carries Authorization: Bearer <token>. Tokens are issued by Paysera Marketplace
sign-in (OAuth 2.0). There are no API keys: an integration authenticates as an agent — a
delegated identity the seller creates and approves from their dashboard, with its own client id and
secret. Each operation below names the capability the agent needs, for example products:read_write.
Create an agent
In the seller dashboard under Team & access → Agents, create an agent for your integration and choose its capabilities.
Copy its credential
You get a client id (
agt_…) and a secret. Store the secret server-side; it can be rotated with a 24-hour overlap.Request a token
Exchange the credential for an access token with the client-credentials grant.
Call the API
Send the token as a bearer. It is short-lived; request a new one when you get 401.
curl -X POST https://marketplace-api.paysera.com/auth/realms/marketplace/protocol/openid-connect/token \
-d grant_type=client_credentials \
-d client_id=agt_7tvsvcagent0001 \
-d client_secret=$AGENT_SECRETTrying things out as yourself? Your own seller sign-in also yields a token (the password grant on the same endpoint). Use it for exploration only; production integrations use an agent so access can be limited and revoked without touching your account.