Skip to main content
By the end of this page you will have made an authenticated call to the StableMint API. Start here before writing any integration code — if your signing implementation is wrong, every other call fails the same way, and it is much easier to debug against a GET with no body.

What you need

1

Sandbox access

A sandbox partner account and a dashboard login. See Sandbox.
2

An RSA key pair

Generate one and upload the public half when you create a service account:
3

A service account

Create one in the Developer Hub, register stablemint-public.pem, and note the API key and API secret. Grant it permission to read transactions so it can do something once it authenticates. See Service accounts.

Make the call

Set your credentials:
Then sign and send a request for your accounts:
A 200 means your signing is correct and you can move on. Anything else is worth fixing now.

If it did not work

One of the four headers is missing or empty. Check that STABLEMINT_API_KEY is actually set — an unset variable expands to an empty header, which counts as missing.
Something added an Authorization header. The public API takes signed requests only.
The signature did not verify. The two most common causes are a canonical string joined with literal \n characters instead of real line feeds, and a clock more than 60 seconds out of step. Check both before looking anywhere else.

Next

Authentication

The full signing contract, including bodies and query strings.

Sandbox

Simulate a deposit and watch it mint.