Dots API is designed for easy integration with your internal systems, such as HR, or procurement tools, so you can automate visibility into who owns what within your organization.
Currently, the API includes two main endpoints:
Get Employee Details – Retrieve employee data using their email address. The response also includes all assets currently assigned to that employee.
Get Asset Details – Retrieve detailed information about a specific asset, including model, serial number, purchase date, and assignment status.
All requests require an API key that can be generated from your Client Dashboard → Tab Settings → API Access section.
The key must be passed in the request header:
authorization: YOUR_API_KEY
This API is READ-ONLY and returns structured JSON responses, making it simple to connect with your internal dashboards, inventory systems, or reporting tools.
Authentication & Example Requests
Get Employee Details
Endpoint:
GET https://dots-public-api.dotstech.com/api/v1/company-staff?email=EMPLOYEE_EMAIL
Description:
Retrieves information about an employee by their email address and lists all assets currently assigned to that employee.
Get Asset Details
Endpoint:
https://dots-public-api.dotstech.com /api/v1/asset/ASSET_ID
Description:
Returns detailed information about a specific asset.
Error Handling & Rate Limits
All API responses include a “success” field and return standard HTTP status codes.
If a request fails, the response will contain a clear “message” explaining what went wrong.
For example:
Error Response Format
Example:
success: false
message: Invalid API key
Common HTTP Status Codes
200 – OK
Request completed successfully.
400 – Bad Request
Missing or invalid parameter (for example, missing “email”).
401 – Unauthorized
Invalid or missing x-api-key header.
404 – Not Found
Employee or asset not found.
429 – Too Many Requests
Rate limit exceeded — wait and retry later.
500 – Internal Server Error
Unexpected error on the server side.
Rate Limits
To ensure stable performance, the API enforces per-minute and per-day limits for each organization.
If you exceed these limits, you will receive HTTP 429 Too Many Requests.
Rate limit information is also included in each response header:
x-ratelimit-limit-day – maximum number of requests allowed per day
x-ratelimit-limit-minute – maximum number of requests allowed per minute
x-ratelimit-remaining-day – how many requests remain for the current day
x-ratelimit-remaining-minute – how many requests remain for the current minute
x-ratelimit-reset-day – timestamp when the daily limit resets
Tip: Use these headers to monitor your usage and prevent rate limit errors. If your integration sends many requests, add retry logic that waits until reset before sending more.
If you have any questions please reach our support - support@dotstech.com