Request commute time from a property to a destination
View all Realty in US Property & Mortgage Data endpoints →Request travel time from a US property to a destination address. Supply the required property_id from property search and destination_address as query strings. Use a complete destination, including locality information when available; location autocomplete is documented as a way to obtain a more complete address. Optional transportation_type accepts the documented values bicycling, driving, transit and walking. The example value walking is not an established default. Optional with_traffic is a boolean described as requesting rush-hour time calculation; false is the documented example, not a verified omission default. These input controls do not establish real-time traffic coverage or availability of every mode for every journey. No observed probe response is available for this operation. The retained source example is truncated and begins with listing data rather than an identifiable commute result. No commute-specific response field names, time units, route geometry or traffic forecast fields are established by that example. Validate the actual response contract before parsing travel times or presenting numerical commute comparisons; do not assume a duration key or unit from the endpoint name.
API Features
Live API Demo
🔒 Sign in to try it live
Log in to call this API with your own API key. New accounts get 100 free credits — no card required.
Log in / Sign upNo active API key found. Create one in your Dashboard, then reload this page. Dashboard →
/api/project/realty-in-us/properties-v3-get-commute-time API Response (JSON)
{} curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/properties-v3-get-commute-time?key=<API_KEY>&destination_address=<destination_address>&property_id=<property_id>'
Query Result
Use Cases
- Build an opt-in home-to-office commute form using a shortlisted property and a user-entered work address.
- Let relocation users choose a documented travel mode before requesting a commute estimate, while making route availability explicit.
- Record the chosen rush-hour preference beside a commute request so later results retain their input assumptions.
- Verify duration fields and units in an integration test before enabling numerical comparisons between shortlisted homes.
Frequently asked questions
Which inputs are required for a commute request?
Both destination_address and property_id are required. Obtain property_id from a property-list result and provide a complete destination address. A street-only example is documented, but adding city and state information helps make the intended destination explicit.
Which transportation_type values are documented?
The documented values are bicycling, driving, transit and walking. The field is optional. Walking is an example value, not an established default, and successful routing for each mode has not been verified.
What does with_traffic mean?
The optional boolean is documented as controlling whether rush-hour time is calculated. False is an example input. The supplied evidence does not establish the default when omitted, live traffic availability, or a departure-time forecasting model.
Which response field contains the commute duration, and in what units?
Neither a duration field name nor its units are established by the supplied evidence. No probe response was observed, and the retained source example is truncated listing data rather than a verified commute payload. Inspect and verify the actual response before displaying a time.
Can this endpoint be presented as a verified route map or traffic forecast?
No. The documentation describes a commute-time request and its mode and rush-hour controls, but there is no observed response establishing route geometry, forecast fields, transport coverage or commute accuracy.