Client ID and client secret can be passed as x-www-url-encoded params or as basic auth base64(client_id:client_secret).
curl --location --request POST 'https://auth-dev.bikeep.com/oauth2/token' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials' \
--data-urlencode 'client_id=INSERT_ID_HERE' \
--data-urlencode 'client_secret=INSERT_SECRET_HERE'
curl --location --request POST 'https://auth-dev.bikeep.com/oauth2/token' \
--header 'Authorization: Basic INSERT_BASE64_HERE' \
--header 'Content-Type: application/x-www-form-urlencoded' \
--data-urlencode 'grant_type=client_credentials'
Bikeep API provides the functionality to get locations, control devices and query sessions that are initiated from controlling the devices. API can be accessed in two ways - authenticating your users through Bikeep (see 'External users') or using your server as proxy to all requests (service-to-service authentication user Oauth2 client credentials flow).
Client credentials and operator IDs will be provided for you by Bikeep. Contact us if want to request API credentials, and we can figure out which one best suits your needs; or if you have any additional questions/suggestions regarding the API documentation.