Skip to main content

Getting Started

Overview

Integrating the CMS API into your publishing workflow triggers priority auditing of the page you’re working on for on-the-fly auditing. This allows you to see the results in Conductor Monitoring immediately after making a change.

Note!

Conductor provides APIs for several different uses across its Conductor Monitoring and Conductor Intelligence products. This article describes Conductor Monitoring’s CMS API. If you are looking for information about a different API offering, consider the following articles:

How does the CMS API work?

The CMS API uses a single endpoint in Conductor Monitoring’s Reporting v1 API. When you publish a new or edited page, you can send the URL in the request body to this endpoint to let Conductor Monitoring know that it should be prioritized for auditing.

Authentication

Get your CMS API integration token

To use the CMS API you need to get your Conductor Monitoring account’s CMS API token. You’ll find it in the Integration Tokens section under the Account tab in the main Account section. contentking-retrieving-cms-api-token@2x.png

Configure your request headers

To authenticate your requests, you need to include the following request headers:

Note!

The value for the Authorization header must be the string “token” followed by a space and then your actual API token.

Using the CMS API

Prioritize a Page for Audit by Conductor Monitoring

https://api.cm.conductor.com/v1/check\_url

Every time you make a change through your CMS, such as adding, deleting, or changing a page, you need your website to call the Conductor Monitoring API with a POST request to this endpoint.

Request Body

Note!

Don’t forget to include the domain name and protocol (http or https) in your request.

Responses

Need some help with integrating the CMS API?

In case you or your developer need any help with integrating the API don’t hesitate to reach out. We’re always happy to help!