API Reference
Plexy Merchant API.openapi.json.ApiDog endpoints
Plexy Merchant API.openapi.json into ApiDog as an OpenAPI specification. ApiDog will create real endpoint pages with request parameters, request bodies, response schemas, and x-api-key authentication instead of rendering this information as static Markdown tables.Included Endpoints
| Method | Path | Folder | Purpose |
|---|---|---|---|
POST | /v2/paymentMethods | Payment Methods | Get available payment methods for a checkout. |
POST | /v2/payments | Payments | Start a transaction in the Advanced flow. |
POST | /v2/payments/details | Payments | Submit additional payment details, such as 3DS redirect results. |
POST | /v2/sessions | Sessions | Create a payment session for Drop-in or Components. |
GET | /v2/sessions/{sessionId} | Sessions | Get the result of a payment session. |
Base URL
https://api.plexypay.com/v2 prefix, for example /v2/sessions. Use a test x-api-key for simulated transactions and a live APSE x-api-key for production. Do not use a separate sandbox host and do not add live-apse to the /v2/sessions request body.Authentication
ApiKeyAuth security scheme:x-api-key and client SDK clientKey must belong to the same merchant account and mode.Import Steps
Open ApiDog import
In ApiDog, choose OpenAPI import and select the local file
Plexy Merchant API.openapi.json.Import endpoints
Keep the generated folders
Payment Methods, Payments, and Sessions.Set an environment variable
Store the API key as an ApiDog environment variable, then bind it to the
x-api-key auth scheme.Publish with SDK docs
Place the imported endpoint folders under
Server Integration alongside the explanatory Markdown pages.Related Guides
Modified at 2026-07-07 10:25:45