Go from zero to a live API call against the Openprovider REST API.
You need an active reseller account. Sign in to the Control Panel — or create one — to obtain your username and password.
Open Control Panel →Send your credentials to the /auth/login endpoint. The response returns a token you’ll use to authorize every subsequent request.
curl -X POST https://api.openprovider.eu/v1beta/auth/login \
-H 'Content-Type: application/json' \
-d '{
"username": "you@example.com",
"password": "your-password",
"ip": "0.0.0.0"
}'The token is returned in data.token and is valid for a limited time. Cache it and re-use it across requests rather than logging in on every call.
Pass the token in the Authorization header as a bearer token. Here we check whether a domain is available:
curl -X POST https://api.openprovider.eu/v1beta/domains/check \
-H 'Authorization: Bearer YOUR_TOKEN' \
-H 'Content-Type: application/json' \
-d '{
"domains": [{ "name": "mybrand", "extension": "com" }]
}'Browse every endpoint, request schema, and response example in the interactive documentation — or import the OpenAPI spec into Postman.
| Item | Value |
|---|---|
| Base URL | https://api.openprovider.eu/v1beta |
| Protocol | HTTPS only |
| Format | JSON request & response bodies |
| Authentication | Authorization: Bearer <token> |
| Methods | GET, POST, PUT, DELETE |
Successful responses wrap the payload in a predictable envelope with a numeric code (0 indicates success) and a data object:
{
"code": 0,
"data": { /* result */ },
"desc": ""
}A non-zero code indicates an error. Inspect desc for a human-readable message and handle failures gracefully in your integration.