Quick Start

Get up and running with the Unduit API in minutes. Authenticate with the login endpoint, obtain an access token, and make your first API call.

What you can do

The Unduit API lets you integrate enterprise-grade mobile device management into your platform. Manage repairs, recycling, and buyback services programmatically — employees, assets, orders, recoveries, ticketing, and more are available under /api/v1.

All protected endpoints require a Bearer token. Your first step is always to call POST api/v1/auth/login with your API credentials.

Before you begin

You need an Unduit account with API access and your client_id (email) and client_secret (password). Find these under Settings → API Credentials in the Unduit app, or contact your account manager if API access is not enabled.

Step 1 — Login and get a token

Send a POST request to the login endpoint with your credentials in the JSON body. No Authorization header is required for this call.

POST
/api/v1/auth/login
FieldTypeDescription
client_idstringYour API user email address.
client_secretstringYour API password / client secret.
curl --location 'https://uat.unduit.com/api-exposed/api/v1/auth/login' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "client_id": "your-email@example.com",
    "client_secret": "your-client-secret"
  }'

Response

On success you receive a JWT access token valid for 4 hours. Store the token value securely — use it as a Bearer token on all subsequent requests.

{
  "message": "Login successful",
  "token": "YOUR_ACCESS_TOKEN_HERE"
}

Step 2 — Make your first API call

Pass the token from Step 1 in the Authorization header. This example lists employees in your organization:

GET
/api/v1/employees?page=1&limit=10
curl -X GET 'https://uat.unduit.com/api-exposed/api/v1/employees?page=1&limit=10' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Content-Type: application/json'

What's next

Tokens expire after 4 hours. Use the refresh-token endpoint to obtain a new token without re-entering credentials. See the guides below for full authentication details, base URL environments, and API conventions.