# Validate a JSON API response before handoff

**Use case:** 

Check a JSON API response's required fields and value types against a bounded JSON Schema before handing it off. Uses deterministic rules; no network calls.

## Input

```json
{
  "requirements": [
    {
      "name": "response.json",
      "kind": "json",
      "maxBytes": 10000,
      "jsonSchema": {
        "type": "object",
        "required": [
          "status",
          "data"
        ],
        "properties": {
          "status": {
            "type": "string",
            "enum": [
              "ok"
            ]
          },
          "data": {
            "type": "object",
            "required": [
              "count"
            ],
            "properties": {
              "count": {
                "type": "integer",
                "minimum": 0
              }
            },
            "additionalProperties": false
          }
        },
        "additionalProperties": false
      }
    }
  ],
  "files": [
    {
      "name": "response.json",
      "content": "{\"status\":\"ok\",\"data\":{\"count\":2}}"
    }
  ],
  "allowExtraFiles": false
}
```

## Output

```json
{
  "status": {
    "label": "Report status",
    "format": "string"
  },
  "failedFiles": {
    "label": "Failed files",
    "format": "integer"
  },
  "requiredFiles": {
    "label": "Required files",
    "format": "integer"
  },
  "totalBytes": {
    "label": "Total input bytes",
    "format": "integer"
  },
  "issues": {
    "label": "Bundle issues",
    "format": "array"
  },
  "files": {
    "label": "Per-file checks",
    "format": "array"
  },
  "notChecked": {
    "label": "Out-of-scope checks",
    "format": "array"
  }
}
```

## About this Actor

This example demonstrates how to use [Delivery Check — JSON & CSV Handoff Validator](https://apify.com/grayt/delivery-check.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/grayt/delivery-check.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
This Task's input is already configured above — use it as-is rather than inventing a new one.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/grayt/delivery-check.md

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).