alternative-payments-api-patternslisted

# Alternative Payments API Patterns ## Overview The [Alternative Payments](https://www.alternativepayments.io/) API is a RESTful JSON API for B2B payments: customers, invoices, hosted payment requests, transactions, payouts, and webhooks. This skill covers OAuth2 client-credentials authentication, pagination, rate limiting, and error handling. The WYRE integration exposes a **read + safe-write** surface. It deliberately does **not** implement direct payment creation (`POST /payments`), which would charge a card or bank account. Money movement is out of scope. ## Anti-triggers - **Transaction and payout data** — the transactions resource lives at `GET /payments`, which makes this skill look like the destination; the filters, statuses, and reconciliation workflows are `alternative-payments-payments`. - **Invoice, line-item, and payment-link fields** — use `alternative-payments-invoicing`. ## Base URLs | Environment | Base URL | |-------------|----------| | Production | `https://public-api.alternativepayments.io` | | Demo | `https://public-api.demo.alternativepayments.io` | ## Authentication Alternative Payments uses **OAuth 2.0 client-credentials**. Generate an API key (`client_id` / `client_secret`) in the Partner Dashboard, then exchange it for a short-lived bearer token. **Token request** (HTTP Basic auth, form-encoded body): ```bash curl -s -X POST https://public-api.alternativepayments.io/oauth/token \ -u "${AP_CLIENT_ID}:${AP_CLIENT_SECRET}" \ -H "C