AfterShip · Schema
Meta
Meta data object.
ShippingTrackingE-CommercePost-PurchaseNotificationLogisticsReturnsWarrantyAddress ValidationFulfillmentCarrierWebhookMCPRetail
Properties
| Name | Type | Description |
|---|---|---|
| code | integer | Code of Meta |
| message | string | Message of Meta |
| details | array | Details of Meta |
| retryable | boolean | Whether this request will be retryable or not |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/aftership/main/json-schema/aftership-meta-v3-schema.json",
"title": "Meta",
"description": "Meta data object.",
"x-generated": "2026-10-12",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/aftership-address-validations-beta-api-openapi.yml#/components/schemas/Meta.v3",
"type": "object",
"x-tags": [
"Envelope"
],
"properties": {
"code": {
"type": "integer",
"description": "Code of Meta"
},
"message": {
"type": "string",
"description": "Message of Meta"
},
"details": {
"type": "array",
"description": "Details of Meta",
"items": {
"$ref": "#/$defs/Error.v3"
}
},
"retryable": {
"type": "boolean",
"description": "Whether this request will be retryable or not"
}
},
"required": [
"code",
"message"
],
"$defs": {
"Error.v3": {
"type": "object",
"title": "Error",
"description": "Each error object contains a \"path\" key and an \"info\" key. The \"path\" is the JSON path of the request object to indicate the error location. The \"info\" is a human-readable description of the error.",
"additionalProperties": false,
"x-tags": [
"Envelope"
],
"properties": {
"path": {
"type": "string",
"description": "The json path of the request object to indicate the error location"
},
"info": {
"type": "string",
"description": "A human-readable description of the error."
}
}
}
}
}
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/aftership-meta-v3"
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.