Developer overview
If you're integrating the Merchant Dashboard with your own systems — pulling transactions into your ERP, automating refunds, reacting to payments in real time — this section is for you.
Section pending detail
Once you confirm the API basics (REST/GraphQL, auth, base URL, OpenAPI spec) I'll fill in this overview with concrete examples and links to the right reference material.
What you can do
- Read account data with the API: transactions, invoices, customers, payouts.
- React to events with webhooks: get notified the moment a payment succeeds, an invoice is paid, etc.
- Authenticate with API keys you create and manage from Connect.
Where things live in the dashboard
The developer-facing controls are grouped under Connect in the left navigation.
| Surface | Used for |
|---|---|
| API keys | Create, rotate, revoke keys |
| Webhooks | Register and monitor endpoints |
| Connect | Top-level hub for the above |
API basics
Confirm
- Protocol: REST? GraphQL? Both?
- Base URL(s) for production and development.
- Auth: API key in
Authorization: Bearer …? Other? - Versioning: URL prefix (
/v1/)? Header? - OpenAPI / Swagger spec available?
- Rate limits.
- Pagination convention.
SDKs
Confirm
Are there official client libraries (Node, Python, PHP, Ruby, Go)? If yes, link them. If no, say "no official SDKs — call the API directly".