Developers
Choose the Probo interface for your integration, authenticate safely, and automate compliance records with GraphQL, the CLI, MCP, n8n, or webhooks.
Connect Probo to the tools your team already uses. Query and update organization-scoped records, build workflows, or react to changes with the interface that fits your integration.
Start with API fundamentals Understand endpoints, authentication, organization identifiers, pagination, and errors.
Interfaces
Section titled “Interfaces”| I want to… | Use | Start here |
|---|---|---|
| Build an application integration | GraphQL | GraphQL API |
| Work from a terminal, script, or CI job | prb CLI | CLI overview |
| Give an AI assistant access to Probo | MCP | MCP overview |
| Build a visual workflow | n8n | n8n overview |
| Receive signed notifications about supported record changes | Webhooks | Webhooks overview |
| Enroll devices and report endpoint security posture | Device Agent API | Device Agent API overview |
Before your first request
Section titled “Before your first request”- Choose the organization. Records are scoped to an organization; use the identifier required by the operation.
- Choose authentication for your client. Use a supported interactive OAuth flow or a scoped token as described in API fundamentals.
- Start with a read. Confirm access to the intended records before adding an operation that changes them.
Keep credentials out of source code and logs. Request only the scopes your integration needs.
Interface parity
Section titled “Interface parity”GraphQL, MCP, the CLI, and n8n work with the same product resources, but they differ in transport, workflow, and available operations. Check the reference for the exact operation you need before choosing an interface:
- MCP tool reference — tool inputs, outputs, and behavior.
- n8n resource reference — the operations exposed by the Probo node.
- CLI command reference — command usage and implementation links.
If you are learning the records rather than integrating them, start with Core concepts.