Getting Started
Get up and running with the Nomid MDM API in just a few minutes. This guide will walk you through authentication setup and making your first API call.
Prerequisites
- A Nomid MDM account with administrator access
- Access to the Company Settings in the Portal
- A tool to make HTTP requests (curl, Postman, or your preferred language)
Step 1: Create an API Key
- Log in to the Nomid Portal at portal.nomid.tech
- Navigate to Company Settings > Integrations
- Click 'Create API Key' and give it a descriptive name
- Copy the API key - it will only be shown once!
Step 2: Make Your First Request
Use your API key to authenticate requests. Include it in the X-API-Key header:
curl -X GET "https://api.nomid.tech/emm/api/v1/assets" \
-H "X-API-Key: nm_acme_abc123..." Step 3: Handle the Response
The API returns JSON responses. Here's an example response from the devices endpoint:
{
"content": [{
"pathName": "k3x9m2pa",
"identification": "Warehouse-Scanner-01",
"status": "ACTIVE",
"syncedAt": "2026-01-20T14:22:00Z"
}],
"totalElements": 1,
"totalPages": 1,
"size": 20,
"number": 0
} Responses are paginated. Use the 'page' and 'size' query parameters to navigate through results.
Rate limits
The REST read endpoints do not apply a per-key limit in the Nomid application, but build your client to back off on 429 anyway. The MCP endpoint allows 60 requests per minute per key. Device commands, policy changes (each propose and apply call) and provisioning QR codes share a write limit of 10 per minute per key, across the REST endpoints and the MCP tools. A Sign in with Nomid connection has the same MCP and write limits, counted per connection.
| HTTP | Description |
|---|---|
| Retry-After | Seconds to wait before retrying. Sent with HTTP 429 responses from the MCP endpoint, the REST command endpoints, the policy change endpoints and the provisioning QR code endpoint. |
The API does not send X-RateLimit-Limit, X-RateLimit-Remaining or X-RateLimit-Reset headers.