Harness · Schema
ApprovalsShowApprovalResponseBodyStatusInfo
Show-ApprovalResponseBody result type (statusInfo view)
DevOpsGitOpsInternal Developer PortalLifecycleSoftware DeliveryCI/CDContinuous DeliveryContinuous Integration
Properties
| Name | Type | Description |
|---|---|---|
| actioned_by | string | User that approved/rejected the step |
| actioned_by_email | string | Email of the user that approved/rejected the step |
| created | integer | Created is the unix timestamp at which the resource was originally created in milliseconds. |
| status | string | Status of the approval resource |
| updated | integer | Modified is the unix timestamp at which the resource was last modified in milliseconds. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/harness/main/json-schema/harness-approvals-show-approval-response-body-status-info-schema.json",
"title": "ApprovalsShowApprovalResponseBodyStatusInfo",
"description": "Show-ApprovalResponseBody result type (statusInfo view)",
"x-generated": "2026-10-04",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/harness-approvals-api-openapi.yml#/components/schemas/ApprovalsShowApprovalResponseBodyStatusInfo",
"type": "object",
"properties": {
"actioned_by": {
"type": "string",
"description": "User that approved/rejected the step"
},
"actioned_by_email": {
"type": "string",
"description": "Email of the user that approved/rejected the step"
},
"created": {
"type": "integer",
"description": "Created is the unix timestamp at which the resource was originally created in milliseconds.",
"format": "int64"
},
"status": {
"type": "string",
"description": "Status of the approval resource",
"default": "pending"
},
"updated": {
"type": "integer",
"description": "Modified is the unix timestamp at which the resource was last modified in milliseconds.",
"format": "int64"
}
},
"required": [
"status",
"created",
"updated"
]
}
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/harness-approvals-show-approval-response-body-status-info"
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.