ThinkLP
Fortress Case API

Overview

ThinkLP is the Loss, Safety, and Risk Intelligence Platform for enterprise retail. These APIs let your own systems create and manage theft investigations, and the people, vehicles, and items involved in them. They run on Salesforce and present a single versioned REST API.

Every domain follows the same rules for authentication, response shapes, field metadata, and errors. Conventions is where those rules are written down.

The domains

DomainBase pathUse it to
Theft Cases/theft-casesManage cases and the records involved in them.
Vehicles/vehiclesManage canonical vehicles. Find one by plate.
Persons/personsManage canonical people. Search the directory.
Items/itemsManage canonical items. Find one by SKU.
Locations/locationsLoad and update locations by id. No create path.
Insights/insightsCreate cases from Frontier transactions. Read 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.

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 edit-only: no create path).
  • Insights — the case-linkage surface: create a theft case from Frontier point-of-sale transactions, list a case's linked transactions, and read transaction badges. It shares the authentication and error envelope, but uses its own request and response shapes.
  • Case Management (Legacy) — the superseded Case Management API, kept for existing integrations. Do not build against it. It uses its own vocabulary (/incidents rather than /theft-cases, snake_case fields rather than camelCase) and it does not return the { detail, fieldSpecs } envelope. Build new work on Theft and Banks above.

Where to start

Start with Getting Started to make your first authenticated call, then read Conventions and Field metadata before a specific domain.

Last modified on