Clyde · Schema

PostContractSalesFbd13A8FB74649888925456843Ddc533ClaimsReque

Extended WarrantyProduct RegistrationShipping ProtectionE‑commerce IntegrationClaims Processing

Properties

Name Type Description
data object Top‑level object containing all of the request data
data.type string Must be "claim"
data.attributes object Attributes of the claim
data.attributes.claimType string Type of claim (e.g., "stoppedWorking")
data.attributes.description string Description of the issue
data.attributes.failureDate string Date of failure (UTC, format YYYY‑MM‑DD)
data.attributes.filedDate string Date the claim was filed (UTC, format YYYY‑MM‑DD)
data.attributes.retailerAssessment object Details of any retailer assessment performed before creating the claim
data.attributes.retailerAssessment.date string Assessment date (UTC, format YYYY‑MM‑DD)
data.attributes.retailerAssessment.status string Assessment status (e.g., "approved")
data.attributes.retailerAssessment.resolutionType string Resolution type (e.g., "replace")
data.attributes.retailerAssessment.resolutionMethod string Resolution method (e.g., "payout")
data.attributes.retailerAssessment.resolutionQuote number Monetary quote for the resolution
View JSON Schema on GitHub

JSON Schema

clyde-post-contract-sales-fbd13-a8-fb74649888925456843-ddc533-claims-reque-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "$id": "https://raw.githubusercontent.com/api-evangelist/clyde/main/json-schema/clyde-post-contract-sales-fbd13-a8-fb74649888925456843-ddc533-claims-reque-schema.json",
  "title": "PostContractSalesFbd13A8FB74649888925456843Ddc533ClaimsReque",
  "x-generated": "2026-10-12",
  "x-method": "derived",
  "x-generator": "derive-json-schema.py",
  "x-source": "openapi/_ae-authored/clyde-openapi-generated.yml#/components/schemas/PostContractSalesFbd13A8FB74649888925456843Ddc533ClaimsReque",
  "type": "object",
  "properties": {
    "data": {
      "type": "object",
      "description": "Top‑level object containing all of the request data"
    },
    "data.type": {
      "type": "string",
      "description": "Must be \"claim\""
    },
    "data.attributes": {
      "type": "object",
      "description": "Attributes of the claim"
    },
    "data.attributes.claimType": {
      "type": "string",
      "description": "Type of claim (e.g., \"stoppedWorking\")"
    },
    "data.attributes.description": {
      "type": "string",
      "description": "Description of the issue"
    },
    "data.attributes.failureDate": {
      "type": "string",
      "description": "Date of failure (UTC, format YYYY‑MM‑DD)"
    },
    "data.attributes.filedDate": {
      "type": "string",
      "description": "Date the claim was filed (UTC, format YYYY‑MM‑DD)"
    },
    "data.attributes.retailerAssessment": {
      "type": "object",
      "description": "Details of any retailer assessment performed before creating the claim"
    },
    "data.attributes.retailerAssessment.date": {
      "type": "string",
      "description": "Assessment date (UTC, format YYYY‑MM‑DD)"
    },
    "data.attributes.retailerAssessment.status": {
      "type": "string",
      "description": "Assessment status (e.g., \"approved\")"
    },
    "data.attributes.retailerAssessment.resolutionType": {
      "type": "string",
      "description": "Resolution type (e.g., \"replace\")"
    },
    "data.attributes.retailerAssessment.resolutionMethod": {
      "type": "string",
      "description": "Resolution method (e.g., \"payout\")"
    },
    "data.attributes.retailerAssessment.resolutionQuote": {
      "type": "number",
      "description": "Monetary quote for the resolution"
    }
  },
  "required": [
    "data",
    "data.type",
    "data.attributes",
    "data.attributes.claimType",
    "data.attributes.description",
    "data.attributes.failureDate",
    "data.attributes.filedDate"
  ]
}

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.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/clyde-post-contract-sales-fbd13-a8-fb74649888925456843-ddc533-claims-reque"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.