n0t1fy-dev · Schema
MessageResponse
One message resource. Text, full recipient, and provider internals are never included.
CompanySMSGeorgiaTransactionalDeveloper-First
Properties
| Name | Type | Description |
|---|---|---|
| id | string | Opaque message identifier. Store it to read the status later. |
| object | string | Always `message`. |
| to | string | Masked recipient: country code and first digit, then the last two digits. |
| status | string | Normalized delivery state. `submitted` means the provider accepted the request, not that a handset received it. |
| segments | object | SMS segments this message occupies — the unit the provider bills. `null` only for messages created before segment counting existed. |
| error | object | `null` unless the message failed or was undeliverable. |
| created_at | string | ISO 8601 UTC, second precision, `Z` suffix. |
| updated_at | string | ISO 8601 UTC time of the most recent change. |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://artifacts.apis.io/n0t1fy-dev/json-schema/n0t1fy-dev-message-response-schema.json",
"title": "MessageResponse",
"description": "One message resource. Text, full recipient, and provider internals are never included.",
"x-generated": "2026-10-31",
"x-method": "derived",
"x-generator": "derive-json-schema.py",
"x-source": "openapi/n0t1fy-dev-api-openapi.json#/components/schemas/MessageResponse",
"properties": {
"id": {
"type": "string",
"title": "Id",
"description": "Opaque message identifier. Store it to read the status later."
},
"object": {
"type": "string",
"const": "message",
"title": "Object",
"description": "Always `message`."
},
"to": {
"type": "string",
"title": "To",
"description": "Masked recipient: country code and first digit, then the last two digits."
},
"status": {
"type": "string",
"enum": [
"queued",
"submitted",
"delivered",
"undeliverable",
"failed",
"unknown"
],
"title": "Status",
"description": "Normalized delivery state. `submitted` means the provider accepted the request, not that a handset received it."
},
"segments": {
"anyOf": [
{
"type": "integer"
},
{
"type": "null"
}
],
"title": "Segments",
"description": "SMS segments this message occupies — the unit the provider bills. `null` only for messages created before segment counting existed."
},
"error": {
"anyOf": [
{
"$ref": "#/$defs/MessageError"
},
{
"type": "null"
}
],
"description": "`null` unless the message failed or was undeliverable."
},
"created_at": {
"type": "string",
"title": "Created At",
"description": "ISO 8601 UTC, second precision, `Z` suffix."
},
"updated_at": {
"type": "string",
"title": "Updated At",
"description": "ISO 8601 UTC time of the most recent change."
}
},
"type": "object",
"required": [
"id",
"object",
"to",
"status",
"segments",
"created_at",
"updated_at"
],
"$defs": {
"MessageError": {
"properties": {
"code": {
"type": "string",
"title": "Code",
"description": "Stable machine-readable code, safe to branch on."
},
"message": {
"type": "string",
"title": "Message",
"description": "Human-readable explanation. Wording may change; the code will not."
}
},
"type": "object",
"required": [
"code",
"message"
],
"title": "MessageError",
"description": "A safe, provider-neutral explanation attached to a message."
}
}
}
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/n0t1fy-dev-message-response"
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.