The LightBox Identifier is a persistent and universal identifier for our data that creates powerful connections to the LightBox information model. It is critical to have an ID that is persistent, reliable, and trusted, to ensure consistent implementation of our data.
Connect data across the LightBox property graph, helping gain comprehensive insights.
Are unique and never reused, allowing you to traverse object changes over time.
The LightBox ID is used to navigate the LightBox property graph.
Examples:
Using a LightBox Parcel ID - return all addresses on that parcel record.
Using a LightBox Structure ID - return all address on that structure record.
Using a LightBox Parcel ID - return all structures that are on that parcel record.
Using a LightBox Assessment ID - return all addresses related to that assessment record.
LightBox ID in the API
LightBox IDs are found throughout our APIs. If you have any one of the IDs you can use _on/id endpoints to retrieve data associated with that id.
Note:
While we reference name IDs within this document, our ID fields names have a prefix of _LID (LightBox ID). When referencing them in our SmartFabric product you will see them with these field names:
ASSESSMENT_LID
PARCEL_LID
ADDRESS_LID
BUILDING_LID
etc.
LightBox API resources that include the LightBox ID
Geocoding
Addresses
Structure footprints
Parcel boundaries
Assessment
Transactions
Location
Pro Tip:
LightBox IDs are not only available through the LightBox APIs. LightBox IDs are also delivered with our data via on-site delivery; this allows the use of the LightBox RESTful APIs, and the ability to link resources returned through the API back to data that you are storing locally, providing a reliable link mechanism.
LightBox ID in SmartFabric
LightBox IDs are also populated within each of the SmartFabric products. This provides the same ID graph that is found in the APIs and because these IDs are persistent you can use them interchangeably between onsite data and through the API.
Pro Tip:
Many of our clients and partners subscribe to a SmartFabric product. They typically have data that they source with address information that they would like to link to the SmartFabric records. To do this they will use the LightBox Geocoder, sending in the address and retrieving the LightBox IDs to achieve this join.
If your data only has a APN number and no address, don't worry. LightBox has a APN Lookup service that will also return the LIDs.
The LightBox Identifier is a permanent and universal identifier for our data that creates powerful connections to LightBox’s information model.
API stands for Application Programming Interface. An API can be used to deliver data, through code, to your applications. LightBox has APIs that deliver our SmartFabric and many other data sets.
A RESTful API is an application programming interface (API) that uses HTTP requests to access and use data. REST stands for representational state transfer.
API stands for Application Programming Interface. An API can be used to deliver data, through code, to your applications. LightBox has APIs that deliver our SmartFabric and many other data sets.
SmartFabric is LightBoxs' robust property data package. SmartFabric includes nationwide parcels, addresses, assessment, structures and all the relationship tables to tie it all together.
API stands for Application Programming Interface. An API can be used to deliver data, through code, to your applications. LightBox has APIs that deliver our SmartFabric and many other data sets.
The LightBox Identifier is a permanent and universal identifier for our data that creates powerful connections to LightBox’s information model.
Assessor Parcel Number (APN) or tax account number is an ID that is assigned to a property by the tax assessor/tax authority that uniquely identifies that property.
LightBox Identifier (LID) is a permanent and universal identifier for our data that creates powerful connections to LightBox’s information model. It is critical to have an ID that is persistent, reliable, and trusted, to ensure consistent implementation of our data.
Was this article helpful?
Thank you for your feedback! Our team will get back to you