Skip to main content
Create and manage Moove Payment Links programmatically.
The API is live and serving production traffic. Base URL https://api.moove.xyz.

Quickstart

1

Create an API key

At moove.xyz/dashboard/api-keys, scoped to the Moove Receive Agent. The plaintext key is shown once.Moove API Keys →
2

Create a payment link

Response
3

Send the payer to `url`

They pay in any token on any chain. It settles to your default wallet in your settlement token.

At a glance

Endpoints

Before your first call

The API refuses to create links for an account that cannot receive payments. Make sure the key owner has: Without both, POST /v1/payment-link returns 409.

What the API cannot do

No endpoint moves funds. A payment link always settles to the authenticated user’s own default wallet, in that wallet’s chain and token. The caller cannot specify a destination.A key is a down-scope of its owner: it acts as that user and can only do a subset of what they can do. A leaked key can request payments that pay its owner — it cannot redirect money elsewhere.
There is also no key-minting endpoint. Key management is session-authenticated only, so a key can never issue another key.

Coming soon

Moove Send, Moove Swap, Moove Bridge, Moove Stake and Moove Ramp have no public API yet. The pages under Coming Soon track what is planned.

Next

Authentication

Keys, scopes and the header.

Moove Payment Links

Both endpoints in full.

Errors

Status codes and retry behaviour.