Create and use an API key

Step-by-step guide
  • About 3 minutes
  • 6 steps
  • Growth and Agency
  • Checked 2 Nov 2026
0 of 6 steps done

Before you start

  • You are on Growth or Agency. On other plans the Developer page shows Part of Growth and Agency.
  • Two-factor sign-in is set up if Skylane asks for it - keys cannot be created until it is.
  • Somewhere safe to store the key, such as a password manager or your server's secret settings. Never put it in front-end code.

Steps

  1. Step 1

    Open Developer settings

    Under Settings in the left-hand menu, click Developer.

    Where to find it in Skylane
    1. Settings
    2. Developer
    3. Create a key
  2. Step 2

    Name the key

    In Create a key, type a name into Key name that says where it will be used, for example Zapier production. Names help when you revoke one later.

  3. Step 3

    Click Create key

    Click Create key. You can have up to 5 active keys at once.

    Diagram: on the Developer API keys screen, press Create key.
  4. Step 4

    Copy the key now

    Under Copy your new key now, click Copy key and store it safely. This is the only time Skylane shows the full key - we keep only a fingerprint. Then click I have saved my key.

  5. Step 5

    Call the API

    Send the key in the Authorization header as a Bearer token. Start by checking the key works:

    Check your keyshell
    curl https://skylane-api.moneymasterhq.com/api/v1/me \
      -H "Authorization: Bearer YOUR_API_KEY"
  6. Step 6

    Revoke a key you no longer need

    Under Your keys, click Revoke next to the key, then Yes, revoke. Anything using it stops working straight away.

Good to know

  • Each key can make 60 requests a minute. Calls need no cookies.
  • Errors come back as JSON with a detail message and an error.code you can match on.
  • Each key shows when it was last used, so you can spot keys that are safe to revoke.

Common problems

I lost the key

Skylane cannot show it again. Revoke it and create a new one.

"You have reached the limit of 5 active keys"

Revoke a key you no longer use, then create the new one.

401 Unauthorized

Check the header is exactly Authorization: Bearer followed by the key, with no quotes or spaces at the end, and that the key is not revoked.

429 Too Many Requests

Slow down to 60 requests a minute per key, and wait before retrying.

Still stuck? Contact support

Tell us which step you reached and what you see on screen. A screenshot helps.