Create Your Melbicom API Token

TUTORIAL

Generate a private access token from the client area: pick an expiry, copy the value shown once, and verify it with your first authenticated request.

A private access token authenticates your own scripts against the Melbicom API: service lists, invoices, credit balance, CDN cache purges. This tutorial creates the token from the client area, from the expiry choice to the first authenticated request.

Prerequisites

  • A Melbicom account with client area access.
  • A terminal with curl, for the verification call.
  • A password manager or secret store for the token value.

Step 1: Open the API Tokens Page

Log in to the client area, open the account menu at the top right and choose API Tokens. Creation, restrictions and deactivation all happen on this one page.

Step 2: Choose an Expiry and Generate

Pick the expiry that matches how often you rotate credentials, then click Generate token. A dated expiry (one year in this example) is the safer habit; No expiry is for setups with their own rotation schedule.

Weigh one fact before generating: the token grants read and write access to everything on your account, so treat it like your account password.

API tokens page with the expiry choice and the Generate token button

Step 3: Copy the Token Now

The new token is displayed exactly once. Copy it and store it in your secret manager before leaving the page. Melbicom stores only a hash, so the value cannot be shown again, in full or in part. If you lose it, you generate a new one; the old value keeps working until you deactivate it.

Newly generated API token revealed once with its copy control

Step 4: Make Your First Call

Verify the token with the version endpoint, replacing YOUR_TOKEN with the value you copied:

curl -H "Authorization: Bearer YOUR_TOKEN" https://api01.melbicom.net/api/version

A JSON response with the current API version confirms the token authenticates. Every other endpoint uses the same header and the same base URL, https://api01.melbicom.net/api.

Back on the API Tokens page, the token now reads Active, with its creation date, expiry and last request:

Active API token card after creation with its expiry and metadata

What You Have

An active token with a one-year expiry, verified with a real request and stored in your secret manager. Before using it in scripts, restrict where it works from and set your rotation routine: both are covered in Secure and Manage Your Melbicom API Token. The full endpoint list is in Melbicom API: Authentication and Endpoints.

Can’t find what you need? Our engineers are available around the clock, from quick fixes to full infrastructure design.