What the ThinkLP APIs are, how they're organized, and where to start.
ThinkLP is the Loss, Safety, and Risk Intelligence Platform for enterprise
retail. These APIs open that platform to your own systems: create and manage
theft investigations and the people, vehicles, and items involved in
them, programmatically. They're built on Salesforce and exposed as a single
versioned REST API.
The domains
| Domain | Base path | Use it to |
|---|---|---|
| Theft Cases | /theft-cases | Manage cases and the records involved in them. |
| Vehicles | /vehicles | Manage canonical vehicles; look them up by plate. |
| Persons | /persons | Manage canonical people; search the directory. |
| Items | /items | Manage canonical items; look them up by SKU. |
| Locations | /locations | Look up canonical locations by id (read-only). |
| Insights | /insights | Create theft cases from Frontier transactions; look up linkage badges. |
A theft case links to vehicles, persons, and items through junction
records (Involved Vehicle, Involved Person, Case Item) that carry case-specific
context. Vehicles, persons, and items are canonical records that can be
reused across many cases. See the Glossary for the full
vocabulary.
One consistent contract
The theft-case and canonical domains follow the same rules, so what you learn on
one applies across them:
- Authentication — OAuth 2.0 Client Credentials; send a bearer token on every
request. See Authentication. - Response shapes — canonical retrieve/create/update return a
{ detail, fieldSpecs }envelope; lookups return a flat record; search
returns an array. See Conventions. - Field metadata —
fieldSpecsdescribes every field so you can render and
validate forms dynamically. See Field metadata. - Errors — failures return a
{ code, message }envelope; branch oncode.
See Errors.
The Insights endpoints share the same authentication and { code, message }
error envelope, but are a purpose-built case-linkage surface and use their own
request/response shapes rather than the { detail, fieldSpecs } envelope. See
Conventions.
How this reference is organized
- Theft — the theft-case endpoints, grouped by what they act on: Cases, Case
Items, Involved Persons, Involved Vehicles. - Banks — the canonical domains: Persons, Vehicles, Items, Locations
(Locations is read-only). - Insights — the case-linkage surface: create a theft case from Frontier
point-of-sale transactions, list a case's linked transactions, and look up
transaction badges.
Where to start
New here? Start with Getting Started to make your first
authenticated call, then skim Conventions and
Field metadata before diving into a specific domain.