For the complete documentation index, see llms.txt. This page is also available as Markdown.

Endpoints

Everything CIPP does in the interface is backed by an API endpoint, and the full reference for them now lives inside your own CIPP instance rather than on this site. It is generated from the source of the exact version you are running, so it always describes the deployment in front of you.

Opening the endpoint reference

Go to CIPP → Integrations → CIPP-API and open the API Documentation tab.

Every endpoint your deployment exposes is listed there. Expand one to see the parameters it accepts, the body it expects, and the responses it returns. The filter box at the top narrows the list by name.

Trying an endpoint

Each operation has a Try it out button that sends the call to the instance you are signed in to, using your existing session. There is no client ID, secret or token to paste in.

Using the specification in your own tools

The description behind the page is an OpenAPI 3.1 document, published by your instance at:

https://<your-cipp-url>/openapi.json

Open it while signed in to CIPP and save the file, then import it into Postman, Insomnia, or a client generator to scaffold your automation. It is rebuilt with every release, so pull a fresh copy after an upgrade to pick up new and changed endpoints.

Finding the endpoint behind a page

If you are not sure which call sits behind something you do in CIPP, open your browser's developer tools, switch to the Network tab, and perform the action. The request name matches the endpoint in the reference, so you can look it up there and see its full parameters.

Setting up access

Setup & AuthenticationCIPP-API & MCP

Feature Requests / Ideas

We value your feedback and ideas. Please raise any feature requests on GitHub.

Last updated

Was this helpful?