Skip to main content
The RABOT Partner API uses OAuth 2.0 for authentication (see RFC 7649). Using the OAuth client credentials flow, you can obtain an access token from the RABOT authentication server.

​
Token Request

replace CLIENT_ID and CLIENT_SECRET with the credentials you received from Rabot Charge. See Partner setup
Example API request
curl -L "auth.rabot-charge.de/connect/token" \
-H "Content-Type: application/x-www-form-urlencoded" \
-d "client_id={{CLIENT_ID}}" \
-d "client_secret={{CLIENT_SECRET}}" \
-d "grant_type=client_credentials" \
-d "scope=api:partner"

​
Scopes

You need to specify, which scopes you want to include in the token by specifying them in scope parameter. Multiple scopes should be separated by a space. The following scopes are available for Whitelabel Partners:
ScopeDescription
api:partnerpermission to access Partner API, required for all API requests
create:orderspermission to create orders
role:finance-reportingpermission to access customer and contract data, limited to finance reporting related information
role:customer-supportpermission to access customer and contract data, limited to customer support related information (includes role: finance-reporting)
role:applicationpermission to access all customer and contract data (includes role: finance-reporting and role:customer-support )
The following scopes are available for HEMS / 3rd Party Partners:
ScopeDescription
api:partnerpermission to access Partner API, required for all API requests
In order to access further customer or contract specific information e.g. Working Price via the metrics endpoint, you will need to integrate the 3rd Party Authorization flow.Once the RABOT customer has authorized the data exchange between our platforms, you will be able to access all endpoint under the /customers path.
The following scopes are available for Sales Affilliate Partners:
ScopeDescription
api:partnerpermission to access Partner API, required for all API requests
create:orderspermission to create orders
role:finance-reportingpermission to access customer and contract data, limited to finance reporting related information
To use scopes, you need to have them assigned to your API client by RABOT administrators. If you feel you should have a scope, that you don’t have, please contact our Integration Management team.

​
Token Response

If successful, the authentication server responds with a HTTP/200 status code, and the response body contains a structure with the access token 
{
  "access_token": "eyJhbGciOiJS....QnkY36d_ac",
  "token_type": "Bearer",
  "expires_in": 3599
}
In all requests to the partner API, include the access token as Bearer token in the HTTP authorization header:
Example API request
curl -L "https://api.rabot-charge.de/partner/v1/tariffs" \
-H "Authorization: Bearer eyJhbGciOiJS....QnkY36d_ac"
Note that the token only has a limited life time; when the life time has expired, you will need to request a new token from the authentication server.