LEAP is excited to roll out new features on LEAP APIs and SDK for use by new and
existing integrators, prospectors, and individual developers who are looking to create
their own productivity tools while adding more value to LEAP’s ecosystem through the
integration of these tools.

LEAP API

New endpoints have been made available for developers to further enforce data
integrity and make the flow of information seamless and more efficient. Some examples
of these are the comprehensive Matter packages endpoint that returns the full matter
JSON along with its associated cards and the card’s associated persons and Card
packages endpoint (/api/v1/matters/packages/{matterId} and
/api/v1/cards/packages/{cardId})
that returns Card information.

Other enhancements also include modifications to an API endpoint to include new query
string filters, such as the changes implemented for the /api/v1/documentpacket
endpoint. These should allow developers to choose the proper filters to use when calling
these APIs.

Webhooks have also been improved by adding additional properties to existing ones
(as is the case with the Card webhooks) or implementing a new one altogether (the
newly-developed webhook when saving a Person’s information).

If you would like to know more about these latest features and are looking for in-depth
information about what has changed, please visit the LEAP API Reference.

LEAP HOST SDK

The LEAP Host SDK’s latest version (2.1.7) now supports more contexts. As a result, some
contexts were renamed and reorganized to be more descriptive and concise in relation
to their function.

An example would be renaming “sdk.context” to “sdk.leapContext” to indicate that the
context being used for the SDK is LEAP’s context. The context for the SDK’s
“leapContext” has also been made more generic so that developers wanting to get
information other than Matter-related items are able to do so. For example, you can
now get Card or Person information through the SDK’s context by doing something like
“sdk.leapContext.context.cardId” or “sdk.leapContext.context.personId” to get
a cardId or a personId.

If you have been using the previous contexts and would like to upgrade to the latest LEAP Host SDK version, please ensure that you have a plan in place to update all the references to
these contexts.

Please note that you should develop with the latest LEAP Desktop 2.3 or above in order
for these new SDK features to be supported.

For more information regarding the details of the SDK changes or if you want detailed
instructions on how to use the SDK, please visit the LEAP Host SDK and ensure you are selecting the most recent released version.

LEAP is always evolving to adapt to the business landscape’s ever-changing nature.
Please keep an eye on this blog for any announcements, changes, or new features that
will be implemented to LEAP’s developer tools.

If you have any questions regarding the APIs, the SDK, or LEAP’s developer tools in
general, you may e-mail the LEAP Integrations team.

GeneralLEAP Host SDKLEAP API