Rental community comparison
Greystarエンドポイントを使えば、「Rental community comparison」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Research Greystar's public rental communities and their location, floor-plan, fee, and available-unit records alongside local guides, renter resources, and corporate newsroom content.
Collect Greystar rental communities, floor plans, available units, published fees, location guides, renter articles, and newsroom records as JSON.
エンドポイントファミリー
6
ドキュメント化されたパラメータ
52
サンプル数
11
ライブカタログスナップショット
稼働エンドポイント
11
メソッド
GET
必須パラメータ
16
スキーマ参照
11
{
"platform": "Greystar",
"endpoint": "greystar-markets",
"method": "GET",
"path": "/greystar/markets",
"auth": "apiKey"
}ユースケース
Collect Greystar rental communities, floor plans, available units, published fees, location guides, renter articles, and newsroom records as JSON.
Greystarエンドポイントを使えば、「Rental community comparison」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Greystarエンドポイントを使えば、「Floor-plan and fee research」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
Greystarエンドポイントを使えば、「Location and renter-content discovery」をドキュメント化された入力とJSONレスポンスによる再現可能なAPIリクエストに変えられます。
マネージド実行
以下の数値はすべて、稼働中のGreystarエンドポイントカタログから取得しています（エンドポイント11件、ドキュメント化されたリクエストパラメータ52個、公開レスポンススキーマ11件）。DocsとPlaygroundが参照しているカタログと同じものです。
Greystarのエンドポイントは11件、9つのリクエストファミリーに分類されています（Articles、Newsroom、Locationほか6件）。
これらのGreystarエンドポイントには52個のリクエストパラメータがドキュメント化されており、うち16個が必須です。統合コードを書く前に入力仕様をすべて確認できます。
11件のGreystarエンドポイントのうち11件が実際のサンプルレスポンスを、11件がドキュメント化されたレスポンススキーマを備えています。最初のリクエストの前に実データの形に合わせて実装できます。
Greystarのエンドポイントは成功時のスキーマに加えてエラーレスポンス（400、404、429、503）もドキュメント化しています。ブロック、レート制限、レコード欠損は空データではなく型付きのエラーとして返ります。
Greystarのエンドポイントは11個のホスト型MCPツールとして提供されており、エージェントは同じパラメータと同じJSON契約のまま、追加の実装なしに同じルートを呼び出せます。
カバレッジマップ
これらのカードは稼働中のエンドポイントカタログから生成されるため、このページはDocsとPlaygroundが使うAPIサーフェスをそのまま反映します。
/greystar/articles
/greystar/newsroom
/greystar/location
/greystar/locations
/greystar/markets
/greystar/properties/{id}
エンドポイントカタログ
/greystar/marketsReturns every value accepted by the /greystar/search market_area, neighborhood, city, state, and country_code filters, each with the number of communities currently published. Derived from the full live community list, so it is the complete value space.
レスポンスに関する注記
Returns every value the `/greystar/search` filters accept, each with the number of Greystar communities currently published: `countries` (`country_code`), `states` (`state`, `state_name`), `market_areas` (`market_area`), `neighborhoods` (`neighborhood`, with its `market_area`), and `cities` (`city`, with its `state`). The lists are derived from the complete live community list (about 4,000 communities, refreshed hourly), so they are the full value space rather than a sample. Communities with no market area or neighborhood on Greystar's side are counted in `total_properties` but appear in no market or neighborhood entry. The list is a snapshot refreshed every few minutes and changes as communities are added or removed; fetch it instead of persisting values.
MCPツール greystar_markets
/greystar/searchLists Greystar communities published on greystar.com, optionally filtered by market area, neighborhood, city, state, country, starting rent, or free text. Filter values must come from /greystar/markets; an unknown value returns 400. Starting prices reflect each community's published minimum and are null when none is published. Results come from an hourly snapshot of every community listed on greystar.com; the default order follows the site.
レスポンスに関する注記
Filter values match case-insensitively but must exist in `/greystar/markets`; an unknown value returns `400` instead of an empty list. Filters combine with AND. Results come from an hourly snapshot of every community listed on greystar.com (about 4,000 on 2026-10-04), so `total_count` is exact for the snapshot. `min_price` is the community's published starting rent and is `null` when none is published. A page past the end returns an empty `properties` array. Use a result's `id` with `/greystar/properties/{id}` for floor plans, fees, and available units.
MCPツール greystar_search
/greystar/unit-locationsLists every location accepted by /greystar/units: the nationwide us listing, states, metros, cities, and neighborhoods (nested ones carry their parent), taken from the site's own search pages. Locations Greystar has no unit listing for are dropped once detected.
レスポンスに関する注記
Lists every location `/greystar/units` accepts, taken from greystar.com's own search pages: the nationwide `us` listing first, then states, metros, cities, and neighborhoods in slug order (1,797 on 2026-10-04). Nested locations such as `greater-austin/round-rock` carry their `parent`. A handful of the site's search pages have no unit listing; each is dropped from this list once a unit search has detected it. The list is cached for an hour. These slugs are a different taxonomy from `/greystar/markets` (community data) and `/greystar/locations` (rental guide pages).
MCPツール greystar_unit_locations
/greystar/unitsSearches apartment units currently available to rent on greystar.com within one location (nationwide by default), filtered by bedrooms, bathrooms, building type, community highlights, and monthly price, sorted by relevance or price. Results are grouped by community: each carries its address, coordinates, the number of matching units, and up to about 100 units with unit number, floor plan, bedrooms, bathrooms, price range, and lease term. The response also returns filter counts for the location. Several values of one filter match any of them. Get location values from /greystar/unit-locations.
レスポンスに関する注記
Lists units currently available to rent, grouped by community. `total_count` counts community groups (a very large community can appear as more than one group). Each entry in `properties` carries `property_id` (usable with `/greystar/properties/{id}`), name, address, coordinates, `matching_units`, and `units`: each with `unit_id`, `unit_number`, `floorplan`, `bedrooms`, `bathrooms`, `price`, `min_price`/`max_price`, `min_base_rent_lease_term`, and required monthly fees. At most about 100 units are listed per community; `units_truncated` is `true` when `matching_units` is larger. `facets` gives the counts for `bedrooms`, `bathrooms`, `building_types`, and `highlights` in the location. A listed location that Greystar has no unit listing for returns `404`.
MCPツール greystar_units
/greystar/properties/{id}Retrieves a public Greystar community profile by its numeric property id: location, description, amenities, office hours, walk scores, tours, floor plans, published fees, and currently available units with starting prices and available dates. Get ids from /greystar/search.
レスポンスに関する注記
Returns the public community profile: `location` (address, coordinates, market area, neighborhood), descriptions, `highlights`, `amenities`, `features`, public `phone` and `email`, `office_hours`, walk/bike/transit scores, 3D `tours`, `floorplans`, published `fees`, and `available_units` with starting prices, available dates, and lease terms. Placeholder text such as "Information coming soon!" is dropped, so lists can be empty. Prices are `null` when none is published. An unknown or unpublished id returns `404`; an upstream failure or malformed response returns an upstream error.
MCPツール greystar_property
/greystar/locationsLists Greystar's state, city, and neighborhood rental hub pages (the site's own location tree) with slugs and URLs. Use the slugs with /greystar/location for a hub's editorial content, child locations, listed communities, and FAQs.
レスポンスに関する注記
Lists the state, city, and neighborhood rental hub pages that make up greystar.com's own location tree (803 pages on 2026-10-04). Each entry has `level`, `state`, `city`, `neighborhood`, `path`, `url`, and `last_modified`. Entries sort by state, then city, then neighborhood. Unknown `state` or `city` values return `400`. Use the slugs with `/greystar/location`. This tree is the site's navigation and differs from the market areas in `/greystar/markets`, which come from the community data.
MCPツール greystar_locations
/greystar/locationRetrieves one Greystar state, city, or neighborhood rental hub: title, description, editorial guide text as ordered blocks, child locations with summaries, communities listed on the page (id, name, address, and price text when shown), and FAQs. State, city, and neighborhood slugs must come from /greystar/locations; unknown values return 400.
レスポンスに関する注記
Returns one rental hub page: `level` (`state`, `city`, or `neighborhood`), `title`, `description`, `blocks` (the editorial guide text as ordered `heading`, `subheading`, `paragraph`, and `list_item` entries), `sub_locations` (direct children with `name`, `slug`, `path`, and `summary`), `communities` (communities listed on the page with `id`, `name`, `slug`, `url`, `address`, and `price_text` when shown), and `faqs` (question and answer pairs). Use a community `id` with `/greystar/properties/{id}`. State hubs list sub-locations but usually no communities. Child summaries are truncated by the site. Slugs are checked against the live location list first, so an unknown value returns `400` rather than a missing page.
MCPツール greystar_location
/greystar/articlesLists Greystar's renter guides (applying and leasing, general guides, moving) and blog posts from its public sitemap, newest first. Entries carry the section, slug, URL and last-modified date; fetch /greystar/articles/{section}/{slug} for the title and body.
レスポンスに関する注記
Lists Greystar's renter guides and blog posts from its public sitemap, newest first by last-modified date. Each entry has `section`, `slug`, `url`, and `last_modified`; titles and bodies are not in the sitemap, so call `/greystar/articles/{section}/{slug}` for them. Index pages (for example the blog's browse page) are excluded. An unknown `section` returns `400`; a page past the end returns an empty `entries` array. The sitemap is cached for an hour.
MCPツール greystar_articles
/greystar/articles/{section}/{slug}Retrieves one Greystar renter guide or blog post: title, description, category, publish date (blog posts), lead image, and the body as ordered heading, paragraph, and list blocks. Get section and slug values from /greystar/articles.
レスポンスに関する注記
Returns `title`, `description`, `category`, `image_url`, and `blocks`, the article body as ordered `heading`, `subheading`, `paragraph`, and `list_item` entries. Blog posts also carry `published_date` (as shown on the page) and `published_at` (`YYYY-MM-DD`); renter guides carry no publish date, and their `category` is the section. Breadcrumb text and the blog's related-posts section are excluded. An unknown slug returns `404`; an invalid section or slug returns `400`.
MCPツール greystar_article
/greystar/newsroomLists Greystar corporate newsroom releases and news articles from its public sitemap, newest first, with slug, URL and last-modified date. Fetch /greystar/newsroom/{slug} for the title, date, and body.
レスポンスに関する注記
Lists Greystar corporate newsroom releases and news articles from its public sitemap, newest first by last-modified date, with `slug`, `url`, and `last_modified`. Call `/greystar/newsroom/{slug}` for the title, date, and body. A page past the end returns an empty `entries` array. The sitemap is cached for an hour.
MCPツール greystar_newsroom
/greystar/newsroom/{slug}Retrieves one Greystar newsroom release: title, type (for example Press Release), publish date, lead image, and body paragraphs. Older news stubs carry only a title and date, so the body can be empty. Get slugs from /greystar/newsroom.
レスポンスに関する注記
Returns `title`, `category` (the release type, for example `Press Release` or `News Article`), `published_date` (as shown) and `published_at` (`YYYY-MM-DD`), `image_url`, and `blocks` with the body paragraphs. Older news stubs carry only a title, type, and date, so `blocks` can be an empty array. An unknown slug returns `404`; an invalid slug returns `400`.
MCPツール greystar_newsroom_article
関連API
Real Estate & Property
Use a Zillow API to turn public property search, home detail, and location autocomplete pages into structured JSON for real estate research, market monitoring, and property intelligence workflows.
Real Estate & Property
Use a Redfin API to turn public Redfin listing search, property detail, Redfin Estimate, comparables, and regional market-trend pages into structured JSON for real estate research, valuation, and market-monitoring workflows.
Real Estate & Property
Turn Rightmove — the UK's largest property portal — into structured JSON: location autocomplete, for-sale/to-let/sold property search with price and bedroom filters, dedicated commercial, new-homes and student-accommodation searches, estate-agent branch listings, and full property detail including floor plans, EPC rating, and nearby schools, all with one API key.
Greystarのスクレイピング方法
Greystar separates homes-to-rent discovery, individual community pages, local guides, renter resources, and its corporate newsroom. The nine documented routes retain those distinctions. Start with the markets directory to obtain exact country, state, city, neighborhood, and market-area values, then search communities and use their numeric IDs for property detail. Search operates on a periodically refreshed published-community snapshot rather than a tenant application or resident-account session. Preserve retrieval time and price context: a community may have no published starting rent, while property detail can carry floor plans, available units, lease terms, and required monthly fees separately. These public research routes do not submit rental applications, reserve units, or guarantee that an advertised unit remains available.
Call /greystar/markets and reuse its exact market_area, neighborhood, city, state, and country_code values. Matching is case-insensitive, but unknown values return 400; do not replace the returned market area with an invented slug.
Use /greystar/search with query text and any returned geography filters. Filters combine with AND. page is one-based and per_page is capped at 100; a page beyond the snapshot total returns an empty properties array. Price bounds exclude communities whose starting rent is not published.
Read /greystar/unit-locations and pass one of its exact slugs to /greystar/units. This directory is separate from community markets and rental guides. Filter bedrooms, bathrooms, building types, highlights, and unit prices; results are grouped by community. Preserve matching_units and units_truncated so a partial unit list is visible, and keep required monthly fees separate from the quoted unit price.
Pass a search result's numeric id to /greystar/properties/{id}. Read amenities, contact details, floor plans, fees, tours, and available units where published. Keep null prices and empty lists meaningful rather than converting them into zero-cost offers or unavailable features.
Use /greystar/locations and /greystar/location for local-guide discovery, /greystar/articles for renter-guide or blog slugs, and /greystar/newsroom for corporate stories. Article detail requires the matching section and slug; newsroom detail uses its own slug route. These routes return structured public content blocks, not tenant documents.
FAQ
The markets response supplies the supported geography values. Search accepts those country, state, city, neighborhood, and market-area filters plus free text, published starting-rent bounds, sort, page, and per_page. Unknown geography values return 400, and the filters combine with AND.
Treat the search starting-rent field, published required monthly fees, unit prices, and lease terms as distinct data. The official site explains its displayed monthly leasing prices, while the API preserves the documented component fields. Retain the source context and use property detail for the published breakdown; null means no price was supplied.
Use the exact slug from /greystar/unit-locations, such as a city, state, or nested metro/neighborhood slug. The nationwide default is us. These values differ from /greystar/markets and rental-guide locations; unknown unit-location slugs return 400. Use each location's returned unit-search facets to select supported bedroom, bathroom, building-type, and highlight filters.
Use an id returned by /greystar/search or the numeric p_<id> segment in the community's own Greystar URL. A nonnumeric ID returns 400; an unknown or unpublished community returns 404. A property record describes published information and does not promise current booking availability.
No. Renter resources use applying-and-leasing, general-guides, moving, or blog sections with a matching article slug. The newsroom has separate list and detail routes. Local guides have their own location directory and state/city/neighborhood selectors, so a newsroom slug or property ID is not a substitute for a local-guide request.
These routes collect supported public community and editorial records. They do not log in to resident accounts, submit tenant applications, schedule a reservation, or make a housing eligibility decision. Follow Greystar's own application and resident workflows for those actions.