Most users will switch from v1 directly to v3. While the documentation for v3 may be harder to read for a general reader, it follows an industry standard and is very easy for a programmer to use.
v3 is thoroughly documented here, and the list below is intended as a user-friendly overview.
- The API returns a 200 status code only when a data response is provided. If data is not returned because the address or parcel could not be found a 404 status code is returned.
- The format of the main flood data results is unchanged, in particular the FEMA flood zone layers are presented in the same manner as earlier versions.
- The community data is now collected in a dictionary instead of multiple individual entries.
- The census bureau data is now collected in a dictionary instead of multiple individual entries.
- The three datasets
parcelthat require an additional access are now all contained within the same API. If a user's key does not include access to this data, the data will not be provided.
- The query parameter
getbfehas been replaced by the parameter
elevationto be consistent with
- The endpoint
floodmaphas been renamed
floodmaprawto make clear that this endpoint returns raw data and not a map.
- The fields returned in the geocode section have changed.
- The paths for the static and dynamic maps have changed, but the maps themselves remain the same.
- The data API no longer contains a preformatted url to access the static map. The user must now query the static map directly. The coordinates returned by the API may be used in the request to the static map endpoint.