Terms in practice

Use of the API is subject to the Darak API terms of use. Five clauses shape how you build, so they are worth knowing before you design a sync rather than after:

Storage is capped at 30 days. You may keep Darak data to run your application for up to 30 days from when you retrieved it; after that, refresh it through the API or delete it. Aggregated statistics you derive for internal reporting may be kept longer, as long as they can't be reversed into listing-level data. The sync recipe above is built for exactly this: it keeps a copy current rather than accumulating one.
Delisted listings come down within 7 days. Once a listing stops being returned — sold, rented, withdrawn, merged as a duplicate — stop showing it within 7 days. A listing you can no longer fetch by id, or that comes back in missing_ids, is your signal.
Takedowns are 3 business days. If we tell you specific data must be removed, delete it and stop showing it within 3 business days. Keep the listing ids you have stored addressable so you can act on that.
Attribution is required where you display data. Show "Data by Darak" near it with a link to darak.app, and where you show an individual listing, link its url and credit the source by name ("Listed on Aqar"), or link source.url, which forwards to the original ad. That credits the original publisher and lets people verify the ad.
Showing data to your users needs a paid plan. Free is for building and testing, with your own team and test users. No self-serve plan lets you redistribute Darak data as a dataset, feed or API; Enterprise can license redistribution of derived aggregates (medians, indices, yields) that can't be reversed into listings.
Government open data is different. Responses that carry an attribution object (the registered-transaction endpoints under /transactions and /market/transactions, and /market/land-prices) serve Saudi open data under the Saudi Open Data License. None of the rules above apply to it: store it, publish it and resell it as you like, as long as the attribution notice and dataset links travel with it (section 3.4 of the API terms).

Standard endpoints are built to exclude advertiser names, phone numbers and commercial registration numbers. Listing text and images may still contain personal data an advertiser chose to include, and you are an independent controller of whatever you store — the Saudi Personal Data Protection Law applies to you directly.

Terms in practice

Use of the API is subject to the Darak API terms of use. Five clauses shape how you build, so they are worth knowing before you design a sync rather than after:

Storage is capped at 30 days. You may keep Darak data to run your application for up to 30 days from when you retrieved it; after that, refresh it through the API or delete it. Aggregated statistics you derive for internal reporting may be kept longer, as long as they can't be reversed into listing-level data. The sync recipe above is built for exactly this: it keeps a copy current rather than accumulating one.

Delisted listings come down within 7 days. Once a listing stops being returned — sold, rented, withdrawn, merged as a duplicate — stop showing it within 7 days. A listing you can no longer fetch by id, or that comes back in missing_ids, is your signal.

Takedowns are 3 business days. If we tell you specific data must be removed, delete it and stop showing it within 3 business days. Keep the listing ids you have stored addressable so you can act on that.

Attribution is required where you display data. Show "Data by Darak" near it with a link to darak.app, and where you show an individual listing, link its url and credit the source by name ("Listed on Aqar"), or link source.url, which forwards to the original ad. That credits the original publisher and lets people verify the ad.

Showing data to your users needs a paid plan. Free is for building and testing, with your own team and test users. No self-serve plan lets you redistribute Darak data as a dataset, feed or API; Enterprise can license redistribution of derived aggregates (medians, indices, yields) that can't be reversed into listings.

Government open data is different. Responses that carry an attribution object (the registered-transaction endpoints under /transactions and /market/transactions, and /market/land-prices) serve Saudi open data under the Saudi Open Data License. None of the rules above apply to it: store it, publish it and resell it as you like, as long as the attribution notice and dataset links travel with it (section 3.4 of the API terms).