Instasent · Schema
Attention report
Everything demanding attention for the project and the organization behind it, worst first and then soonest deadline. Always recomputed; nothing is persisted.
CompanyMessagingSMSRCSWhatsAppArtificial IntelligenceMarketing
Properties
| Name | Type | Description |
|---|---|---|
| items | array | Filtered by the request. Sorted by severity, then deadline, then key. |
| counts | object | |
| computedAt | string | When the backend computed this (UTC ISO-8601). There is no cache behind it, so it is always "now" at assembly time. It travels because the CLIENT holds it, and because it is the only clock the timesta |
| truncated | boolean | True when the engine hit its per-report ceiling. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/instasent/json-schema/instasent-attention-response-schema.json",
"title": "Attention report",
"description": "Everything demanding attention for the project and the organization\nbehind it, worst first and then soonest deadline. Always recomputed;\nnothing is persisted.\n",
"x-generated": "2026-11-10",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/instasent-attention-api-openapi.yml#/components/schemas/AttentionResponse",
"type": "object",
"properties": {
"items": {
"type": "array",
"description": "Filtered by the request. Sorted by severity, then deadline, then key.",
"items": {
"$ref": "#/$defs/AttentionItem"
}
},
"counts": {
"$ref": "#/$defs/AttentionCounts"
},
"computedAt": {
"type": "string",
"format": "date-time",
"description": "When the backend computed this (UTC ISO-8601). There is no cache\nbehind it, so it is always \"now\" at assembly time. It travels\nbecause the CLIENT holds it, and because it is the only clock the\ntimestamps on the items can be read against.\n"
},
"truncated": {
"type": "boolean",
"description": "True when the engine hit its per-report ceiling."
}
},
"required": [
"items",
"counts",
"computedAt",
"truncated"
],
"additionalProperties": false,
"$defs": {
"AttentionCounts": {
"type": "object",
"title": "Attention counts",
"description": "Always computed over the WHOLE list, never over the filtered one: a\nsurface that asked for one tag still needs to know there are errors\nelsewhere, and it should not pay for a second call to learn a number\nthis one already computed.\n",
"properties": {
"error": {
"type": "integer"
},
"warning": {
"type": "integer"
},
"info": {
"type": "integer"
},
"byKey": {
"type": "object",
"description": "Occurrences per key.",
"additionalProperties": {
"type": "integer"
}
}
},
"required": [
"error",
"warning",
"info",
"byKey"
],
"additionalProperties": false
},
"AttentionEntity": {
"type": "object",
"title": "Attention entity",
"description": "Something an item is about, so a consumer can navigate to it without\nparsing copy. `name` is the entity's own display name and is therefore\ncustomer-written text; it is never personal data.\n",
"properties": {
"type": {
"type": "string",
"enum": [
"organization",
"card",
"invoice",
"subscription",
"project",
"datasource",
"auth",
"sender",
"register",
"campaign",
"token"
]
},
"id": {
"type": "string",
"description": "The entity's own id, or its uid where the surfaces address it that way."
},
"name": {
"type": "string",
"description": "Omitted when there is none. Never personal data."
}
},
"required": [
"type",
"id"
],
"additionalProperties": false
},
"AttentionItem": {
"type": "object",
"title": "Attention item",
"description": "ONE OCCURRENCE of one rule, not one rule with rows: two connectors\nneeding a reconnect are two items sharing a `key`.\n\n`type` says what it is and `severity` says how to react; they are\nindependent axes. `expired-card` and `expiring-card` are both\n`problem`, one `error` and one `warning`: the same card on either side\nof its expiry date. And `info` is not a type — `pending-review`\n(`procedure`) and `campaign-sending` (`live`) both carry it.\n\nSEVERITY IS DECLARED ONCE PER KEY and never varies per occurrence. An\nimport that is running and an import that has stalled are therefore not\none key at two severities; the second would be a key of its own.\n\n`tags` are a closed vocabulary and a key always carries exactly the same\nones, exactly one of which is a domain tag; never derive severity from a\ntag or the reverse.\n\n`data` is DISCRIMINATED BY `key`. Switch on the key; never infer the\npayload from which fields came back absent.\n\nTimestamps are absolute UTC and are ABSENT rather than null when\nunknown. Nothing relative is ever sent: the payload outlives the\ninstant it was computed, so read them against the report's\n`computedAt`.\n",
"properties": {
"id": {
"type": "string",
"description": "Content fingerprint of this occurrence, stable across polls while\nit is the same problem, and defined per key: an expired card is\nidentified by brand, last4 and expiry rather than by its id, so\nthat re-adding the same card stays dismissed while a different one\nresurfaces. Nothing volatile enters it.\n"
},
"key": {
"type": "string",
"description": "Stable rule identifier; the client owns the copy. It also\ndiscriminates `data`. A client must render an unknown key rather\nthan drop it: the backend can ship one ahead of its consumers.\n",
"enum": [
"expired-card",
"expiring-card",
"low-balance",
"subscription-past-due",
"unpaid-invoice",
"overdue-invoice",
"requested-payment-pending",
"pending-connection",
"datasource-reconnect",
"stale-datasource",
"scheduled-campaign-underfunded",
"campaign-unpaid",
"campaign-sending",
"datasource-syncing",
"auto-charge-disabled",
"api-rate-limit-blocked",
"rejected-registration",
"pending-review",
"unsubmitted-registration",
"regulation-deadline",
"registration-payment-pending"
]
},
"scope": {
"type": "string",
"enum": [
"org",
"project",
"channel"
],
"description": "`org` items affect every project of the organization."
},
"channel": {
"type": [
"string",
"null"
],
"enum": [
"sms",
"rcs",
null
],
"description": "Set only on a channel-scoped item."
},
"type": {
"type": "string",
"enum": [
"problem",
"live",
"procedure",
"recommendation"
],
"description": "What the item IS. The axis that separates `live` from `procedure`\nis WHO IS ACTING: `live` is something WE are doing right now (a\ncampaign going out, a connector importing) and changes in seconds,\nso it is only quotable freshly fetched; `procedure` is something\nfiled with a THIRD PARTY that has not resolved (a carrier or a\nregulator looking at a registration), changes in days, and is a\npointer to go and look rather than a figure to quote.\n\n`recommendation` never appears on THIS endpoint: the catalog is\npartitioned by type and recommendations are served by\n`/project/{project}/recommendations`. The value is listed because\nit exists in the vocabulary.\n\n⚠ `activity` WAS REMOVED on 2026-09-07 and split into `live` and\n`procedure`. Lumping \"a campaign is going out\" with \"a regulator is\ntaking its time\" told a consumer nothing about how long the answer\nstays true, which is the one thing it needed.\n"
},
"severity": {
"type": "string",
"enum": [
"error",
"warning",
"info"
],
"description": "Act, act soon, just know."
},
"summary": {
"type": "string",
"maxLength": 64,
"description": "One English sentence saying what this key IS, declared once per key\nand identical on every item of it. It exists for the consumers with\nno glossary and no localisation layer.\n\nAnything situational is in `data`, typed. A dashboard should render\nits own localised copy per key and never this.\n"
},
"tags": {
"type": "array",
"description": "Constant per key. Exactly one is a domain tag.",
"items": {
"type": "string",
"enum": [
"billing",
"compliance",
"delivery",
"data",
"audience",
"setup",
"entity:organization",
"entity:campaign",
"entity:datasource",
"entity:auth",
"entity:sender",
"entity:register",
"pending-connection",
"regulation-deadline",
"low-balance",
"expired-payment-method",
"insufficient-funds",
"unpaid-invoice",
"auto-charge-off",
"stale-data",
"registration-blocked"
]
}
},
"dismiss": {
"type": "object",
"description": "How a consumer may let a user silence this item. Declared by the\nrule and CONSTANT PER KEY, like the tags: no surface decides this\nper key on its own.\n\n`none` cannot be hidden. `dismiss` hides it with no date and it\nreturns only if the content changes, which is what `id` tracks.\n`snooze` hides it for `days` and it returns afterwards even if\nnothing changed, for facts that get worse on their own while their\nfingerprint stays identical.\n\nA snooze is a FLOOR, not a ceiling: if the content changes inside\nthe window the `id` changes and the item comes back early. The\nexpiry itself is computed by the browser when it silences the\nitem, so changing `days` here is not retroactive over dismissals\nalready stored. The backend stores none of it.\n",
"properties": {
"mode": {
"type": "string",
"enum": [
"none",
"dismiss",
"snooze"
]
},
"days": {
"type": "integer",
"description": "Present only when `mode` is `snooze`."
}
},
"required": [
"mode"
],
"additionalProperties": false
},
"entities": {
"type": "array",
"items": {
"$ref": "#/$defs/AttentionEntity"
}
},
"data": {
"type": "object",
"description": "Rule-specific payload, discriminated by `key`. Absent when the rule carries none.",
"additionalProperties": true
},
"state": {
"type": "string",
"enum": [
"running",
"finished"
],
"description": "How far along the underlying thing is. Authoritative over `endsAt`.\nNOT TIED TO A TYPE: any key may carry it, and a consumer must not\ninfer the type from its presence. Today `pending-review`\n(`procedure`) carries a `state` with no `progress`.\n"
},
"progress": {
"type": "object",
"description": "ABSENT rather than zeroed while the total is unknown, and not tied\nto a type either. That only the `live` keys carry it today is an\nobservation about the current catalog, not a contract. Absent while\nthe total is unknown: an import in its first seconds and a campaign\nthat reached `sending` without a resolved audience both report\n`state` alone. `done` is already clamped to `total`.\n",
"properties": {
"done": {
"type": "integer"
},
"total": {
"type": "integer"
}
},
"required": [
"done",
"total"
],
"additionalProperties": false
},
"startsAt": {
"type": "string",
"format": "date-time",
"description": "When the underlying fact began. Absent when unknown."
},
"endsAt": {
"type": "string",
"format": "date-time",
"description": "When it ended or will end, if bounded."
},
"dueAt": {
"type": "string",
"format": "date-time",
"description": "The deadline after which the consequence lands."
}
},
"required": [
"id",
"key",
"scope",
"channel",
"type",
"severity",
"summary",
"tags",
"dismiss",
"entities"
],
"additionalProperties": false
}
}
}
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/instasent-attention-response"
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.