US English (US)
GB English (UK)

By Appointment to
His Majesty The King
Contact Centre Service Software
Cirrus Response Ltd
Epsom

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Cirrus eLearning
  • Contact Us
English (UK)
US English (US)
GB English (UK)
  • Home
  • Cirrus Digital
  • API Documentation

Cirrus Digital REST APIs

Written by Keith Winhall

Updated at January 7th, 2025

Contact Us

If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.

Please fill out the contact form below and we will reply as soon as possible.

  • Cirrus Connect
    Agent Supervisor Administrator
  • Cirrus Digital
    Agents Supervisors Administrators API Documentation
  • Release Notes
    Release FAQs Latest Release 2025 2024 2023
  • Customer Billing
+ More

Table of Contents

Overview Structure and Examples Access Token Base URI Request Response Possible Response Status Codes

Overview

Cirrus utilizes the REST APIs principles, allowing developers to perform queries to the Cirrus platform. We support GET, POST, and DELETE requests. Use a Get request to retrieve information, a POST to create or update an entity, and a DELETE to remove an entity.
After receiving the request, the API sends back an HTTP code as a response in JSON format.

Structure and Examples

Access Token

All API requests require an Access Token to validate authenticity to indicate to the system what modules, operations, and resources the user can access. See more detailed information in the Security and Authentication section of this documentation.

Base URI

All URLs referenced in the documentation have the following base: https://api.commbox.io

Request

  • The request must include the module and operation in the URI.
    For example, to access an operation called SystemStatus in the Core module, make an HTTP request to –
    /Core/SystemStatus
  • To receive specific information regarding a resource, use the provided parameters in the URI.
    For example, to access a specific user data in the Core module, make an HTTP GET request to –
    /Users/{USER_ID}/Details
  • To change a resource, use an HTTP POST request to the resource URI.
    For example, to change a specific user name in the Core module, make an HTTP POST request to –
    POST /Users/{USER_ID}/Details
    And include the post parameter
    data={"FirstName":"FIRSTNAME", "LastName":"LASTNAME"}
  • To delete a resource, use an HTTP DELETE request to the resource URI.
    For example, to change a specific user name in the Core module, make an HTTP DELETE request to –
    DELETE /Users/{USER_ID}/

Response

Property Description
status The HTTP status code for the response
description A more informative message
response_time UTC Timestamp for the operation
data (Optional) Additional output data, varies by operation

Possible Response Status Codes

Status Code Description Notes
200 OK The request was successful
400 Bad Request The request could not be understood by the server. Incoming parameters might not be valid
401 Unauthorized The supplied credentials, if any, are not sufficient to access the resource
404 Not Found The requested resource is not found
429 Too Many Requests Too many requests have been made in a short period of time (Throttling)
500 Server Error The server could not return the representation due to an internal server error
501 Not Implemented The requested operation is not supported (e.g. supports GET but not POST etc.)

Was this article helpful?

Yes
No
Give feedback about this article

Related Articles

  • Digital User Provisioning

Cirrus
Office 126
63 St Mary Axe
London, EC3A 8AA
Tel: 0333 103 3333
Email: cm@cirrusconnects.com

Social: twitter linkedin

Privacy Policy

Postal address
Cirrus
PO Box 708
Epsom, KT17 9RA
Tel: 0333 103 3333
Email: support@cirrusconnects.com

© Copyright Cirrus


Knowledge Base Software powered by Helpjuice

Expand