/api/v1/records
Query Parameters
Type of records to retrieve. Must be URL-encoded. The possible values vary depending on how the community is configured in Forerunner, but one common value is
Preliminary Damage Assessment.Find record via it’s
externalSystemId. Since this value is unique, this will return exactly zero or one entry in the records array. externalSystemId can be set via the Submit SI/SD or Update SI/SD API or through an integration with an external data source (such as Accela).Used for getting the next page in the sequence. See
pageInfo for pagination details.Filter records created strictly after this timestamp (exclusive). Provide in ISO 8601 format (e.g.,
2024-09-25T21:33:10Z).Response
Array of record objects (25 per page)
Pagination information. See Pagination.
Best Practices
Pagination for large datasets
Pagination for large datasets
Always paginate through results when querying record types with many entries. Don’t assume all data will fit in a single response.
Incremental synchronization
Incremental synchronization
Use the
createdFrom parameter to implement efficient incremental syncs rather than fetching all records every time. Store the last sync timestamp and use it for subsequent requests.URL encoding record types
URL encoding record types
Always URL-encode the
recordType parameter, especially for types with spaces or special characters.Handle varying data structures
Handle varying data structures
Different record types have different data structures. Build flexible parsers that can handle type-specific fields based on the
recordType value.