Jabra for Developers

Appearance

API Endpoints ​

See API Portal for full API reference

This page describes the most common usage of our API endpoints. The full set of API endpoints and versions is available in the API Portal.

Devices API ​

The Devices API lets you retrieve device inventory, update device settings, and manage firmware versions.

Breaking changes in v2

The latest Devices collection endpoint uses POST with filter fields in a JSON request body.

Previous versions used GET with query parameters.

For new integrations, use API version 2 to align with the current endpoint behavior and filter model.

Basic differences:

  • Method changed from GET to POST
  • Filter and paging inputs moved from query string parameters (for example DeviceClientType, PageSize, ContinuationToken) to JSON body fields (for example deviceClientType, pageSize, continuationToken)

Important filter fields (request body):

  • deviceClientType (enum): Filter by client type, for example personal or meeting-room client usage
  • continuationToken (string): Token for requesting the next page

The complete parameter list is available in the API Portal.

Example: Get Devices using filters

http
POST https://api.cloud.jabra.com/devices/api/devices HTTP/1.1
Cache-Control: no-cache
api-version: 2
Ocp-Apim-Subscription-Key: {your API subscription key}
Content-Type: application/json

{
	"deviceClientType": "MeetingRoom",
	"sortDescending": false,
	"pageSize": 100
}
sh
curl -v -X POST "https://api.cloud.jabra.com/devices/api/devices" -H "Cache-Control: no-cache" -H "api-version: 2" -H "Ocp-Apim-Subscription-Key: {your API subscription key}" -H "Content-Type: application/json" -d '{"deviceClientType":\"MeetingRoom\","sortDescending":false,"pageSize":100}'

Get devices including settings (v2) ​

Version 2 includes an additional operation named Get devices in pages, including their settings.

Use this operation when your integration needs both device inventory and device settings in the same workflow.

This avoids an N+1 request pattern where you first fetch a page of devices and then call device settings for each device individually.

Why this endpoint is useful:

  • Reduces the total number of API calls
  • Improves performance for inventory and configuration views
  • Simplifies synchronization jobs and backend processing

When to use it:

  • You need device settings shown together with each device in your UI
  • You run periodic sync jobs and want fewer round trips
  • You want to lower the risk of hitting rate limits caused by many follow-up settings calls

The request follows the same v2 model of POST plus filter/pagination parameters in the JSON body. See the API Portal for the latest schema and response details.

Meeting Rooms API ​

The Meeting Rooms API can retrieve room details, list meeting rooms using filters, and reboot all Jabra meeting room devices in a room.

Example: Get meeting rooms using filters

http
POST https://api.cloud.jabra.com/meetingrooms/api/meetingrooms HTTP/1.1
Cache-Control: no-cache
api-version: 2
Ocp-Apim-Subscription-Key: {your API subscription key}
Content-Type: application/json

{
	"sortDescending": false,
	"pageSize": 100
}
sh
curl -v -X POST "https://api.cloud.jabra.com/meetingrooms/api/meetingrooms" -H "Cache-Control: no-cache" -H "api-version: 2" -H "Ocp-Apim-Subscription-Key: {your API subscription key}" -H "Content-Type: application/json" -d '{"sortDescending":false,"pageSize":100}'

Example: Retrieve a room

http
GET https://api.cloud.jabra.com/meetingrooms/api/meetingrooms/{groupId of one device in room} HTTP/1.1
Cache-Control: no-cache
api-version: 2
Ocp-Apim-Subscription-Key: {your API subscription key}
sh
curl -v -X GET "https://api.cloud.jabra.com/meetingrooms/api/meetingrooms/{groupId of one device in room}" -H "Cache-Control: no-cache" -H "api-version: 2" -H "Ocp-Apim-Subscription-Key: {your API subscription key}"

Example: Reboot all Jabra meeting room devices in a room

http
POST https://api.cloud.jabra.com/meetingrooms/api/meetingrooms/{groupId of one device in room}/reboot HTTP/1.1
Cache-Control: no-cache
api-version: 2
Ocp-Apim-Subscription-Key: {your API subscription key}
sh
curl -v -X POST "https://api.cloud.jabra.com/meetingrooms/api/meetingrooms/{groupId of one device in room}/reboot" -H "Cache-Control: no-cache" -H "api-version: 2" -H "Ocp-Apim-Subscription-Key: {your API subscription key}"

API versioning ​

Jabra Plus APIs use explicit version headers to control behavior and maintain backward compatibility.

Use the latest API versions from the API Portal for new integrations.

Version header format:

http
api-version: [version-number]

Older versions remain supported during a transition period. Breaking changes are introduced in new versions.

Pagination and continuation tokens ​

When requesting device lists, responses are paged. If more devices are available, a continuation token is returned.

In the latest Devices API, pagination inputs are sent in the request body.

Example: Request next page with continuation token

http
POST https://api.cloud.jabra.com/devices/api/devices HTTP/1.1
Cache-Control: no-cache
api-version: 2
Ocp-Apim-Subscription-Key: {your API subscription key}
Content-Type: application/json

{
	"sortDescending": false,
	"continuationToken": "{your continuation token}",
	"pageSize": 100
}
sh
curl -v -X POST "https://api.cloud.jabra.com/devices/api/devices" -H "Cache-Control: no-cache" -H "api-version: 2" -H "Ocp-Apim-Subscription-Key: {your API subscription key}" -H "Content-Type: application/json" -d '{"sortDescending":false,"continuationToken":\"{your continuation token}\","pageSize":100}'