Skip to main content
The Proceeds REST API lets you manage your services and paywalls programmatically, and read your transactions and events. It’s organized around REST: resource-oriented URLs, JSON request and response bodies, and standard HTTP status codes. This is the management API. It is distinct from the payment URLs your paywalls expose to buyers — see the callout below.

Base URL

All endpoints live under the /v1 path, for example GET /v1/services.

Authentication

Every endpoint except the unauthenticated health check requires an API key generated from your dashboard, sent as a header. See Authentication for key format, header options, and scopes.

Response envelope

Successful responses wrap the result in a data field alongside a meta object:
List endpoints add pagination to meta:

Conventions

The REST API documents management endpoints under api.myproceeds.xyz. The payment URLs your buyers call (myproceeds.xyz/api/x402/pay/... and /api/mpp/pay/...) follow the x402 and MPP standards instead — see Payment URLs.

Next steps

Authentication

Create an API key, choose a header, and scope it correctly.

Errors & rate limits

Error codes, the response shape, and the 1000 req/min limit.