> ## Documentation Index > Fetch the complete documentation index at: https://withforerunner.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # List Records > Returns records of a single record type, 25 per page. Page through the results rather than assuming one response holds them all, and URL-encode `recordType` — most type names contain spaces. For an incremental sync, store the timestamp of your last run and pass it as `createdFrom` instead of refetching everything. Each record's `data` keys follow that record type's configuration in your account, so parse them defensively rather than against a fixed shape. ## OpenAPI ````yaml /developers/v1/openapi.json get /api/v1/records openapi: 3.1.0 info: title: Forerunner Integration API v1 version: 1.0.0 description: >- Read and write floodplain data in Forerunner. This is the v1 contract; each version is documented separately and evolves on its own. v1 is the current version. It covers files, properties, records, and SI/SD, and is the one to build against. Its record endpoints handle `Log` records only; use v2 for any other record type. Every request needs an `Authorization: Bearer ` header. List endpoints return 25 results per page; page through them with `page` and read `pageInfo` for the totals. Every JSON response carries an `errors` array, empty when the request succeeded; the `401`, `403`, and `429` responses are plain text or HTML instead. Develop against the staging server, which is a separate account with separate API keys and separate data. Requests are rate limited per IP at the CDN. A request over the limit is answered with a `429` and an HTML body, not the JSON error shape. servers: - url: https://app.withforerunner.com description: Production - url: https://app.staging.withforerunner.com description: Staging, for development and testing security: - bearerAuth: [] tags: - name: Files description: >- Upload, retrieve, and update documents such as Elevation Certificates and permits. - name: Properties description: Query the properties in your account. - name: Records description: >- Read, create, update, and delete `Log` records. Other record types are available on v2. - name: SI/SD description: >- Track substantial improvement and substantial damage against your community's thresholds. paths: /api/v1/records: get: tags: - Records summary: List Records description: >- Returns records of a single record type, 25 per page. Page through the results rather than assuming one response holds them all, and URL-encode `recordType` — most type names contain spaces. For an incremental sync, store the timestamp of your last run and pass it as `createdFrom` instead of refetching everything. Each record's `data` keys follow that record type's configuration in your account, so parse them defensively rather than against a fixed shape. operationId: listRecords parameters: - in: query name: recordType schema: type: string description: >- Record type to return, URI-encoded, such as `Log` or `Preliminary Damage Assessment`. Must match a record type configured for your account; the available types vary by account, so check with your customer success manager. example: Preliminary Damage Assessment required: true description: >- Record type to return, URI-encoded, such as `Log` or `Preliminary Damage Assessment`. Must match a record type configured for your account; the available types vary by account, so check with your customer success manager. - in: query name: createdFrom schema: description: >- Return only records created strictly after this ISO 8601 timestamp. Use it to sync incrementally. example: '2024-03-01T00:00:00.000Z' type: string format: date-time pattern: >- ^(?:(?:\d\d[2468][048]|\d\d[13579][26]|\d\d0[48]|[02468][048]00|[13579][26]00)-02-29|\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\d|30)|(?:02)-(?:0[1-9]|1\d|2[0-8])))T(?:(?:[01]\d|2[0-3]):[0-5]\d:[0-5]\d(?:\.\d+)?(?:Z))$ description: >- Return only records created strictly after this ISO 8601 timestamp. Use it to sync incrementally. - in: query name: page schema: type: integer minimum: 1 description: 1-based page number. List endpoints return 25 results per page. example: 1 - in: query name: externalSystemId schema: type: string minLength: 1 description: >- Return only items your system recorded under this identifier. Files and SI/SD records enforce uniqueness, so those match at most one; `Log` records do not. It can be set when creating or updating the item, or by an integration with an external system such as Accela. example: EC-2024-0417 responses: '200': description: Success. `errors` is empty. content: application/json: schema: $ref: '#/components/schemas/V1SubmissionListResponse' example: errors: [] pageInfo: page: 1 pageSize: 25 totalCount: 67 totalPages: 3 records: - id: c7d8e9f0-1a2b-4c4d-8e6f-7a8b9c0d1e2f externalSystemId: PDA-2024-0417 data: {} property: id: a1b2c3d4-e5f6-4890-abcd-ef0123456789 address: 123 Main St, Springfield, IL 62701 url: >- https://demoville.app.withforerunner.com/map?propertyId=a1b2c3d4-e5f6-4890-abcd-ef0123456789&tab=overview publicURL: >- https://demoville.withforerunner.com/properties/a1b2c3d4-e5f6-4890-abcd-ef0123456789 coordinates: - 39.7817 - -89.6501 '400': description: The request failed validation. `errors` names each field at fault. content: application/json: schema: anyOf: - $ref: '#/components/schemas/V1SubmissionListResponse' - $ref: '#/components/schemas/APIResponse' example: errors: - message: Required field: recordType records: [] '401': description: >- Missing or invalid API key. The body is plain text, not the JSON error shape. '403': description: >- Blocked by our web application firewall, which answers with an HTML body rather than the JSON error shape. Most often caused by a client sending a `PostmanRuntime`, `python-requests`, or `HeadlessChrome` `User-Agent`; clear that header and retry. '429': description: >- Too many requests from your IP. Rate limiting is applied at the CDN, so the body is HTML rather than the JSON error shape. Back off and retry. components: schemas: V1SubmissionListResponse: type: object properties: errors: type: array items: $ref: '#/components/schemas/APIError' description: >- Empty when the request succeeded. Otherwise one entry per failure, and the resource fields on the response are empty: `null` for single resources, `[]` for lists, with `pageInfo` omitted. example: [] pageInfo: $ref: '#/components/schemas/V1PageInfo' records: type: array items: $ref: '#/components/schemas/V1Record' description: Up to 25 records for the requested page. required: - errors - records additionalProperties: false APIResponse: type: object properties: errors: type: array items: $ref: '#/components/schemas/APIError' description: >- Empty when the request succeeded. Otherwise one entry per failure, and the resource fields on the response are empty: `null` for single resources, `[]` for lists, with `pageInfo` omitted. example: [] required: - errors additionalProperties: false description: Every response carries an `errors` array alongside its resource fields. APIError: type: object properties: message: type: string description: Human-readable description of what went wrong. example: Required field: type: string description: The request field that caused the error, as a dot-separated path. example: data.type required: - message - field additionalProperties: false description: A single validation or processing failure. V1PageInfo: type: object properties: page: type: number description: The page that was returned. example: 1 pageSize: type: number description: Results per page. Always 25. example: 25 totalCount: type: number description: Total results matching the filters, across all pages. example: 67 totalPages: type: number description: Number of pages available. example: 3 required: - page - pageSize - totalCount - totalPages additionalProperties: false description: >- Pagination metadata for a list response. Present whenever the request succeeded, and omitted when it failed validation. example: page: 1 pageSize: 25 totalCount: 67 totalPages: 3 V1Record: type: object properties: id: type: string description: UUID of the record in Forerunner. example: c7d8e9f0-1a2b-4c4d-8e6f-7a8b9c0d1e2f externalSystemId: description: >- Your system's identifier for this record, if one was supplied when it was created. example: PDA-2024-0417 type: - string - 'null' data: type: object propertyNames: type: string additionalProperties: {} description: >- The record's fields. The keys vary by record type and by how your community has configured that type. property: anyOf: - $ref: '#/components/schemas/V1Property' - type: 'null' description: >- The property this record is attached to, or null when it is not attached to one. required: - id - externalSystemId - data - property additionalProperties: false description: A record of a single record type. V1Property: type: object properties: id: type: string description: UUID of the property in Forerunner. example: a1b2c3d4-e5f6-4890-abcd-ef0123456789 address: description: >- The property's fully qualified address. Null for properties that have no address on file. example: 123 Main St, Springfield, IL 62701 type: - string - 'null' url: type: string description: >- Link to the property on the map in Forerunner. Requires an account to open. example: >- https://demoville.app.withforerunner.com/map?propertyId=a1b2c3d4-e5f6-4890-abcd-ef0123456789&tab=overview publicURL: description: >- Link to the property's public profile page. Null when the property is hidden from the public site. example: >- https://demoville.withforerunner.com/properties/a1b2c3d4-e5f6-4890-abcd-ef0123456789 type: - string - 'null' coordinates: type: array prefixItems: - type: number - type: number items: false minItems: 2 maxItems: 2 description: '`[latitude, longitude]` in EPSG:4326 (WGS 84).' example: - 39.7817 - -89.6501 required: - id - address - url - publicURL - coordinates additionalProperties: false description: A property in Forerunner. securitySchemes: bearerAuth: type: http scheme: bearer description: >- Your account's API key, sent as `Authorization: Bearer `. Keys are issued per environment, so a staging key will not work against production. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.