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 Bulk Payments API

Handle bulk payment file uploads and manual entry for batch payment processing with approval workflows and status tracking.

Temenos Bulk Payments 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 Bulk Payments. 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 4 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.temenos.com/payments/v1, https://sandbox.temenos.com/payments/v1.

3 operations 2 paths 4 schemas 1 GET2 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 Bulk Payments API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — JWT-based authentication token obtained through the Temenos authentication endpoint.

Paths & Operations 3

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

Bulk Payments 3

Handle bulk payment file uploads and manual entry for batch payment processing with approval workflows and status tracking.

GET
/bulkPayments
List Bulk Payment Batches
listBulkPayments 3 params → 200401
POST
/bulkPayments
Create Bulk Payment Batch
createBulkPayment body → 201400401
POST
/bulkPayments/{batchId}/approve
Approve Bulk Payment Batch
approveBulkPayment 1 param → 200401404

Schemas 4

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

Error
object
Error response
2 properties
BulkPaymentCreate
object
Request body for creating a bulk payment batch
4 properties 3 required
BulkPayment
object
Bulk payment batch
7 properties
PaginationHeader
object
Pagination metadata for list responses
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

temenos-bulk-payments-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 Callback Registry API
Temenos Cards API
Temenos Configuration Management API
Where this information came from

This is an independent, third-party profile of Temenos Bulk Payments 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.