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

Lorum Simulation API

The Simulation API from Lorum — 4 operation(s) for simulation.

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

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

This API exposes 4 operations across 4 paths, and defines 7 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.

4 operations 4 paths 7 schemas 4 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
License
Proprietary license
Resource Areas
1

Authentication & Security 1

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

Paths & Operations 4

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

Simulation 4
POST
/v1/simulate/execute-payment
Simulate executed status for an outbound payment
simulate_execute_payment body → 200
POST
/v1/simulate/fail-payment
Simulate failed status for an outbound payment
simulate_fail_payment body → 200
POST
/v1/simulate/inbound-payment
Simulate inbound payment
simulate_inbound_payment body → 200
POST
/v1/simulate/return-payment
Simulate a return payment.
simulate_return_payment body → 200

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are SimulateInboundRequest (7 properties), WireBankDetails (2 properties), ScanDetails (2 properties), SimulateFailPaymentRequest (2 properties). Each schema is shown below with its type and property counts.

SimulateInboundRequest
object
Parameters to simulate an inbound payment.
7 properties 3 required
AccountDetailsIdentifier
SimulateFailPaymentRequest
object
Parameters for failing a payment.
2 properties 2 required
SimulateExecutePaymentRequest
object
Parameters to simulate executing a payment.
1 property 1 required
ScanDetails
object
2 properties 2 required
WireBankDetails
object
2 properties 2 required
SimulateReturnedPaymentRequest
object
Parameters to simulate executing a payment.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lorum-simulation-api-openapi.yml Raw ↑

Other APIs Lorum publishes across the network.

Lorum Accounts API
Lorum Customers API
Lorum Customers V2 API
Lorum Documents API
Lorum Exchange API
Lorum Internal Transfers API
Lorum Oauth API
Lorum Payments API
Lorum Transactions API
Where this information came from

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