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

Lithic Transaction Monitoring API

Fraud/AML case and queue management for flagged transactions.

Lithic Transaction Monitoring API is one of 31 APIs that Lithic publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transaction Monitoring. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 18 operations across 11 paths, and defines 1 schema. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://api.lithic.com, https://sandbox.lithic.com.

18 operations 11 paths 1 schemas 3 DELETE9 GET3 PATCH3 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.lithic.com/v1
Authentication
API Key
Contact
License
Resource Areas
1

Authentication & Security 1

Lithic Transaction Monitoring API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (ApiKeyAuth). By default, every request must be authenticated.

  • ApiKeyAuth — Raw API secret key value (not prefixed with "Bearer").

Paths & Operations 18

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

Transaction Monitoring 18

Fraud/AML case and queue management for flagged transactions.

GET
/v1/transaction_monitoring/cases
List cases
listTransactionMonitoringCases → 200401422
GET
/v1/transaction_monitoring/cases/{case_token}
Get case
getTransactionMonitoringCase → 200401422
PATCH
/v1/transaction_monitoring/cases/{case_token}
Update case
updateTransactionMonitoringCase body → 200401422
GET
/v1/transaction_monitoring/cases/{case_token}/activity
List case activity
listTransactionMonitoringCaseActivity → 200401422
GET
/v1/transaction_monitoring/cases/{case_token}/transactions
List case transactions
listTransactionMonitoringCaseTransactions → 200401422
GET
/v1/transaction_monitoring/cases/{case_token}/cards
List case cards
listTransactionMonitoringCaseCards → 200401422
POST
/v1/transaction_monitoring/cases/{case_token}/comments
Add case comment
createTransactionMonitoringCaseComment body → 200401422
PATCH
/v1/transaction_monitoring/cases/{case_token}/comments/{comment_token}
Update case comment
updateTransactionMonitoringCaseComment body → 200401422
DELETE
/v1/transaction_monitoring/cases/{case_token}/comments/{comment_token}
Delete case comment
deleteTransactionMonitoringCaseComment → 200401422
POST
/v1/transaction_monitoring/cases/{case_token}/files
Create case file
createTransactionMonitoringCaseFile body → 200401422
GET
/v1/transaction_monitoring/cases/{case_token}/files
List case files
listTransactionMonitoringCaseFiles → 200401422
GET
/v1/transaction_monitoring/cases/{case_token}/files/{file_token}
Get case file
getTransactionMonitoringCaseFile → 200401422
DELETE
/v1/transaction_monitoring/cases/{case_token}/files/{file_token}
Delete case file
deleteTransactionMonitoringCaseFile → 200401422
POST
/v1/transaction_monitoring/queues
Create queue
createTransactionMonitoringQueue body → 200401422
GET
/v1/transaction_monitoring/queues
List queues
listTransactionMonitoringQueues → 200401422
GET
/v1/transaction_monitoring/queues/{queue_token}
Get queue
getTransactionMonitoringQueue → 200401422
PATCH
/v1/transaction_monitoring/queues/{queue_token}
Update queue
updateTransactionMonitoringQueue body → 200401422
DELETE
/v1/transaction_monitoring/queues/{queue_token}
Delete queue
deleteTransactionMonitoringQueue → 200401422

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is TransactionMonitoring (2 properties). Each schema is shown below with its type and property counts.

TransactionMonitoring
object
Fraud/AML case and queue management for flagged transactions.
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

lithic-com-transaction-monitoring-api-openapi.yml Raw ↑

Other APIs Lithic publishes across the network.

Lithic 3DS API
Lithic Account API
Lithic Account Holder API
Lithic Auth Rules API
Lithic Auth Stream Access (ASA) API
Lithic Balance API
Lithic Book Transfer API
Lithic Card API
Lithic Card Authorizations API
Lithic Card Bulk Orders API
Lithic Chargeback API
Lithic Credit Product API
Where this information came from

This is an independent, third-party profile of Lithic Transaction Monitoring 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.