Code42 API documentation viewers

Overview

API documentation viewers describe the resources and methods provided by the Code42 API. This article describes how to access and use the two API documentation viewers: one for API version 1 (https://<authority-server-address>/apidocviewer), the other for API versions 3 and later (https://<authority-server-address>/swagger). A new version of the API is created whenever there is a breaking change that prevents backward compatibility.

Considerations

The Code42 API documentation viewers are publicly available. You can see them in a browser without signing in. But the API resources themselves only work for you under these conditions:

You have a product plan that includes access to the Code42 API.
Your credentials rely on local authentication. SSO or authentication through any third-party provider will not work.
Your role provides permission to access the data necessary to a given API resource. For example, if you do not have permission to change device settings in the Code42 console, then you don't have permission to change device settings with the API.

If your API calls fail because you do not have permission to use them, you will see reply messages like these:

HTTP 401 Unauthorized
HTTP 401 Could not authenticate user
Your Code42 product plan does not permit use of the Code42 API.

Authentication
Use version 1 and version 4 API resources with either token authentication or name:password authentication. For version 3, however, you must use token authentication. See Code42 API authentication methods for details.

Find API documentation

A authority server hosts two API documentation viewers for several versions of the API.

Version 1

Go to https:/./<authority-server-address>:4285/apidocviewer.

Versions 3 and later

Go to https://<authority-server-address>:4285/swagger and select a version in the API Version menu in the upper-right.

API documentation reference

Version 1

Code42 v1 API documentation viewer

Item		Description
a	Search API	Filters the list of resources based on search text.
b	Resources	Lists the version 1 Code42 API resources. Click a resource to view its description. Click > next to a resource to show links to the methods it offers.
c	Resource description	Describes the resource and the methods it offers. Available methods vary by resource but may include get, put, post, and delete.
d	Refresh API	Loads the latest resources and descriptions from the authority server, instead of from the browser's cache. When the authority server gets updated, you may need to click Refresh API to see new API information.
e	Shortcut Controls	Displays keyboard shortcuts.

Versions 3 and later

Code42 v3 v4 API Documentation Viewer

Item		Description
a	URL	Version 3 and later documentation resides at https:/./<authority-server-address>:4285/swagger.
b	API Version	Select a version.
c	Links and controls	Base URL: When you create API requests, direct them to the Base URL, followed by the resource name, for example: `https:/./server.example.com:4285/c42api/v3/ping` /v3/apispec, /docs/v4: Get this API documentation as a single JSON object. Code42 Server API License: The Code42 API is available to administrators whose product plans include the Code42 API. Code42 API authentication: Get instructions for both name:password and token-based authentication. V1 API Documentation: See the documentation viewer for additional API resources. Code42 Support - Website: A link to this support page. Send email to Code42 Support: Send questions to gethelp@code42.com. Schemes: The only possible value is `HTTPS`. Authorize: Controls a currently unsupported feature of the documentation viewer.
d	Category	API resources are categorized according to their functions. Click the heading to expand or collapse a category.
e	Resource	Click on a resource to see details about its use.

Details

Code42 v3 v4 API documentation details

Item		Description
a	Description details	The documentation may further describe a resource here. Three kinds of notes are common: Parameter Specification Options: For most resources, and unless otherwise stated, provide parameters as name=value pairs at the end of a URL, after a question mark (?), and separated by ampersands (&). Other parameters, especially complex data for POST and PUT methods, use parameters defined in the body of a request. Some parameters can be defined in either form. Associated License: This states when a resource requires specific licensing. A common example: You must have a license for the following feature: Legal_Hold For information about which features are included in an associated license, see Code42 product plans. Authority Server Only: Such notes apply only to on-premises Code42 environments, where administrators may control multiple Code42 servers.
b	Query Parameters	Describes valid parameters and values, and whether they are required. Unless stated otherwise, provide parameters as name=value pairs at the end of a URL, after a question mark (?), and separated by ampersands (&).
c	Request body	When parameters can or must be provided as body data, the documentation describes that request body.
d	application/json	For most resources, format body parameters as JSON data. For some resources, you may format data as `application/x-www-form-urlencoded`. Note: The documentation viewer does not display examples of such data. Regardless of your menu selection, the display shows JSON data.
e	Example Value \| Model	For data in request bodies and in responses, the documentation displays either example values for you to imitate, or the precise specifications of the data model. The viewer also provides a complete list and description of data models at the end, following the descriptions of resources.
f	Responses	Describes the value and meaning of the possible HTTP response codes. Some resources respond with additional data. Such data is always in JSON format.

Overview

Considerations

Find API documentation

Version 1

Versions 3 and later

API documentation reference

Version 1

Versions 3 and later

Details

Related topics