Not logged in - Login
< back

API Overview

General Purpose of the Safe API

Tracker clients will generally use the API for the following tasks.

  1. POST or GET System User Accounts (User Admin)
  2. POST or GET Case Information
  3. POST or GET Person Information
  4. POST or GET New Item(s) Information
  5. GET Updated Items Information
  6. GET Chain of Custody Information for Items

Requirements for each API request

Each request made to the SAFE webAPI will require the following

  1. Valid URL (from list of available URLs below)
  2. User Token (from a Org Admin user)
  3. Valid OrgID # (See instructions below for getting this)
  4. Valid Office ID # (See instructions below for getting this)

Getting a valid User Token

  1. Go to Settings -> Users
  2. Select a (Org Admin) user in which to create a static token for, and select ‘Edit’ (Or you may want to create a new user for this process)
  3. At the bottom of the edit screen will be the token create section:
  4. Press ‘Generate’ to create the token.
  5. If you created a token for the currently logged in user, then you must logout before using the token.

Setting a Static License

In most cases, you are going to want to peg a license to the user that was created in the previous step. This will ensure that a license is available when the interface makes a call to the SAFE webAPI. If not license is available, then the API will respond with a message that no licenses are available.
  1. Go to Settings > License Allocation
  2. In the column ‘Reserved for Individual Users’ find the user you created for the API and then select the ‘No’ value to set a license.

What is your Org / Office ID

From within the SAFE interface, go to Settings > Offices to see your Org and Office ID.

How often should you POST or GET

Making an API call to the database more than once a minute may cause your account to be disabled. It is highly recommended that you make (or schedule) your call every 10 minutes or so. Please contact Tracker support if you need to POST or GET more often.

What we are trying to avoid here is pulling data from the API on a constant basis when not needed. If you are posting data and it happens quickly that is not a problem.

Testing the Tracker API

  1. Use Postman in Chrome (or any similar tool). The following example is using Postman:
  2. Header Fields
    1. Accept application/json – required field
    2. Content-Type application/x-www-form-urlencoded – required field
    3. Authorization – This field requires the word ‘Bearer’ followed by a single space and then the static token that was created.
    4. OrganizationId – the organization ID to use (Found in Settings > Offices)
    5. OfficeId – the office ID to use (Found in Settings > Offices)
    6. StaticToken – tells the API that the bearer token is static
  3. Once these fields are in place, select ‘Send’ and verify that an item was returned (if one exists).

make sure you have a valid item in the system before you try to select one from the webAPI or you will get no results and it might look like something is wrong.

POST or GET from API

GET Item (Including Item Updates)

This API endpoint allows for polling of all items (and updates) in the system in sequential order. Every item, or update, will be applied an ascending ID number. Program your system to poll for ID 1 and continue until you do not get a response. Once there is no response you will store the last ID that was good and start at that number for your next pool. With this you are always keeping up with new items and updates to those items.


Where X = SeqOrgItemHistoryID of item

Important Objects Returned

  • SeqOrgItemHistoryID: This is the ascending ID for each item and update. Start with1.
  • historyType ["Create" or "Update"] Create being a new entry and Update being a update to the item.

SeqUpdateOrgX Example Screenshot


Used to post a single item to the system. Multiple item entries will simply loop this process.

GET (Specific) Case

Used to return all results of a specific (single) case.

Where X = Case number entered into the system by the user.

Example Screenshot

GET (Specific) Item

Used to return all results of a specific (single) item.
API URL ={id}

Where {id} = Item ID found in Get Case area or other API searches.

GET (All) Item(s) (In a specific case)

Used to return all results of a specific (single) item.
API URL ={id}/items

Where {id} = Case ID found in GET Case API above.

Case POST (Create)

Used for posting a new Case record to the system.

See Info Page for all necessary info to submit to this endpoint.

Case Edit (Edit existing case)

Used for posting a updated Case record to the system.[casenumber]

See Info Page for all necessary info to submit to this endpoint. )

Person POST (Create)

Used for posting new Person, Address and/or Entry to a Case.

See Info Page for all necessary info to submit to this endpoint.

Person POST (Update existing Person)

Used for updating an existing person entry.

Where X = ID of Person

See Info Page for all necessary info to submit to this endpoint.

POST Existing Person to Existing Case

Used for posting an existing Person to an existing Case.

See Info Page for all necessary info to submit to this endpoint.

GET People in a Case

Used to get a list of all Persons tied to a specific case.

Where X = the "PrimaryCaseID"

FYI - The API for Retrieving Specific Case Data will be need to also be used so that you can get the PrimaryCaseID to enter into this URL.

Example Screenshot

GET CSV list of all Persons in Org

GET Chain of Custody

Returns chain of custody for a specific item.

Where X = the "id" value of the item which is provided in the SeqUpdateOrgID

Important: Do NOT use any nested ID's, use the root level ID.

Example Screenshot

POST User Administration

Used for creating a User in User Administration

Important: Users are required to be unique across the entire system. If a duplicate email is found it will notify you in the response.

Example Screenshot