01. Overview and Quick Start

Two requests that prove your setup works. Send them in order.

The first needs no credentials at all, so it tells you whether base_url is correct. The second is a fully signed request, so it tells you whether api_key, api_secret and origin are correct. Testing them separately means a failure points at one cause instead of four.

If the first request fails

Your base_url is wrong, or you cannot reach the host. Check the address supplied with your account, and check it starts with https:// and has no trailing slash.

If the second request fails

Read the code field in the response body. It names the exact problem:

`code`	What it means	Fix
`INVALID_API_KEY`	No key matches what you sent	Check `api_key` for stray spaces or a missing `mg_` prefix
`INVALID_ORIGIN`	Your `origin` does not match the domain on the key	Set `origin` to the exact domain you registered, scheme included
`INVALID_TIMESTAMP`	Your computer's clock is off by more than 5 seconds	Turn on automatic time syncing (NTP)
`INVALID_SIGNATURE`	The signature did not verify	Check `api_secret`, including the `mgs_` prefix
`KYC_REQUIRED`	Your identity verification is not approved yet	Finish verification in the web app, then retry. No code change is needed
`API_KEY_DISABLED`	An administrator disabled the key	Contact support

A successful second request means every other endpoint in this collection will work too, because they all share the same signing scheme.

01. Overview and Quick Start

If the first request fails#

If the second request fails#

If the first request fails

If the second request fails