LendKey Developer Portal

Le

LendKey E-Sign API (via Kong Gateway)

# LendKey E-Sign API - Kong Gateway Documentation ## Overview The LendKey E-Sign API provides endpoints for creating and managing electronic signature contracts using DocuSign. This API is accessed through Kong Gateway, which handles authentication via OAuth2. ## Authentication All requests to this API require OAuth2 authentication through Kong Gateway. ### Step 1: Get OAuth2 Token Before calling any endpoint, you must obtain an access token: **Production Environment:** ```bash curl -X POST https://api.lendkey.com/esign/oauth2/token \ -d "grant_type=client_credentials" \ -d "client_id=YOUR_CLIENT_ID" \ -d "client_secret=YOUR_CLIENT_SECRET" ``` **Response:** ```json { "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...", "token_type": "bearer", "expires_in": 7200 } ``` ### Step 2: Use Token in API Calls Include the access token in the `Authorization` header: ``` Authorization: Bearer YOUR_ACCESS_TOKEN ``` **Token Lifetime:** 2 hours (7200 seconds) ## Base URLs (Kong Gateway) | Environment | Kong Base URL | Backend Kubernetes Service | |------------|---------------|---------------------------| | **Production** | `https://api.lendkey.com/esign` | `main-esign-kotlin.ci.lkeyprod.com` | ## How Kong Routes Requests When you call Kong: ``` https://api.lendkey.com/esign/applications ``` Kong: 1. Validates your OAuth2 token 2. Strips the `/esign` prefix 3. Forwards to: `http://main-esign-kotlin.ci.lkeyprod.com/applications` You don't need to manage any backend authentication - Kong handles everything! ## Getting Started 1. **Get Credentials:** Contact your Kong admin or use the Kong Developer Portal 2. **Get Token:** Use the OAuth2 token endpoint for your environment 3. **Call API:** Use the token in the Authorization header 4. **Refresh:** Get a new token every 2 hours

v0.1

Pa

Partner Integration Internal API - Production

# Partner Integration Internal API ## Overview The Partner Integration Internal API provides endpoints for logging API requests and responses for monitoring and debugging purposes. This is an internal API used by the loan origination service and other internal services. ## Authentication All requests to this API require OAuth2 authentication. ### Step 1: Get OAuth2 Token Before calling any endpoint, you must obtain an access token: **Production Environment:** ```bash curl -X POST https://api.lendkey.com/lo_partnerintegrationinternalapi/oauth2/token \ -d "grant_type=client_credentials" \ -d "client_id=YOUR_CLIENT_ID" \ -d "client_secret=YOUR_CLIENT_SECRET" ``` **Response:** ```json { "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...", "token_type": "bearer", "expires_in": 7200 } ``` ### Step 2: Use Token in API Calls Include the access token in the `Authorization` header: ``` Authorization: Bearer YOUR_ACCESS_TOKEN ``` ## Base URLs - **API URL**: `https://api.lendkey.com/lo_partnerintegrationinternalapi`

v1

In

Integration API

This API collection represents the integration APIs LendKey offers for 3rd party dependencies/integrations, and is for dev/qa use only. External connections are not prohibited following this document.

v1.0.0

Tr

Treasury Management API (via Kong Gateway)

# Treasury Management API - Kong Gateway Documentation ## Overview The Treasury Management API provides endpoints for managing loan inventory, disbursements, payments, and treasury operations. This API is accessed through Kong Gateway, which handles authentication via OAuth2. ## Authentication All requests to this API require OAuth2 authentication through Kong Gateway. ### Step 1: Get OAuth2 Token Before calling any endpoint, you must obtain an access token: **QA Environment:** ```bash curl -X POST https://api.lkeyqa.com/TreasuryMgmtQa/oauth2/token \ -d "grant_type=client_credentials" \ -d "client_id=YOUR_CLIENT_ID" \ -d "client_secret=YOUR_CLIENT_SECRET" ``` **DEV Environment:** ```bash curl -X POST https://api.lkeyqa.com/TreasuryMgmtDev/oauth2/token \ -d "grant_type=client_credentials" \ -d "client_id=YOUR_CLIENT_ID" \ -d "client_secret=YOUR_CLIENT_SECRET" ``` **Staging Environment:** ```bash curl -X POST https://api.lkeystaging.com/TreasuryMgmt/oauth2/token \ -d "grant_type=client_credentials" \ -d "client_id=YOUR_CLIENT_ID" \ -d "client_secret=YOUR_CLIENT_SECRET" ``` **Production Environment:** ```bash curl -X POST https://api.lendkey.com/TreasuryMgmt/oauth2/token \ -d "grant_type=client_credentials" \ -d "client_id=YOUR_CLIENT_ID" \ -d "client_secret=YOUR_CLIENT_SECRET" ``` **Response:** ```json { "access_token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9...", "token_type": "bearer", "expires_in": 7200 } ``` ### Step 2: Use Token in API Calls Include the access token in the `Authorization` header: ``` Authorization: Bearer YOUR_ACCESS_TOKEN ``` **Token Lifetime:** 2 hours (7200 seconds) ## Base URLs (Kong Gateway) | Environment | Kong Base URL | Backend OutSystems URL | |------------|---------------|------------------------| | **DEV** | `https://api.lkeyqa.com/TreasuryMgmtDev` | `https://lendkey-dev.outsystemsenterprise.com` | | **QA** | `https://api.lkeyqa.com/TreasuryMgmtQa` | `https://os.lkeyqa.com` | | **Staging** | `https://api.lkeystaging.com/TreasuryMgmt` | `https://os.lkeystaging.com` | | **Production** | `https://api.lendkey.com/TreasuryMgmt` | `https://os.lendkey.com` | **Note:** Route names are case-insensitive (`/TreasuryMgmt`, `/treasurymgmt`, `/TREASURYMGMT` all work) ## How Kong Routes Requests When you call Kong: ``` https://api.lkeyqa.com/TreasuryMgmtQa/v1/createLoan ``` Kong: 1. Validates your OAuth2 token 2. Strips the `/TreasuryMgmtQa` prefix 3. Adds OutSystems authentication headers (X-Auth-Key, X-Auth-AppId) 4. Forwards to: `https://os.lkeyqa.com/TreasuryManagement_API/rest/v1/createLoan` You never need to manage OutSystems credentials directly! ## Getting Started 1. **Get Credentials:** Contact your Kong admin or use the Kong Developer Portal 2. **Get Token:** Use the OAuth2 token endpoint for your environment 3. **Call API:** Use the token in the Authorization header 4. **Refresh:** Get a new token every 2 hours

vv1