Properties
| Name | Type | Description |
|---|---|---|
| description | string | In this field, connectors should describe relevant information about the log, so Sent Offers users can better understand the action taking place. |
| date | string | Logs follow a chronological timeline, so make sure the date included corresponds to the correct order of logs. |
| type | string | Connectors are responsible for attributing the correct type for each log. Therefore, be mindful of their correct usage. `success`: only logs that conclude an interaction’s goal should be `“type”=”succ |
| agent | string | Entity responsible for creating the entry. |
| evidence | object | |
| data | object | |
| errors | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "#/components/schemas/CreateLogRequest",
"title": "CreateLogRequest",
"required": [
"description",
"date",
"type",
"agent",
"evidence",
"data",
"errors"
],
"type": "object",
"properties": {
"description": {
"type": "string",
"description": "In this field, connectors should describe relevant information about the log, so Sent Offers users can better understand the action taking place.",
"default": "Insert your message"
},
"date": {
"type": "string",
"description": "Logs follow a chronological timeline, so make sure the date included corresponds to the correct order of logs.",
"default": "2020-03-22"
},
"type": {
"type": "string",
"description": "Connectors are responsible for attributing the correct type for each log. Therefore, be mindful of their correct usage. \n\n`success`: only logs that conclude an interaction\u2019s goal should be `\u201ctype\u201d=\u201dsuccess\u201d`. \n\n`information`: logs that expose the actions of an update process, to provide visibility and contribute with more technical investigations. Information logs may include internal processes of a system (`agent` attribute), or calls between two systems. \n\n`warning`: logs used in cases where the communication between two systems fails, and there are no actions that the user can take to fix it. They are usually cases where the connector should perform a retry, and provide visibility of what is being attempted again. \n\n`failure`: logs noticed by the connector as errors that prevent an offer from being correctly sent and synced to a channel.",
"default": "information"
},
"agent": {
"type": "string",
"description": "Entity responsible for creating the entry.",
"default": "broadcaster"
},
"evidence": {
"$ref": "#/components/schemas/Evidence"
},
"data": {
"$ref": "#/components/schemas/Data"
},
"errors": {
"$ref": "#/components/schemas/Errors"
}
}
}
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/vtex-createlogrequest"
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.