Sign In

Contacts

Written by Jarad on March 20, 2023

FastBound provides API methods for retrieving a list of contacts, retrieving a single contact by FastBound identifier or External Identifier, creating new contacts, updating a contact, and deleting a contact.

Generally speaking, storing FastBound Identifiers is more efficient because you can infer from the presence of the ID whether the record exists in FastBound, and you know the ID needed for all API calls.

External Identifiers work great if you can’t store FastBound Identifiers but may require additional API calls to retrieve the FastBound Identifiers for some API calls.

FastBound also provides API methods for managing contact licenses, including getting a list of licenses, getting a single license, updating a license, or deleting a license.

Some Contact API methods return additional information in HTTP response headers.

FastBound’s Acquisitions/CreateAndCommit and Dispositions/CreateAndCommit API calls accept item and contact details in a single request and response. In these API calls, contactId and contactExternalId can only reference an already-created contact, or you can create a new contact with the nested contact object.

A FastBound contact can be an FFL/licensee, an individual, or an organization (i.e., police departments). Specific fields are required depending on the type of contact:

  • If your contact represents an FFL/licensee, fflNumber, fflExpires, licenseName, tradeName are required. sotein, sotClass, and businessType are optional.

  • If your contact represents an organization, organizationName is required.

  • If your contact represents an individual, firstName and lastName are required. middleName is optional.

All contact types require premiseAddress1, premiseCity, premiseState, premiseZipCode, and premiseCountry. Optional fields omitted from create and update requests will be set to null. If you want to erase a value, set that property to null (vs. an empty string).

Sign In