TM Forum · Schema
Intent
Intent schema from TM Forum API
TelecommunicationsBSSOSSOpen APIsStandardsTM Forum
Properties
| Name | Type | Description |
|---|---|---|
| description | string | The description of the intent. |
| validFor | object | |
| isBundle | boolean | isBundle determines whether an intent represents a single intent (false), or a bundle of intents(true). |
| priority | string | Can be used by intent owner to prioritize intents in an intent management system |
| statusChangeDate | string | A date time( DateTime). The date that the entity status changed to the current one |
| context | string | A string used to give a context to the intent |
| version | string | A field that identifies the specific version of an instance of an intent. |
| intentSpecification | object | |
| intentRelationship | array | A list of intents related to this intent |
| characteristic | array | |
| relatedParty | array | |
| attachment | array | Attachments that may be of relevance to this intent, such as picture, document, media |
| name | string | The name of the intent. |
| expression | object | |
| creationDate | string | Date and time of the creation of this REST resource |
| lastUpdate | string | Date and time of the last update of this REST resource |
| lifecycleStatus | string | Used to indicate the current lifecycle status of this intent |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://raw.githubusercontent.com/api-evangelist/tm-forum/refs/heads/main/json-schema/tmf637-product-inventory-intent-schema.json",
"title": "Intent",
"description": "Intent schema from TM Forum API",
"allOf": [
{
"$ref": "#/components/schemas/Entity"
},
{
"type": "object",
"description": "An Intent instance is the formal description of all expectations including requirements, goals, and constraints given to a technical system",
"properties": {
"description": {
"type": "string",
"description": "The description of the intent."
},
"validFor": {
"$ref": "#/components/schemas/TimePeriod"
},
"isBundle": {
"type": "boolean",
"description": "isBundle determines whether an intent represents a single intent (false), or a bundle of intents(true)."
},
"priority": {
"type": "string",
"description": "Can be used by intent owner to prioritize intents in an intent management system"
},
"statusChangeDate": {
"type": "string",
"format": "date-time",
"description": "A date time( DateTime). The date that the entity status changed to the current one"
},
"context": {
"type": "string",
"description": "A string used to give a context to the intent"
},
"version": {
"type": "string",
"description": "A field that identifies the specific version of an instance of an intent."
},
"intentSpecification": {
"$ref": "#/components/schemas/EntityRef"
},
"intentRelationship": {
"type": "array",
"items": {
"$ref": "#/components/schemas/EntityRelationship"
},
"description": "A list of intents related to this intent"
},
"characteristic": {
"type": "array",
"items": {
"$ref": "#/components/schemas/Characteristic"
}
},
"relatedParty": {
"type": "array",
"items": {
"$ref": "#/components/schemas/RelatedPartyRefOrPartyRoleRef"
}
},
"attachment": {
"type": "array",
"items": {
"$ref": "#/components/schemas/AttachmentRefOrValue"
},
"description": "Attachments that may be of relevance to this intent, such as picture, document, media"
},
"name": {
"type": "string",
"description": "The name of the intent."
},
"expression": {
"$ref": "#/components/schemas/Expression"
},
"creationDate": {
"type": "string",
"format": "date-time",
"description": "Date and time of the creation of this REST resource"
},
"lastUpdate": {
"type": "string",
"format": "date-time",
"description": "Date and time of the last update of this REST resource"
},
"lifecycleStatus": {
"type": "string",
"description": "Used to indicate the current lifecycle status of this intent"
}
}
}
],
"discriminator": {
"propertyName": "@type",
"mapping": {
"Intent": "#/components/schemas/Intent"
}
}
}
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/tmf637-product-inventory-intent"
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.