AbsolutePayDocs

Introduction

Everything in the AbsolutePay developer stack — agent skill, SDKs, REST API, webhooks, and sandbox — and how the pieces fit together.

AbsolutePay is a crypto payments API. With one integration you can accept payments from your customers, send payouts to anyone, and reconcile every movement — settled in stablecoins, on the chains you choose.

These docs are for developers integrating an existing AbsolutePay account. If you don't have one yet, sign up in the dashboard first.

Pick your integration path

Three ways in — all hit the same API, so you can mix them freely.

1. Agent skill — fastest with an AI coding agent

If you build with Claude Code, Cursor, or any agent that supports skills, install the official AbsolutePay skill:

npx skills add AbsolutePay/absolutepay-skill

It teaches your coding agent to integrate AbsolutePay end to end — via the SDKs or raw REST — with the guardrails (request signing, webhook verification, idempotency) built in. Tell your agent "add AbsolutePay checkout to this app" and it knows what to do.

Full install

npx skills add installs the skill itself. To also pull the bundled reference files, run npx github:AbsolutePay/absolutepay-skill.

2. Official SDK — Node, Python, or Go

The SDKs sign every request for you, raise typed errors, and handle pagination:

npm install absolutepay
pip install absolutepay
go get github.com/AbsolutePay/absolutepay-go

See SDK setup for configuration and your first call. Every guide in these docs shows Node, Python, Go, and curl side by side.

3. REST API — any language

Plain REST over HTTPS, JSON in and out. The full interactive reference lives at /api. Requests from non-SDK languages are HMAC-signed — the Authentication guide shows the canonical string and a signing helper you can port to any language.

How it fits together

  • Account & workspace — you sign up, create a workspace, and pass verification (KYC/KYB) in the dashboard. A verified workspace is provisioned with its own settlement account.
  • API keys — each workspace issues API keys (ap_test_… and ap_live_…). Every API call authenticates with a key; the key determines the workspace and whether you're in test (sandbox) or live mode. See Authentication.
  • The API — REST over HTTPS. Base URLs:
Production   https://api.absolutepay.io
Sandbox      https://sandbox-api.absolutepay.io
  • Webhooks — the platform tells you the moment anything reaches a terminal state: payment.succeeded / payment.failed, charge.refunded, and payout.settled / payout.partial / payout.failed. Verify each delivery on the raw body and act idempotently on event.id. See Webhooks.

What you can do

Build in the sandbox first

Two ways to test without moving real funds — both mock-backed, both fire the same webhooks as production:

  • Test mode on production — use an ap_test_ key against https://api.absolutepay.io. Same base URL and request shapes as live; only the key prefix changes.
  • The dedicated sandbox — sign up at sandbox.absolutepay.io and point your calls at https://sandbox-api.absolutepay.io. A fully isolated playground where apps are auto-approved (no review wait) and you trigger settlement yourself.

Next steps

Reference

On this page