Multiple Locations Quietness
Listings & Quietness
Multiple Locations Quietness
Get the Quiet Score™ for multiple locations and create/update your listings in batch
POST
Multiple Locations Quietness
Overview
The Multiple Locations Quietness API calculates the Quiet Score™ for multiple locations at once and automatically manages your listings. This is the batch version of the quietness API - ideal for processing multiple properties at once.To obtain an API key, register for an account and subscribe to a plan.
How It Works
For each listing in your request:- Check Listing: Verifies if you already have a listing at this geolocation
- Check Freshness: If listing exists, checks if the quietness data needs refresh based on your plan
- Calculate: If needed, calculates the Quiet Score™ using our patent-pending AI
- Update: Creates or updates your listing with the latest quietness data
Refresh Rates by Plan
| Plan | Refresh Rate |
|---|---|
| Trial | 1 day |
| Insight | 30 days |
| Intelligence | 7 days |
| Enterprise | 1 day |
Authorization
Your API key for authentication
Request Body
Array of listing objects to get quietness for. Each object must contain
lat (float) and lng (float) coordinates.Request Structure
| Field | Type | Required | Description |
|---|---|---|---|
listings | array | Yes | Array of listing objects |
listings[].lat | float | Yes | Latitude coordinate of the location |
listings[].lng | float | Yes | Longitude coordinate of the location |
Summary Response Fields
| Field | Type | Description |
|---|---|---|
total | number | Total number of listings in the request |
successful | number | Number of listings successfully processed |
failed | number | Number of listings that failed to process |
Individual Result Fields
Each result in theresults array is a dictionary with an id field containing the listing_id (UUID format) for successful results, or a temporary ID (like error_1, limit_reached_2) for errors.
| Field | Type | Description |
|---|---|---|
id | string | Listing ID (UUID) for successful results, or error identifier (e.g., error_1, limit_reached_2) for failures |
status | string | ”OK” for success, “ERROR” for general failure, “LIMIT_REACHED” when listing limit is hit |
request.lat | number | Original latitude from the request |
request.lng | number | Original longitude from the request |
response | object | Full listing data (same as single location quietness response) - only present for successful results |
error | string | Error message (present when status is “ERROR” or “LIMIT_REACHED”) |
Status Values
| Status | Description |
|---|---|
OK | Listing was successfully created/updated |
ERROR | General error (invalid coordinates, server error, etc.) |
LIMIT_REACHED | Your plan’s listing limit has been reached. Quietness data may still be included in the response, but no listing was created. |
Response Fields (for each successful listing)
| Field | Type | Description |
|---|---|---|
listing_id | string | Unique identifier for your listing |
lat | number | Latitude of the listing (rounded to 6 decimal places) |
lng | number | Longitude of the listing (rounded to 6 decimal places) |
quiet_score | number | Score from 0-100 (higher = quieter) |
quiet_score_range | object | The valid range for the quiet score (min: 0, max: 100) |
quietness_level | string | Human-readable rating |
quietness_description | string | Description of what living there feels like |
quiet_day_night | object | Day/night specific quietness data |
noise_sources | array | Array of noise source objects |
quiet_score_confidence | string | Confidence level: “low”, “medium”, or “high” |
created_at | string | ISO 8601 timestamp of when the listing was created |
updated_at | string | ISO 8601 timestamp of when the listing was last updated |
Day/Night Fields (quiet_day_night)
The quiet_day_night object provides separate quietness analysis for daytime and nighttime periods:
| Field | Type | Description |
|---|---|---|
day_window_local | string | Daytime hours (e.g., “07:00-22:00”) |
night_window_local | string | Nighttime hours (e.g., “22:00-07:00”) |
quiet_score_day | number | Quiet Score™ during daytime (0-100) |
quiet_score_night | number | Quiet Score™ during nighttime (0-100) |
estimated_noise_db_day | number | Estimated noise level during day in dBA |
estimated_noise_db_night | number | Estimated noise level during night in dBA |
noise_db_unit | string | Unit of measurement for dB values (“dBA”) |
Limits
- Maximum listings per request: 20
- Each listing counts against your plan’s listing limit
- If you hit your listing limit mid-batch, subsequent locations will have
status: "LIMIT_REACHED"
Handling Listing Limit
When you hit your plan’s listing limit during a batch request:- The API will not break - it continues processing all locations
- Locations that exceed the limit will have
status: "LIMIT_REACHED" - The
summary.failedcount will include these limit-reached items - Quietness data may still be calculated and returned (but no listing is created)
Example: Partial Success with Limit Reached
Notes
- Results are processed in parallel for optimal performance
- Failed listings don’t stop the processing of remaining locations
- Coordinates should be in decimal degrees format (WGS84)
- Each result contains an
idfield:listing_id(UUID) for successful results, or error identifiers likeerror_1,limit_reached_2for failures - Results are returned in the same order as the input request
- Day/night scores help users understand noise patterns throughout the day - night scores are typically higher (quieter) for residential areas