Getting StartedOverview

Scrut API Overview

Learn what the Scrut API covers, which modules you can work with, and which regional base URL to use for your organization.

Who can use this feature

Supported on Foundation, Growth, and Scale plans

The Scrut API gives you programmatic access to your compliance data through a versioned REST interface. Use it to read policies, controls, evidence, frameworks, automated tests, and vulnerabilities, upload evidence attachments, and create or update vulnerability findings from your scripts, CI/CD pipelines, or backend services.

Want to work with your Scrut data in an AI assistant like Claude, ChatGPT, or Cursor? See Scrut MCP.

What You Can Do With the Scrut API

The API currently covers six Scrut modules:

ModuleAvailable operations
FrameworksList frameworks with mapped entities, compliance progress, and next audit date
PoliciesList policies
Get a single policy with its mappings and version history
ControlsList controls
Get a single control with compliance overview, mapped artifacts, and mapped risks
EvidenceList evidence
Get a single evidence
Upload evidence attachments
TestsList tests
Get a single test with flagged resources, mapped risks, and test history
VulnerabilitiesList vulnerabilities
Get a single vulnerability
Create third-party findings
Update third-party findings

How the Scrut API Works

  • Authentication: Every integration uses an API credential (a client ID and client secret) to request a short-lived access token through the OAuth 2.0 client credentials grant. See Authentication and Access Tokens.
  • Access levels: Each credential is Read Only or Read & Write. The access level decides which scopes the credential has and which endpoints it can call. See Scopes and Permissions.
  • Requests and responses: Resource endpoints are versioned under /v1 and return JSON in a consistent envelope. See Requests and Responses.
  • Safe retries: Every write request needs an Idempotency-Key header so you can retry without creating duplicates. See Idempotency.
  • Limits: Requests are rate limited per credential. See Rate Limits.

Base URLs

Send requests to the base URL for the region where your Scrut organization is hosted:

RegionBase URL
Indiahttps://api.scrut.io
UShttps://api.us.scrut.io
EUhttps://api.eu.scrut.io
Australiahttps://api.au.scrut.io

Not sure which region your organization is hosted in? Log in to Scrut and check the URL you're redirected to:
• app.scrut.io, use https://api.scrut.io
• app.us.scrut.io, use https://api.us.scrut.io
• app.eu.scrut.io, use https://api.eu.scrut.io
• app.au.scrut.io, use https://api.au.scrut.io

  • Use the same base URL for the token endpoint and all /v1 requests.
  • A credential works only with its own region's base URL.
  • Resource endpoints are versioned under /v1. The token endpoint, /oauth/token, is not versioned.
  • The examples across these docs use https://api.scrut.io. Replace it with your region's base URL.

Prerequisites

Before you use the Scrut API, make sure you have:

  • A client ID and client secret from an API credential. Org Admins create credentials in Settings → Developer Console. See Create API Credentials.
  • A secure place to store credentials, such as environment variables or a secrets manager.
  • An HTTP client or language of your choice, such as cURL, Node.js, or Python.

Next Reads

Contact support@scrut.io for further assistance.

Was this page helpful?