Knowledge Base

Check for answers to your questions by searching by keywords, or check categories below.

Getting started with Openprovider API

Follow

Who is Openprovider

Openprovider is a wholesaler of Internet services and products with a unique platform from which you can find and manage all the products you need: Domains, new gTLDs, SSL certificates, licenses for Plesk and Virtuozzo, spam filters, and more! 

Getting started

Openprovider API gives access to the entire Openprovider infrastructure via a standardised interface based on OpenAPI Specification. With the help of Openprovider's API, you can do just about anything you can do in Reseller Control Panel.

The Openprovider API is a RESTful API based on HTTPS requests and JSON responses. If you have your Openprovider account, you can obtain your API authentication token via the following endpoint:

POST https://api.openprovider.eu/v1beta/auth/login

Endpoints

Openprovider API is accessed by making HTTPS requests to a specific version endpoint URL, in which GET, POST, PUT, and DELETE methods dictate how your interact with the available data. Every endpoint is accessed only via the SSL-enabled HTTPS (port 443) protocol.

Be noted that in order to maintain compatibility in the future, all requests must specify an API version, which is appended to the URL. The latest version is v1beta and the base URL for this version's endpoint is:

https://api.openprovider.eu/v1beta/

Test environment

Aside from our production environment we maintain a separate environment for testing called CTE. CTE API calls must use the api.cte.openprovider.eu domain.

Authentication

At its current state Openprovider API only supports Bearer Authentication which involves acquiring security tokens that are then passed in a request. This token must be sent in the Authorization header when making requests to protected resources:

Authorization: Bearer <token>

Bearer authentication

curl -X POST \
https://api.openprovider.eu/v1beta/auth/login \
-d '{"username": "user", "password": "******", "ip": "0.0.0.0"}'
{
"data": {
"token": "6f6d86377bc******feb75cea76d8e8b",
"reseller_id": 100001
}
}

Responses

All successful responses will be returned as a JSON object with at least one key: data.

The data element will contain either a single JSON object or a list of JSON objects, depending on the endpoint.

{
"data": {
"id": 11195838,
"status": "ACT",
"activation_date": "2019-06-27 04:22:39",
"renewal_date": "2020-06-25 04:22:39",
"expiration_date": "2020-06-27 04:22:39",
"auth_code": "*******"
},
}

 

Was this article helpful?
3 out of 3 found this helpful