How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Temenos Callback Registry API

Register callback URLs to receive notifications when long-running transaction processing completes.

Temenos Callback Registry API is one of 61 APIs that Temenos publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include Callback Registry. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, a changelog, and an AsyncAPI specification.

This API exposes 3 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://api.temenos.com/transact/microservices/v1.

3 operations 2 paths 3 schemas 1 DELETE1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.temenos.com/transact
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Temenos Callback Registry API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 3

Across 2 paths, the API surfaces 3 operations — 1 DELETE, 1 GET, 1 POST. Each is listed below with its method, path, parameters, and response codes.

Callback Registry 3

Register callback URLs to receive notifications when long-running transaction processing completes.

GET
/callbacks
List Registered Callbacks
listCallbacks 2 params → 200401
POST
/callbacks
Register Callback URL
registerCallback body → 201400401
DELETE
/callbacks/{callbackId}
Remove Callback Registration
removeCallback 1 param → 204401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Callback (4 properties), CallbackCreate (2 properties), Error (2 properties). Each schema is shown below with its type and property counts.

Error
object
Error response
2 properties
CallbackCreate
object
Callback registration request
2 properties 1 required
Callback
object
Registered callback
4 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

temenos-callback-registry-api-openapi.yml Raw ↑

Other APIs Temenos publishes across the network.

Temenos Lifecycle Management Suite API
Temenos Ecosystem API
Temenos Explorer API
Temenos Accounts API
Temenos Accounts Arrangement Details API
Temenos Alert Management API
Temenos Analytics Data Store API
Temenos Application Metering API
Temenos Application Packages API
Temenos Bulk Payments API
Temenos Cards API
Temenos Configuration Management API
Where this information came from

This is an independent, third-party profile of Temenos Callback Registry API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.