Versioning
Learn how the Unduit API is versioned and how to target a specific version in your requests.
Current version: v1
All documented endpoints use the v1 path prefix. This is the only API version available today.
Overview
The Unduit API uses URL path versioning. The version is part of every endpoint path — there is no separate version header to send. Include /api/v1 in the base URL for all requests.
Base URL
Prepend your requests with the versioned base URL. Individual endpoint paths in this documentation are shown relative to this base.
https://uat.unduit.com/api-exposedThe live API is served from https://dev-api.unduit.com. All v1 endpoints are under /api/v1.
| Environment | Base URL |
|---|---|
| Production | https://dev-api.unduit.com/api/v1 |
The production API host is dev-api.unduit.com. All v1 endpoints are under /api/v1.
Version in the URL path
Every endpoint path starts with the version segment. For example, listing employees and authenticating both target v1:
| Endpoint | Full path |
|---|---|
| Login | /api/v1/auth/login |
| List employees | /api/v1/employees |
| List tickets | /api/v1/tickets |
Request headers
Version is not passed via a request header. Use the URL path above to select the API version. Authenticated requests still require the standard headers documented on each endpoint page.
| Header | Required | Description |
|---|---|---|
| Content-Type | Yes (for POST/PUT/PATCH) | Set to application/json for JSON request bodies. |
| Authorization | Yes (protected endpoints) | Bearer token from the login or refresh-token endpoints. |
Unduit does not use Accept-Version, X-API-Version, or similar version headers. Sending an unsupported version in the URL path (for example, /api/v2/...) returns a 404 response.
Example request
The version segment appears immediately after the host in the request URL:
curl -X GET 'https://uat.unduit.com/api-exposed/api/v1/employees' \
-H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
-H 'Content-Type: application/json'Supported versions
| Version | Status | Base path |
|---|---|---|
| v1 | Current | /api/v1 |
When additional versions are released, they will be available under new path prefixes (for example, /api/v2). Existing versions remain available for a transition period before any deprecation notice.
Changelog
API changes, new endpoints, and release notes are recorded in the changelog. Review it when integrating or upgrading your integration.
View API changelog