Back to Clid Cloud
60 SECONDS · NO EXPERIENCE NEEDED

Get started with Clid Cloud

You're three steps away from running your first Clid API call. No setup wizards, no config files, no scopes to pick. Ready?

1Make sure you're signed in

Sign in to your Clid account

If you don't have one yet, it takes 10 seconds — just an email, no password. We'll send you a one-time code to sign in, and you can set up a passkey later if you want to skip the code next time.

Already signed in? Skip to step 2. You can check by looking at the top-right of the Clid Cloud dashboard. If you see your email there, you're good.
Open the Clid Cloud dashboard
2Make an API key

Create your first API key

An API key is a long password that lets your code talk to Clid. One key does everything — buckets, databases, email, all of it. You only have to make one.

Where to click In the dashboard, go to Developer in the sidebar → Clid Auth → click the API keys tab → click "Create API key".

Give it a name (anything — "My first key", "Test", whatever helps you remember). Then click Create key. You'll see a long string that starts with clidkey_. Copy it right then — you won't see it again.

Don't lose it. If you close the window without copying, you'll need to delete that key and make a new one. We don't store the key — only a hash of it — so we can't show it to you again.
3Run your first call

Try it right here

Paste your API key below and click "Run it". We'll call the Clid Cloud API and show you what comes back. This is the exact same call your code will make.

Or, in your own terminal (this is what your code will look like):

curl — list your buckets 
curl https://cloud.zylinkcorp.com.ng/api/cloud/buckets \
  -H "Authorization: Bearer YOUR_API_KEY"

You should see a JSON response with your buckets (probably empty if you just signed up):

Response
{
  "buckets": []
}
That's it. You're a Clid developer now. The same key works for every other Clid API — databases, email, domains, all of it. Just change the URL. The Authorization header stays the same.

What's next?