Download OpenAPI specification:Download
This is the reference documentation for the V2 Zubie API. Zubie customers on a Premium plan can access the full API for their account using an encrypted API Key. Third-party developers with apps registered in the ZinC Developer platform will have access a restricted set of API's using Oauth authentication. If you are a developer, visit the ZinC Developer Portal for information on setting up apps and using Oath authentication.
For support, contact us at support@zubie.com.
https://api.zubiecar.com/api/v2/zinc
.Zubie Customers The Zubie API uses an encrypted API Key to provide account-level API accesss, added to the header of every request.
Zubie-Api-Key: {api key}
To generate an API Key, contact us.
Third Party Developers You must first register an app via the ZinC developer platform. Once registered, you are granted a client id and key that can be used through an Oauth authentication exchange to generate a token on behalf of a Zubie user. The client token is added in the Authorization header. Note that third party apps default to read-only scope for a limited set of endpoints.
Authorization: Bearer {oauth token}
Note that Zubie adds new properties from time to time as new features are released without an API version change. We do not recommend using the API docs to perform schema validation.
Zubie uses standard HTTP response codes to indicate success or failure of an API request.
Responses | Description |
---|---|
200 - OK | A GET request succeeded. JSON dictionary response. |
201 - Created | A POST response succeeded. JSON dictionary response. |
400 - Bad Request | The request was unacceptable, often due to missing a required parameter. JSON dictionary response { "errors": "This was a bad request because..." } |
401 - Unauthorized | No valid API key provided. Empty body. |
403 - Forbidden | The requested action is restricted based on your account profile. Empty body. |
404 - Not Found | The requested resource doesn't exist. Empty body. |
500, 502, 503 | Something is wrong on the Zubie side. |
Many endpoints that return large lists of results are paginated. In instances where the number of results exceeds the size parameter (per-endpoint default, or optionally specified with the request), a cursor value is included in the response. Callers may repeat the request, including the original query parameters, with the addition of the cursor parameter, to retrieve the next set of results. Once all results have been returned, the cursor will be omitted from the last response.
Query Parameters
Response Data
The response will be a dictionary containing the account’s data.
Successful.
Update account-wide settings.
nickname | string The account name, i.e. the business name. |
external_id | string An optional, external id string associated with the account. |
street | string The street address for the account. |
city | string The city for the account. |
state | string The street address for the account. |
zipcode | string The zipcode for the account. |
Successful update.
Lists the subscriptions associated with the account. All devices with the same plan will be grouped under the same subscription.
cursor | string The cursor string used for pagination, signifying the object ID where to start the results. |
size | string The number of results to return per call. Defaults to 100 if not provided. |
Successful.
Lists all active and pending devices (vehicle connected hardware) in account.
q | string Search devices by serial. |
cursor | string The cursor string used for pagination, signifying the object ID where to start the results. |
size | string The number of results to return per call. Defaults to 50 if not provided. |
Successful.
key required | string Unique device key. |
Successful.
Update a Device subscription status.
key required | string Unique device key. |
subscription_status | string Specify value |
Successful update.
Lists groups available in the account, based on the group permissions of the user. Groups are a way to provide hierarchical structure to account vehicles and restrict user permissions.
group_keys | Array of string Optional list of group_keys (as repeated parameters) to further filter results, only includes those groups and below. Multiple tag values may be provided. (e.g. “?group_keys=foo&group_keys=bar”). |
show_inactive | boolean Optional boolean, defaults False. Whether to include deactivated groups in hierarchy response. |
Successful.
Create a new group.
name | string |
parent_group_key | string The key of the parent group. If omitted, will use the account as parent, for a level 2 node. Parent group must be active. |
Successfully created.
group_key required | string Unique group key |
Successful.