Project absorption by area, developer or type
GET/market/absorption
Month-by-month absorption pooled over projects: per city (the default), neighborhood, developer, property type or project type, the units on offer at the start and end of each month, units gone, released and re-added, the pooled and median absorption rate, and months of stock at the month's pace. The per-project series and its rules are GET /projects/{id}/absorption; only months that are usable there are pooled, and each figure is null when fewer than min_sample_size projects have one. projects_observed, projects_usable and flagged give the sample behind every month.
This is not a sales record. A portal's or developer site's "available" count is what the page showed on the day. A unit counts as gone when the source stops offering it, which a sale, a reservation, a lease, or the developer pulling it off the page all look like from outside; reservations fall through, and developers hold units back. Read the figures as how fast the advertised offer shrinks, alongside registered deals where you need actual sales.
Which projects. Only sources that publish an inventory count can be measured: unit tables with a status per unit (Asas Makeen, Rasan; basis unit_status), a stated available count (Mada; reported_available), or the number of units listed on the project's page (Wasalt, CompoundIn; listed_units). Every other source's unit count is the project's size, which doesn't move with sales, so most projects have reliability no_inventory_signal. No source reports available units by unit type, so there is no per-type split; listing_type separates sale and rent where the source does. Copies of one project from several sources are read once, from the source with the best basis. Snapshots began on 2026-09-26. Coverage is thin and uneven: most measurable projects are in Riyadh, and a city or developer may have none; check projects_tracked and projects_usable before reading a rate.
Projects are counted by their latest location and developer, including projects that have since gone inactive (for the months they were on offer).
- Authentication
- Send a data key (dk_live_… or dk_test_…) as a Bearer token.
- Scope
projects- Cost
- 50 units per call
Parameters
| Name | Description |
|---|---|
cityType: string · query | Omit for all cities. |
neighborhood_idType: integer[] · query | Neighborhood ids from GET /cities/{city}/neighborhoods. Only projects mapped to a neighborhood match. |
developerType: string · query | Exact developer name, as returned by GET /developers. |
property_typeType: string · query | Projects whose units listed on Kite are mostly of this type. One of: |
project_typeType: string · query | One of: |
listing_typeType: string · query | Which inventory to read: One of: |
group_byType: string · query | One group per city (the default), neighborhood, developer, property type or project type. Projects without a value for the grouping field are left out and counted in One of: |
fromType: string · query | First month ( |
toType: string · query | Last month ( |
min_sample_sizeType: integer · query | A month's figures are null when fewer projects than this have a usable month. |
Response
The data field is an object with these fields.
| Name | Description |
|---|---|
filtersrequiredType: object | |
listing_typerequiredType: string | One of: |
group_byrequiredType: string | One of: |
fromrequiredType: string | |
torequiredType: string | |
min_sample_sizerequiredType: integer | |
projects_ungroupedrequiredType: integer | |
groupsrequiredType: object[] |
Related endpoints
- Search projects
GET /projects - Get a project
GET /projects/{id} - List a project's units
GET /projects/{id}/units - Get a project's unit availability over time
GET /projects/{id}/availability - Search project units
GET /project-units - List developers
GET /developers - Get a project's absorption by month
GET /projects/{id}/absorption