The ServOrbit API, for developers
Today: pricing, domain name availability, WHOIS and the catalog, read-only and with no key. Coming soon: your own account, with an API key.
- Read-only
- No key for public data
- No payments through the API
curl https://api.servorbit.com/pricing
{ "success": true, "data": { … } }The response is JSON. No key is required.
Open today
Public, read-only routes, with no key and no account.
Pricing
Public prices for plans and extensions, the ones the site displays.
Domain name availability
Find out whether a name is free, extension by extension.
WHOIS
The public record of a registered domain name, .ma included, read from its registry when the registry publishes it.
1-Click Apps catalog
Categories and listings of the apps you can install in one click.
Routes that query a registry (availability, WHOIS) are rate-limited per network address: above the limit, the API answers 429 and says when to retry. WHOIS also requires a reCAPTCHA token beyond an hourly volume of lookups not served from cache: a script cannot pass that challenge.
What is coming
Planned, not open yet. We are not announcing a date.
API keys per account
Created in your client area, after two-step verification. You choose what the key can read and when it expires, and you revoke it whenever you want.
Reading your own account
Your services and their due dates, your domains, your DNS zones and your invoices, read-only.
For Reseller (Agency pack) and Builder (VPS) accounts
Open to accounts with an active Agency reseller pack or VPS, end customers and resellers alike; greyed out on Starter. A reseller reads their own account, never their customers' data.
What the API will never do
Whatever the key, this data does not leave through the API.
- Pay, collect payments, or read your payment methods.
- Hand out a domain name's transfer code.
- Show third-party data: domain holders, a reseller's customers.
The documentation
The developer portal describes the public routes, their parameters and their responses.