Source
Integrations & automation — found from sitemap — Scrut Automation
Checked for Scrut Automation on 13 Oct 2026
- Page
- https://developer.scrut.io/create-api-credentials
- Checked
- 13 Oct 2026, 13:02 UTC
- How we may use it
- Public page, crawling permitted
Technical details
- type
- page
- http status
- 200
- content hash
- sha256:b671c2c840fba01b77a8ddbc7d8d6cce57de103f8bb815b0413cd63085056ad6
- permission
- robots_ok
- screenshot
- Screenshot on file (internal exhibit, not published)
Cited by
Facts read from this source
-
API plans Report an error
“Supported on Foundation, Growth, and Scale plans”
-
API credentials Report an error
“API credentials let your scripts, pipelines, and internal tools connect to your compliance data through the Scrut API. Each credential has a client ID and a client secret, which your integration exchanges for a short-lived access token.”
-
Credentials admin required Report an error
“You need Org Admin permissions in Scrut to generate and manage API credentials.”
-
Credential name limits Report an error
“Names can be up to 50 characters, must be unique in your organization, and can't be changed after you create the credential.”
-
Credential expiry options Report an error
“12 months The credential expires 12 months after you create it. Default. Never The credential stays active until you revoke it. Custom Date The credential expires on the date you pick.”
-
Credential scopes Report an error
“Read Only View compliance data across all modules and entities in your organization. Read & Write View compliance data across all modules and entities in your organization, upload evidence, and create or update vulnerability findings.”
-
Client secret shown once Report an error
“The client secret is shown only once. You can't view or recover it after you close this window. If you lose it, revoke the credential and create a new one.”
-
Credential revocation Report an error
“Revoking a credential invalidates all of its access tokens immediately, so any integration that uses it stops working right away. You can't undo this action.”
-
Audit logging Report an error
“The Developer Console → Audit Logs capture all actions, including credential creation and revocation. Evidence uploaded through the API is logged in the evidence task's Audit Logs tab, with the credential name as the actor.”
1 fact read from this page is not shown because it could not be confirmed on the page as captured.
Scores citing this record
- The CISO Pricing transparency
- The CISO Audit readiness & evidence
- The CISO Integrations & automation
- The CISO Audit readiness & evidence
- The CISO Integrations & automation
- The GRC Consultant Audit readiness & evidence
- The GRC Consultant Integrations & automation
- The GRC Consultant Audit readiness & evidence
- The GRC Consultant Integrations & automation
- The Evidence Integrator Audit readiness & evidence
- The Evidence Integrator Integrations & automation
- The Evidence Integrator Audit readiness & evidence
- The Evidence Integrator Integrations & automation
- The Drafted IT Officer Audit readiness & evidence
- The Drafted IT Officer Integrations & automation
- The Drafted IT Officer Audit readiness & evidence
- The Drafted IT Officer Integrations & automation
- The Lead Auditor Audit readiness & evidence
- The Lead Auditor Integrations & automation
- The Lead Auditor Pricing transparency
- The Lead Auditor Audit readiness & evidence
- The Lead Auditor Integrations & automation
- The Skeptic Audit readiness & evidence
- The Skeptic Integrations & automation
- The Skeptic Pricing transparency
- The Skeptic Audit readiness & evidence
- The Skeptic Integrations & automation