Postman collection · LendEasy Docs

Import a collection generated from the public OpenAPI contract, select an isolated environment, and run production-shaped LendEasy workflows.

Download

The collection is generated from the same OpenAPI document as the API reference. Its folders, methods, paths, example bodies, and permissions therefore stay aligned with the published contract.

Import and authorize

In Postman, choose Import and add the collection plus the Sandbox environment.
Select LendEasy Sandbox in the environment selector.
Store clientId and clientSecret as secret current values in your personal environment.
Send Authentication → Exchange client credentials.
Save the returned access_token as the secret token value.

Collection requests inherit Authorization: Bearer {{token}}. Add a collection-level LendEasy-Tenant header with your tenant (Sandbox examples use demo-lender) — Lending Core requests reject calls without it. Mutating requests also carry Idempotency-Key: {{$guid}}; the key is optional on Lending Core requests, so replace the GUID with a stable operation key (1–50 characters) when testing a retry.

Environment variables

Variable	Sandbox example	Purpose
`baseUrl`	`https://sandbox.api.lendeasy.ai`	API origin; no trailing slash.
`authUrl`	`https://auth.lendeasy.ai/oauth2/token`	Token exchange.
`token`	secret current value	Short-lived access token.
`customerId`	`412`	Customer used by the portfolio examples.
`loanId`	`7204`	Harbor Personal Loan.
`caseId`	`case_HBR_COL_51`	Harbor collections matter.
`instrumentId`	`704`	Masked, verified customer instrument.

Postman scripts can save IDs from create responses, but the collection never silently changes Production variables.

Recommended smoke sequence

Run these requests in order to validate credentials, idempotency, state, and money simulation:

Customers → Create a customer; resend with the same key and confirm the replay returns the original result with x-served-from-cache: true.
Loans → Create a loan application with command=calculateLoanSchedule; inspect every installment and totals without persisting anything.
Loans → Create a loan application (no command), then Retrieve a loan with associations=repaymentSchedule.
Loans → Retrieve a loan summary; compare its payoff projection and APR disclosure blocks with the guides.
Cases → Create a case; read its timeline and first tasks.
Compliance decisions → Evaluate contact eligibility; inspect cited rules and fact freshness.

Team safety

Exported environments omit current secret values. Keep credentials in a personal environment or your secrets manager, not in a synced team environment. Use a separate OAuth client for automated collection tests so it can be rotated or revoked without affecting applications.

The collection is a convenient client, not a second contract. If a saved request ever differs from the API reference, regenerate it from the published OpenAPI document.