# LeaseAccelerator

> Enterprise lease lifecycle automation for equipment and real estate leases, part of insightsoftware.
> LeaseAccelerator combines lease accounting, lease administration, and asset lifecycle intelligence in a
> single platform, automating compliance with ASC 842, IFRS 16, and GASB 87 through a full lease
> sub-ledger that protects the general ledger.

LeaseAccelerator exposes one API. It is not a modern JSON REST API: it is REST-addressed with XML Remote
Procedure Call payloads, secured by SAML2 against the customer's own identity provider. Every operation
is a POST; the operation is chosen by URL path segment; all structure lives in an XML envelope; and
failures come back inside a 200 response, not as HTTP status codes.

Generated by the API Evangelist enrichment pipeline (2026-07-19) from LeaseAccelerator's published
developer documentation. Not affiliated with or endorsed by LeaseAccelerator or insightsoftware.

## Getting started

- [Application Programming Interface (API) for Developers](https://docs-leaseaccelerator.insightsoftware.com/hc/en-us/articles/33895814655245-Application-Programming-Interface-API-for-Developers): the developer guide — authentication, URL structure, request and response envelopes.
- [API Methods](https://docs-leaseaccelerator.insightsoftware.com/hc/en-us/articles/33895853166093-API-Methods): the reference for all 43 operations, with per-operation request and response payloads and a data ontology.
- [Integration Methods](https://docs-leaseaccelerator.insightsoftware.com/hc/en-us/articles/33895858264717-Integration-Methods): what the API is used for, and the file-based (SFTP) alternative.
- [LeaseAccelerator Help](https://docs-leaseaccelerator.insightsoftware.com/hc/en-us/): full documentation home.

## Authentication

There are no API keys and no OAuth. You must already be integrated with LeaseAccelerator's Single Sign-On
solution via a SAML2-compliant identity provider.

1. Submit a SAML2 ECP GET request to `https://www.leaseaccelerator.com/auth/api`, identifying your
   identity provider and the credentials of a user federated for access in LeaseAccelerator.
2. The response is a text security token.
3. Send that token as the `token` form field on every API POST.

The token carries the federated user's Access Control role and ScopeOfAccess. There is no narrower
credential.

## Calling an operation

POST to `https://{environment}.leaseaccelerator.com/lease_accelerator/api/LeaseAccelerator/{operation}`,
where `environment` is `www` for production (contact LeaseAccelerator Support for other environments).

Required form fields: `token` (the security token) and `file` (the XML `<APIRequest>` document).
`AttachFile` additionally requires `filetoattach`, the file itself.

Request envelope:

    <APIRequest>
      <Request>
        <RequestId>your-unique-id</RequestId>
        <WarningPolicy>Stop|Skip|Ignore</WarningPolicy>
        <ErrorPolicy>Stop|Skip</ErrorPolicy>
      </Request>
      <Payload>operation-specific XML</Payload>
    </APIRequest>

Response envelope:

    <APIResponse>
      <Response>
        <RequestId>your-unique-id</RequestId>
        <Status>0</Status>
        <Context>Ok</Context>
      </Response>
      <Payload>operation-specific XML</Payload>
    </APIResponse>

`Status` of 0 and `Context` of `Ok` mean success. Any other `Status` is an error described by `Context`.
Check these fields — do not rely on the HTTP status code.

`ErrorPolicy` and `WarningPolicy` are the batch-failure contract. `Stop` (the ErrorPolicy default) halts
processing and rolls back everything done so far for the request. `Skip` skips only the offending record
in a multi-record request. `Ignore` (the WarningPolicy default) continues past warnings, which are still
reported in the response.

## Idempotency

There is no idempotency-key header. Instead, write operations accept an `importKey` (your own external
identifier) paired with `ImportedFrom` (a name for your system, max 32 characters). If the
LeaseAccelerator surrogate id is omitted but `importKey` resolves to a known record, that record is
updated rather than duplicated. Always send a stable `importKey` so a retried import converges instead of
creating duplicates, and pair it with `ErrorPolicy=Stop` so a failed batch leaves no partial state.

## The 43 operations

Portfolio and deals: ImportDeals, ImportantClassifyDeals (import plus the automated classification
engine), ModifyDealImport, ImportAssets, UpdateAssets, BulkParticipantUpdate.

Events: RecordEvent, RecordAssetEvent, RollbackEvent (only end-of-term and payment adjustment events can
be rolled back), GetEventsforDeal, GetParticipantsForDealArtifacts.

Financials: ImportDisbursements, ImportExchangeRates, ImportInvoicedExpenses, ImportLesseeRates,
ImportPaidExpenses, ImportPaymentAdjustments.

Reference and master data: AddUpdateAddress, AddUpdateCompany, AddUpdateCostCenters, AddUpdatePerson,
DefineReferenceData, ImportAddresses, ImportCompanies, ImportPeople.

Documents: AddUpdateArtifact, AttachFile, CaptureDocumentId (communicates accepted journal entries from
the ERP back to LeaseAccelerator), GetDocumentsforDeal.

Search: FindDeals, FindAssets, FindContacts. These take a `<Criteria>` element; there is no pagination.

Reporting: Generate (synchronous), GenerateAsynch (returns a request id), GetReportStatus,
GetReportFile.

Process status: GetLatestClose, GetBookingStatus, GetSweepingStatus, GetReportableStatus. Call
GetReportableStatus before running a report to check that sweeping and booking are settled.

SSO user provisioning: FederateUser, UpdateUser, RevokeUser. Only for environments where SSO is in use.

## What this API does not have

- No SDKs or client libraries in any language, and no public GitHub organization.
- No webhooks or event subscriptions. Asynchronous work is polled; file imports notify by email.
- No pagination, no field expansion, no sparse fieldsets.
- No published rate limits.
- No OAuth scopes, no OIDC discovery, no `/.well-known/` documents, no security.txt.
- No RFC 9457 problem details, and no enumerated registry of non-zero `Status` codes.
- No API versioning. Operations track the platform release (currently 26.3); changes appear in dated
  release notes.

## Artifacts in this repository

- openapi/leaseaccelerator-api-openapi.yml — the 43 operations as OpenAPI 3.1
- authentication/leaseaccelerator-authentication.yml — the SAML2 ECP flow
- conventions/leaseaccelerator-conventions.yml — cross-cutting request/response semantics
- errors/leaseaccelerator-problem-types.yml — the error envelope and the import validation message catalog
- data-model/leaseaccelerator-data-model.yml — the entity graph
- lifecycle/leaseaccelerator-lifecycle.yml — versioning, retirements, status page
- changelog/leaseaccelerator-changelog.yml — structured release notes
- conformance/leaseaccelerator-conformance.yml — standards conformance, including ASC 842 / IFRS 16 / GASB 87
- security/ — domain security probe and the insightsoftware trust center
- skills/ — packaged agent skills for the marquee flows

## Company

- [LeaseAccelerator product page](https://insightsoftware.com/leaseaccelerator/)
- [Support](https://help.insightsoftware.com/s/)
- [Status](https://status.insightsoftware.com/)
- [Trust center](https://trust.insightsoftware.com/)
- [Pricing enquiry](https://insightsoftware.com/request-a-price/)

LeaseAccelerator was acquired by insightsoftware on 11 July 2024. leaseaccelerator.com and
explore.leaseaccelerator.com now redirect to insightsoftware.com/leaseaccelerator/, but the API host
www.leaseaccelerator.com/lease_accelerator/ is unchanged and live.