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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Lorum

Lorum Transactions API

The Transactions API from Lorum — 8 operation(s) for transactions.

Documentation Provider Profile APIs.io OpenAPI GitHub

Lorum Transactions API is one of 10 APIs that Lorum publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 9 operations across 8 paths, and defines 40 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against 2 base URLs: https://api.fuse.me, https://api-sandbox.fuse.me.

9 operations 8 paths 40 schemas 7 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://api.fuse.me
Authentication
HTTP Bearer
Contact
Lorum
License
Proprietary license
Resource Areas
1

Authentication & Security 1

Lorum Transactions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (OAuth2). By default, every request must be authenticated.

Paths & Operations 9

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

Transactions 9
GET
/v1/transactions/batches/{batch_id}
Get a single batch
get_batch 1 param → 200
GET
/v1/transactions/{transaction_id}/documents
Get linked documents for a transaction
get_documents_linked_to_transaction 1 param → 200400401404500
POST
/v1/transactions/{transaction_id}/documents
Link a document to a transaction
link_document_to_transaction 1 param body → 200400401404500
GET
/v1/transactions/{transaction_id}
Get a transaction
get_transaction 1 param → 200
GET
/v1/transactions/{transaction_id}/confirmation-letter
Get transaction confirmation letter
get_transaction_confirmation_letter 1 param → 200
GET
/v1/transactions/batches
List batches
list_batches 3 params → 200
GET
/v1/accounts/{account_id}/transactions
List transactions for an account
list_customer_transactions 6 params → 200
POST
/v1/transactions/batches/files
Upload payment batch file.
post_batch_file 1 param body → 201400
GET
/v1/transactions
Get all transactions across accounts
public_list_all_transactions 11 params → 200

Schemas 40

The contract defines 40 schemas that model the data the API accepts and returns. The most detailed are LocalPaymentRecord (24 properties), LocalPayment (23 properties), FxTransfer (16 properties), InternalTransfer (13 properties). Each schema is shown below with its type and property counts.

UploadBatchFileResponse
object
Response to uploading a batch file.
1 property 1 required
AccountDetailsIdentifier
BeneficiaryDetails
object
Account details of the payment beneficiary.
2 properties 2 required
DocumentSummary
object
3 properties 3 required
WireBankDetails
object
2 properties 2 required
ErrorResponse
object
User-facing error type. This is the general error structure returned by all api routes.
3 properties 3 required
TransactionState
string
Transaction State.
PaymentFailure
PurposeCode
string
Enum representing different payment purposes.
Direction
string
Transaction direction.
Currency
string
BeneficiaryType
string
PaymentTypeQuery
string
BeneficiaryExtraDetails
object
Additional details of the beneficiary. It will be not set for inbound payments.
2 properties
FeeDebit
object
6 properties 6 required
UploadBatchFileRequest
object
Request to upload a payments batch file. Note: file can contain up to 1000 payments.
3 properties 3 required
Address
object
5 properties 2 required
LinkDocumentRequest
object
1 property 1 required
InternalTransfer
object
Internal Transfer
13 properties 9 required
Batch
object
7 properties 7 required
InternalTransferTransactionState
string
Internal transfer state
Cursor_String
object
2 properties 1 required
FxTransfer
object
16 properties 12 required
Transaction
Transaction Container.
LocalReturnPayment
object
Return Payment
12 properties 12 required
FeeSourceRef
BatchSummary
object
6 properties 6 required
DocumentType
string
Types of documents that can be uploaded for customers and transactions.
RemitterDetails
object
Account details of the payment remitter.
2 properties 2 required
FeeTargetRef
BatchType
string
The type of batch being uploaded.
LocalPaymentRecord
object
24 properties 8 required
ListBatchesResponse
object
2 properties 2 required
BatchStatus
string
transaction.Batch
object
2 properties 2 required
ScanDetails
object
2 properties 2 required
FxTransferTransactionState
string
Internal transfer state
ListTransactionsPagedResponse
object
2 properties 2 required
LocalPayment
object
Payment
23 properties 13 required
PaymentScheme
string

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lorum-transactions-api-openapi.yml Raw ↑

Other APIs Lorum publishes across the network.

Lorum Accounts API
AE Profile APIs.io
Lorum Customers API
AE Profile APIs.io
Lorum Customers V2 API
AE Profile APIs.io
Lorum Documents API
AE Profile APIs.io
Lorum Exchange API
AE Profile APIs.io
Lorum Internal Transfers API
AE Profile APIs.io
Lorum Oauth API
AE Profile APIs.io
Lorum Payments API
AE Profile APIs.io
Lorum Simulation API
AE Profile APIs.io
#Transaction
← Back to L APIs
API Details
ID
lorum:lorum-transactions-api
Base URL
https://api.fuse.me
Docs
https://docs.lorum.com/docs/getting-started
Provider
Lorum
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=lorum-transactions-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/lorum-transactions-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Lorum Transactions 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.