Interface LithicClient
-
- All Implemented Interfaces:
public interface LithicClientA client for interacting with the Lithic REST API synchronously. You can also switch to asynchronous execution via the async method.
This client performs best when you create a single instance and reuse it for all interactions with the REST API. This is because each client holds its own connection pool and thread pools. Reusing connections and threads reduces latency and saves memory. The client also handles rate limiting per client. This means that creating and using multiple instances at the same time will not respect rate limits.
The threads and connections that are held will be released automatically if they remain idle. But if you are writing an application that needs to aggressively release unused resources, then you may call close.
-
-
Nested Class Summary
Nested Classes Modifier and Type Class Description public interfaceLithicClient.WithRawResponseA view of LithicClient that provides access to raw HTTP responses for each method.
-
Method Summary
-
-
Method Detail
-
async
abstract LithicClientAsync async()
Returns a version of this client that uses asynchronous execution.
The returned client shares its resources, like its connection pool and thread pools, with this client.
-
withRawResponse
abstract LithicClient.WithRawResponse withRawResponse()
Returns a view of this service that provides access to raw HTTP responses for each method.
-
withOptions
abstract LithicClient withOptions(Consumer<ClientOptions.Builder> modifier)
Returns a view of this service with the given option modifications applied.
The original service is not modified.
-
accounts
abstract AccountService accounts()
-
accountHolders
abstract AccountHolderService accountHolders()
-
authRules
abstract AuthRuleService authRules()
-
authStreamEnrollment
abstract AuthStreamEnrollmentService authStreamEnrollment()
-
tokenizationDecisioning
abstract TokenizationDecisioningService tokenizationDecisioning()
-
tokenizations
abstract TokenizationService tokenizations()
-
cards
abstract CardService cards()
-
balances
abstract BalanceService balances()
-
aggregateBalances
abstract AggregateBalanceService aggregateBalances()
-
disputes
abstract DisputeService disputes()
-
events
abstract EventService events()
-
transfers
abstract TransferService transfers()
-
financialAccounts
abstract FinancialAccountService financialAccounts()
-
transactions
abstract TransactionService transactions()
-
responderEndpoints
abstract ResponderEndpointService responderEndpoints()
-
webhooks
abstract WebhookService webhooks()
-
externalBankAccounts
abstract ExternalBankAccountService externalBankAccounts()
-
payments
abstract PaymentService payments()
-
threeDS
abstract ThreeDSService threeDS()
-
reports
abstract ReportService reports()
-
cardPrograms
abstract CardProgramService cardPrograms()
-
digitalCardArt
abstract DigitalCardArtService digitalCardArt()
-
bookTransfers
abstract BookTransferService bookTransfers()
-
creditProducts
abstract CreditProductService creditProducts()
-
externalPayments
abstract ExternalPaymentService externalPayments()
-
managementOperations
abstract ManagementOperationService managementOperations()
-
fundingEvents
abstract FundingEventService fundingEvents()
-
fraud
abstract FraudService fraud()
-
networkPrograms
abstract NetworkProgramService networkPrograms()
-
accountActivity
abstract AccountActivityService accountActivity()
-
apiStatus
abstract ApiStatus apiStatus(ClientApiStatusParams params, RequestOptions requestOptions)
-
apiStatus
ApiStatus apiStatus(ClientApiStatusParams params)
-
apiStatus
ApiStatus apiStatus(RequestOptions requestOptions)
-
close
abstract Unit close()
Closes this client, relinquishing any underlying resources.
This is purposefully not inherited from AutoCloseable because the client is long-lived and usually should not be synchronously closed via try-with-resources.
It's also usually not necessary to call this method at all. the default HTTP client automatically releases threads and connections if they remain idle, but if you are writing an application that needs to aggressively release unused resources, then you may call this method.
-
-
-
-