List schools near coordinates using the deprecated legacy route

View all Realty in US Property & Mortgage Data endpoints →

Deprecated: retain GET /schools/list-nearby only for auditing or migrating existing integrations, not for new development. The operation is documented to list schools near a property location. Supply both required numeric query parameters: lat for latitude and lon for longitude, expressed as decimal-degree coordinates. The documented example values are lat=35.129431 and lon=-117.937021. No property ID, address, radius, pagination, grade filter, or attendance-assignment input is documented. There is no supplied live probe response for this operation. An unverified source example labeled HTTP 200 is present but truncated, so it is not a complete valid JSON response or proof of current route availability. Its visible top-level fields are districts (an empty array in the example), meta.build, and schools. A complete school record within the example includes id, name, greatschools_id, nces_id, funding_type, education_levels, grades.range.low and grades.range.high, lat, lon, and distance_in_miles. It also shows district.id and district.name; location.city, city_slug_id, county, postal_code, state, and street; phone; ratings.great_schools_rating and ratings.parent_rating; relevance; student_count; student_teacher_ratio; and boundary_trimmed.type with nested boundary_trimmed.coordinates. These are example fields, not observed or guaranteed current output. The example has a null ratings.great_schools_rating value, and its empty districts array establishes no district-list schema. Do not assume fixed ordering, complete school coverage, a stable search radius, a particular rating scale, or fresh enrollment statistics. Proximity and example boundary geometry do not establish attendance assignment or enrollment eligibility. Use the route only to understand an existing nearby-school dependency and its nullable fields. Validate a replacement independently before promising continuing nearby-school coverage; do not depend on the unavailable school-search route as a replacement or ID discovery step.

API Features

Legacy coordinate-pair compatibility Document the existing required numeric lat and lon inputs, preserving their separate latitude and longitude roles for migration audits.
Sample-only proximity distance The unverified source example includes distance_in_miles on school records; no stable radius, ordering, or current coverage is established.
Visible school-list field inventory Identify school, district, location, grade-range, and education-level keys visible in the truncated example without treating them as a verified schema.
Nullable legacy rating handling The example shows ratings.great_schools_rating as null alongside parent_rating, so legacy displays must not convert missing ratings into zero scores.
School boundary interpretation warning The sample contains boundary_trimmed geometry, but neither that geometry nor geographic proximity proves school attendance assignment.
Replacement coverage verification Plan retirement around an independently verified alternative instead of recommending this deprecated route or the unavailable school-search dependency.

Live API Demo

GET /api/project/realty-in-us/schools-list-nearby-deprecated

Request cost is temporarily unavailable. No price is assumed.

View pricing

API Response (JSON)

{}
curl -X GET 'https://api.opendata-api.com/api/project/realty-in-us/schools-list-nearby-deprecated?key=<API_KEY>&lat=<lat>&lon=<lon>'
📢
Need Help?
If you encounter API issues or need other API requirements, please contact us.
Contact Us

Use Cases

Frequently asked questions

Should I use this nearby-school route for a new application?

No. It is deprecated and retained as a legacy migration surface. Its current availability has not been verified by a supplied live probe, and any replacement needs independent validation.

Which coordinates are required for the legacy request?

Both lat and lon are required numeric query parameters: latitude and longitude in decimal degrees. The documented example is lat=35.129431 and lon=-117.937021. Do not reverse the two values.

Which response fields are visible in the legacy example?

The truncated source example shows districts, meta.build, and schools. A complete school record within it includes identifiers, name, coordinates, distance_in_miles, district and location details, education levels, grade range, phone, ratings, student counts, student-teacher ratio, relevance, and boundary_trimmed geometry. These fields are example-only, not live-verified output.

Are school ratings always present as numbers?

No such guarantee is established. The source example has ratings.great_schools_rating set to null. Preserve missing-rating states and do not assume a rating scale or convert a missing value into a zero score.

Do nearby schools or the example boundaries prove school eligibility?

No. Geographic proximity and boundary_trimmed in an unverified example are not proof of a property's school assignment or student enrollment eligibility. Verify current rules with official school or district sources.

Can I configure a radius or rely on a school-search replacement?

No radius parameter is documented, and the example does not establish a fixed radius or result ordering. The referenced school-search route is unavailable as a replacement dependency; verify an alternative independently before promising continuing nearby-school coverage.

Related operations

Guides

View Subscription Plans →