The Melbicom API lets your own scripts read your account and act on it: list services, watch invoices and credit, pull domain pricing, purge CDN caches. This page is the working summary: where the API lives, how requests authenticate, and what every endpoint does. Full request and response schemas are in the API documentation.
Basics
| Property | Value |
|---|---|
| Base URL | https://api01.melbicom.net/api |
| Authentication | A private access token in the request header: Authorization: Bearer YOUR_TOKEN. |
| Token scope | Full read and write access to the account; no per-endpoint scopes. Restrict the token by IP and rotate it. |
| Format | JSON requests and responses; write requests send Content-Type: application/json. |
| Rate limiting | Requests over the limit receive 429; reduce the request rate and retry after a pause. |
Tokens are created and managed in the client area: Create Your Melbicom API Token covers creation and the first call, and Secure and Manage Your Melbicom API Token covers IP restriction and rotation.
Endpoints
| Endpoint | What it does |
|---|---|
GET /version |
Returns the API version. The natural first call for verifying a token. |
GET /productgroups |
Lists the product groups available to order. |
GET /products |
Lists products with their configuration and pricing. |
GET /services |
Lists your services with id, product name, status, usage and billing dates. The id is what the per-service endpoints take. |
GET /services/{id} |
Returns one service in detail. |
POST /services/{id}/resources/purge-cache |
Purges a CDN resource’s cache: the whole resource, one path, or a folder (path ending in /). |
GET /domain/tlds |
Returns domain pricing per TLD. |
GET /billing/invoices |
Lists your invoices with number, dates, totals and status. |
GET /billing/creditbalance |
Returns the account’s credit balance and its currency. |
Two recipes build on these endpoints: Purge Your CDN Cache from Your Deploy Pipeline automates the purge call from CI, and Monitor Invoices and Credit Balance with the Melbicom API turns the two billing endpoints into a scheduled watcher.
Every endpoint authenticates the same way. A quick template for any of them:
curl -H "Authorization: Bearer YOUR_TOKEN" https://api01.melbicom.net/api/services