Properties
| Name | Type | Description |
|---|---|---|
| secretHash | string | The SHA-256 hash of the detected secret. |
| workspaceId | string | The ID of the workspace that contains the secret. |
| resolution | string | The secret's current resolution status: - `ACTIVE` — The secret is active. - `FALSE_POSITIVE` — The discovered secret is not an actual secret. - `REVOKED` — The secret is valid, but the user rotated t |
| history | array | The history of the secret's resolution status changes. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/updateSecretResolutions",
"title": "Successful Response",
"type": "object",
"properties": {
"secretHash": {
"type": "string",
"description": "The SHA-256 hash of the detected secret.",
"example": "50dbd2..."
},
"workspaceId": {
"type": "string",
"description": "The ID of the workspace that contains the secret.",
"example": "1f0df51a-8658-4ee8-a2a1-d2567dfa09a9"
},
"resolution": {
"type": "string",
"description": "The secret's current resolution status:\n- `ACTIVE` \u2014 The secret is active.\n- `FALSE_POSITIVE` \u2014 The discovered secret is not an actual secret.\n- `REVOKED` \u2014 The secret is valid, but the user rotated their key to resolve the issue.\n- `ACCEPTED_RISK` \u2014 The Secret Scanner found the secret, but user accepts the risk of publishing it.\n",
"example": "FALSE_POSITIVE",
"enum": [
"FALSE_POSITIVE",
"ACCEPTED_RISK",
"REVOKED",
"ACTIVE"
]
},
"history": {
"type": "array",
"description": "The history of the secret's resolution status changes.",
"items": {
"type": "object",
"properties": {
"actor": {
"type": "number",
"description": "The ID of the user that updated the secret's resolution status.",
"example": 12345678
},
"createdAt": {
"type": "string",
"format": "date-time",
"description": "The date and time at which the resolution status was updated.",
"example": "2024-09-18T18:46:26.000Z"
},
"resolution": {
"type": "string",
"description": "The secret's updated resolution status:\n- `ACTIVE` \u2014 The secret is active.\n- `FALSE_POSITIVE` \u2014 The discovered secret is not an actual secret.\n- `REVOKED` \u2014 The secret is valid, but the user rotated their key to resolve the issue.\n- `ACCEPTED_RISK` \u2014 The Secret Scanner found the secret, but user accepts the risk of publishing it.\n",
"enum": [
"FALSE_POSITIVE",
"ACCEPTED_RISK",
"REVOKED",
"ACTIVE"
],
"example": "FALSE_POSITIVE"
}
}
}
}
}
}
Work with this as data
Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for schemas
4 MCP tools reach this
find_json_schemasBrowse and filter every JSON Schema in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/apis-io-engineering-platform-updatesecretresolutions"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.