Builders overview

Namespace and purpose

The Imoli\EflLeasingSdk\Builder namespace contains fluent builders for the main request models used when calling the EFL Leasing Online API. They provide a more readable and less error‑prone way of constructing complex payloads than assembling nested arrays by hand.

Builders are most often used together with EflClient methods from the clients section and the corresponding models from the models section.

Groups of builders

• Calculation – basket and offer‑related payloads:
  • AssetToCalculationBuilder – builds AssetToCalculation (basket for basic offer calculation),
  • OfferItemBuilder – builds OfferItem entries for the basket,
  • ItemDetailBuilder – builds ItemDetail metadata items for offer items.
• Customer – company and customer‑related payloads:
  • CustomerDataBuilder – builds CustomerData for /Customer/PostCustomerDataForLon,
  • CompanyBuilder – builds Company with contact details, addresses and statements,
  • PersonBuilder – builds Person linked to the company,
  • AddressBuilder – builds Address entries,
  • EmailAddressBuilder – builds EmailAddress entries,
  • PhoneBuilder – builds Phone entries,
  • CustomerDataStatementBuilder – builds CustomerDataStatement entries,
  • IdentityDocumentBuilder – builds IdentityDocument entries.
• Lead – contact / lead‑related payloads:
  • ContactDataBuilder – builds ContactData for /Lead/SendContactForm,
  • ProspectBuilder – builds Prospect data,
  • StatementLeadBuilder – builds StatementLead consent entries.
• Verification – identity verification payloads:
  • VerificationInitializationParamsBuilder – builds VerificationInitializationParams,
  • VerificationResultBuilder – builds VerificationResult,
  • PostVerificationCodeBuilder – builds PostVerificationCode.

When to use builders

Use builders when:

• you want a fluent API instead of constructing nested arrays or calling large model constructors directly,
• you need to enforce required fields – most builders validate required data in build() and throw a \LogicException if it is missing,
• you want a single place where default values and composition rules are encoded.

You can always construct models directly (see the models section), but builders are recommended for application‑level code that prepares payloads for EflClient.

Related sections

• EflClient overview
• Models overview