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. Servicing request names end in [Implemented] or [Future-facing], so existing product-direction APIs remain available without looking like current runtime routes.

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.

Ordinary client requests inherit Authorization: Bearer {{token}} and carry LendEasy-Tenant: {{tenant}}. Mutating requests carry Idempotency-Key: {{$guid}}; replace the GUID with a stable 1–50 character operation key when testing replay on the Lending Core or implemented Servicing Plane. Future-facing operations keep their own documented key constraints.

Connector callbacks override the collection bearer setup. Channel events send gatewaySignature as X-LendEasy-Gateway-Signature; voice callbacks send the dispatch-bound dispatchToken as X-LendEasy-Voice-Task-Token. Those values come from the configured connector journey, not from a human OAuth session.

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.
`tenant`	`demo-lender`	Tenant registry selector sent as `LendEasy-Tenant`.
`token`	secret current value	Short-lived access token.
`customerId`	`412`	Customer used by the portfolio examples.
`loanId`	`7204`	Harbor Personal Loan.
`caseId`	`1001`	Current numeric servicing case ID.
`instrumentId`	`704`	Masked, verified customer instrument.
`dispatchToken`	secret current value	Dispatch-bound voice connector token.
`gatewaySignature`	secret current value	Signature for a configured channel gateway event.

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 [Implemented]; then Retrieve a case workspace [Implemented] and inspect its tasks and allowed actions.
Tasks → Reserve the next eligible task [Implemented]; use a stable key and confirm the reservation belongs to the authenticated worker.
Servicing reports → Read the compliance report [Implemented]; confirm the bounded projection is visible with the expected permission.

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. Do not run a [Future-facing] request against the current runtime. If a saved request ever differs from the API reference, regenerate it from the published OpenAPI document.