The derived tables, in your own systems

Every call is signed HMAC-SHA256 over the method, the path, the sorted query string and the timestamp, using the secret issued with the key. The signature goes in x-opi-signature, the key id in x-opi-key-id, and the timestamp used in the signature in x-opi-timestamp.

Example request, obviously fake secret

GET https://offplanindex.com/api/v1/sync?limit=500&since=b3Q9MTAw

x-opi-key-id: opi_live_4f2a9c
x-opi-timestamp: 1788512000
x-opi-signature: b3f1c9a7d4e6082f1a5c7e9b0d2f4681c3e5a7091f2b4d6c8e0a1b3c5d7e9f01

Secret shown: sk_EXAMPLE_NOT_A_REAL_SECRET_00000000, a placeholder. A real key is issued per organisation and never appears on this page.

Example response, three real projects

{
  "data": {
    "records": [
      {
        "id": "marquis-elegance-20-20",
        "title": "Marquis Elegance",
        "developer": "20/20",
        "developer_slug": "20-20",
        "community": "Arjan",
        "community_slug": "arjan",
        "city": "Dubai",
        "starting_price": 1055634,
        "delivery_quarter": "Q2 2025",
        "delivery_year": 2025,
        "sale_status": "sold_out",
        "construction_status": "completed",
        "property_types": "apartment",
        "bedrooms": "1,2,3",
        "n_units": 8,
        "n_plans": 1,
        "updated_at": "2026-09-04",
        "content_hash": "7a1e9c3f5b2d8061"
      },
      {
        "id": "wellington-ocean",
        "title": "Wellington Ocean",
        "developer": "Wellington",
        "developer_slug": "wellington",
        "community": "Dubai Islands",
        "community_slug": "dubai-islands",
        "city": "Dubai",
        "starting_price": 2152750,
        "delivery_quarter": "Q4 2026",
        "delivery_year": 2026,
        "sale_status": "on_sale",
        "construction_status": "under_construction",
        "property_types": "apartment,duplex",
        "bedrooms": "1,2",
        "n_units": 14,
        "n_plans": 1,
        "updated_at": "2026-09-04",
        "content_hash": "e4b6081a2c9f7d35"
      },
      {
        "id": "nifco-esplora",
        "title": "Esplora",
        "developer": "NiFCO",
        "developer_slug": "nifco",
        "community": "Jumeirah Village Circle",
        "community_slug": "jumeirah-village-circle",
        "city": "Dubai",
        "starting_price": 695000,
        "delivery_quarter": "Q4 2025",
        "delivery_year": 2025,
        "sale_status": "on_sale",
        "construction_status": "completed",
        "property_types": "apartment",
        "bedrooms": "0,1,2",
        "n_units": 20,
        "n_plans": 1,
        "updated_at": "2026-09-04",
        "content_hash": "1f6a3e8c5d9b0247"
      }
    ],
    "tombstones": [
      "al-marasi-tower-b"
    ],
    "next_cursor": "b3Q9NjAw",
    "schema_version": 1,
    "build_date": "2026-10-02"
  },
  "meta": {
    "license": "See /data-policy. Aggregate data only, no listing text or images."
  }
}

next_cursor is opaque and always points just past the last entry returned. The walk is finished when a page comes back with empty records and empty tombstones; keep that cursor and send it again on the next schedule, and new data lands after it. A record listed in tombstones has left the off-plan book (sold out and delisted, or merged into another id) and should be deleted from the client’s own store, not merely skipped. A record absent from both records and tombstones on a given page is simply outside that page’s cursor window, not gone. schema_version only changes when a field is renamed or removed, so a client can trust it holds across an ordinary refresh.

• 14 days. The key stops working at the end of day 14, evaluation or not.
• Scoped to sync. The key only opens GET /v1/sync, not the full /v1 surface.
• 500 records per call. Same page size cap as the paid licence, so an evaluation client is tested against the real pagination.
• A total cap for the 14 days. Enough calls to page the whole corpus more than once, not enough to run a production integration on for free.

Issued by hand, not self-serve: say what you are integrating and we send a key scoped exactly as above.

• ●The schema is testable before the first charge. The sample files on this page are the licensed columns on a slice of the rows, taken evenly across each table rather than off the top of it.
• ●First month refunded in full, for 14 days. If the bundle does not match the published schema, or the tables are materially not as described here.
• ●A month with no new build is credited if you ask for it. The data build is run by hand, so we do not promise a fixed refresh interval. Instead: if a calendar month passes and no newly dated bundle appeared, tell us and we credit that month. Every bundle carries its three dates, so this is checkable from your side rather than ours.
• ●Cancel any month. Access to new bundles ends at the end of the paid month. What you may keep doing with bundles you already hold is written down on the licence page, in full, for the person in your firm who has to read it.
• ●Who answers. One person reads hello@offplanindex.com and answers within one business day. There is no ticket system and no queue.