Temenos · Schema
Temenos Banking Event
Schema for Temenos banking events published through the event-driven architecture via Apache Kafka and JMS messaging. Covers business events, system events, and data replication events.
BankingCloud BankingCore BankingDigital BankingFinancial-ServicesFintechOpen BankingPaymentsWealth Management
Properties
| Name | Type | Description |
|---|---|---|
| eventId | string | Unique event identifier for deduplication and tracking |
| eventType | string | Classification of the event type |
| source | string | Source application or service that generated the event |
| correlationId | string | Correlation identifier for tracing related events across services |
| timestamp | string | ISO 8601 timestamp when the event occurred |
| version | string | Event schema version for compatibility |
| payload | object | Event-specific payload data in JSON format |
| metadata | object |
JSON Schema
{
"$schema": "https://json-schema.org/draft/2020-12/schema",
"$id": "https://temenos.com/schemas/temenos/event.json",
"title": "Temenos Banking Event",
"description": "Schema for Temenos banking events published through the event-driven architecture via Apache Kafka and JMS messaging. Covers business events, system events, and data replication events.",
"type": "object",
"required": ["eventId", "eventType", "timestamp"],
"properties": {
"eventId": {
"type": "string",
"description": "Unique event identifier for deduplication and tracking"
},
"eventType": {
"type": "string",
"description": "Classification of the event type",
"enum": [
"account.created",
"account.closed",
"account.status.changed",
"payment.order.accepted",
"payment.order.confirmed",
"payment.order.failed",
"customer.onboarded",
"customer.updated",
"customer.kyc.changed",
"transaction.committed",
"compliance.sanction.alert",
"compliance.risk.changed",
"data.replication",
"system.health",
"system.config.changed"
]
},
"source": {
"type": "string",
"description": "Source application or service that generated the event"
},
"correlationId": {
"type": "string",
"description": "Correlation identifier for tracing related events across services"
},
"timestamp": {
"type": "string",
"format": "date-time",
"description": "ISO 8601 timestamp when the event occurred"
},
"version": {
"type": "string",
"description": "Event schema version for compatibility",
"pattern": "^[0-9]+\\.[0-9]+$"
},
"payload": {
"type": "object",
"description": "Event-specific payload data in JSON format",
"additionalProperties": true
},
"metadata": {
"$ref": "#/$defs/EventMetadata"
}
},
"$defs": {
"EventMetadata": {
"type": "object",
"description": "Additional metadata about the event for processing and routing",
"properties": {
"tenantId": {
"type": "string",
"description": "Multi-tenant identifier"
},
"userId": {
"type": "string",
"description": "User who triggered the event"
},
"channel": {
"type": "string",
"description": "Channel through which the event originated",
"enum": ["API", "ONLINE_BANKING", "MOBILE", "BRANCH", "ATM", "BATCH", "SYSTEM"]
},
"priority": {
"type": "string",
"description": "Event processing priority",
"enum": ["LOW", "NORMAL", "HIGH", "CRITICAL"]
},
"retryCount": {
"type": "integer",
"description": "Number of delivery retry attempts",
"minimum": 0
}
}
}
}
}
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/temenos-event"
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.