REST API and Webhooks

What is this?

Clue has a comprehensive REST API with 300+ endpoints. If you need to pull data into a BI tool, push information from another system, or build custom automations, the API gives you full access to your fleet data.

Who is this for?

• IT Teams - Build integrations between Clue and your other business systems.
• Data Analysts - Pull equipment, cost, and utilization data into Power BI, Tableau, or custom dashboards.
• Developers - Build custom workflows, mobile apps, or third-party integrations.

Getting started

Step 1: Get an API token

Go to Company Settings > Permissions > API Tokens. Create a new token. This is your authentication key for all API calls.

Step 2: Explore the documentation

Full interactive API documentation is available at public.getclue.com/v1/swagger-ui. You can browse every endpoint, see request/response formats, and test calls directly from the browser.

Step 3: Make your first call

All endpoints follow standard REST conventions. JSON request and response bodies. Bearer token authentication. Paginated results for large datasets.

Webhooks

Instead of polling the API for changes, you can set up webhooks. Clue sends a POST request to your URL when specific events happen (work order created, inspection completed, asset updated, etc.).

Configure webhooks in Company Settings > Permissions > Webhooks.

The full details

• 300+ endpoints covering equipment, work orders, inspections, parts, timecards, projects, and more
• No extra licensing fees. API access is included in your plan.
• Rate limiting: Standard rate limits apply to prevent abuse. Contact support if you need higher limits.
• Authentication: Bearer token via API Tokens page. No OAuth setup needed.
• Interactive docs: public.getclue.com/v1/swagger-ui

Tips

• Use webhooks instead of polling. If you need to react to events (new WO, completed inspection), webhooks are faster and more efficient than checking the API every minute.
• Start with the Swagger UI. Test your queries in the browser before writing code.
• Use pagination for large datasets. Equipment and work order lists can be thousands of records. Always paginate.