Overview

The Developers section of the Reelly API provides structured access to information about real-estate developers operating in the United Arab Emirates. These endpoints allow client applications to retrieve developer profiles, contact details, office information, branding assets (such as logos), and links to the projects managed by each developer.

The available endpoints cover both high-level listings and detailed, developer-specific insights. They are designed to support a wide range of client use cases, including directory pages, project filtering, developer profile screens, map integrations, and UI components that reference developer branding.

What Information Is Available

Through the Developers API, clients can retrieve:

Developer identity and profile

• Name and status (active / inactive)
• Official website
• Company description
• Social links
• Branding assets (logo in multiple resolutions)

Office and contact information

• Office locations (country, region, city, address)
• Working hours
• Email and phone contacts
• Contact persons associated with specific offices, with optional multilingual capabilities

Associated projects

Available through the detailed endpoint (/developers/id):

• A complete list of the developer’s active and historical projects
• Project metadata such as construction and sale status, price ranges, sizes, and location attributes
• Statistics summarizing the developer’s portfolio

Logo-only endpoints

Two lightweight endpoints provide only essential branding fields for use in UI components:

• /developers/id/logo (single logo)
• /developers/logos (list of all developer logos)

These are optimized for scenarios where applications must render logos without the overhead of full developer profiles.

Typical Use Cases

For client-facing applications

• Building a developer directory with searchable profiles
• Rendering developer cards in project lists or detail pages
• Providing contact information for sales, support, or corporate communication
• Displaying logo badges in project components
• Showing developer portfolios, including all associated projects

For map and analytics dashboards

• Highlighting developers active in a region
• Displaying detailed project portfolios per developer
• Powering filters or aggregations based on developer attributes

For automation and integrations

• Synchronizing developer data for CRM or ERP systems
• Periodically fetching updated project portfolios
• Rendering branding assets in PDF / brochures / exports

Available Endpoints

Response Formatting and Metadata

All developer endpoints:

• Return JSON responses only
• Provide stable IDs suitable for long-term references
• Include image metadata (MIME type, size in bytes, width, height) for consistent rendering
• Use the same logo structure as the /projects and /units endpoints to ensure compatibility

Endpoints

List Developers

Request

GET /api/v2/clients/developers

Description

Returns a list of all developers available in the Reelly platform.

Each developer object contains:

• Basic profile — id, name, status, website, description
• Branding — logo with URL and image metadata (MIME type, size, width, height)
• Contacts — phone, email, working_hours
• Social presence — social_links (array)
• Offices — list of office locations with address, country, and office-specific working hours

The response is a simple JSON array of developer objects (no pagination wrapper).

This endpoint is typically used to build developer directories, selection lists, and profile pages in client applications.

Response Example

[  {    "id": 49,    "name": "Kappa Acca Real Estate Development",    "website": "https://kappaacca.ae/",    "description": "Kappa Acca Real Estate Development is developed by Khamas Group. It is a very esteemed and reputed company in the UAE, it is one of the most respected enterprises. Its success exceeds it in the business world, especially that it is a leading stakeholder in construction and other industries. The company has progressed and grown simultaneously with Emirates’ growth and developments.",    "logo": {      "url": "https://api.reelly.io/vault/ZZLvFZFt/hfmrpc0d_fRIEIoHBoj52Nwq52o/0UMgvA../306155932_409449851310971_4064157388172736233_n.jpg",      "metadata": {        "mime": "image/jpeg",        "size": 95854,        "width": 800,        "height": 800      }    },    "status": "active",    "social_links": [],    "phone": "+97142828244",    "email": "[email protected]",    "working_hours": null,    "offices": [      {        "id": 1283,        "developer": 49,        "country": {          "id": 219,          "country": {            "code": "AE",            "name": "United Arab Emirates",            "alpha_2": "AE",            "alpha_3": "ARE",            "numeric": 784,            "flag": "https://reelly-backend.s3.amazonaws.com/static/flags/ae.gif"          },          "currency": "AED",          "timezone": "Asia/Dubai",          "phone_code": "+971",          "status": "active",          "region": null,          "custom_fields": null,          "city": null,          "district": null,          "sector": null,          "village": null        },        "region": "Dubai",        "city": "Dubai",        "address": "Airport Rd, Al Garhoud, Dubai",        "working_hours": [],        "is_main": false,        "email": "[email protected]",        "name": "Kappa Acca Real Estate Development"      }    ]  },  {    "id": 218,    "name": "Karma Developers",    "website": "https://karmadevelopers.ae/",    "description": "Karma Developers have successfully established a prominent presence in the fiercely competitive mid-size development sphere within the rapidly expanding real estate sector of the United Arab Emirates.",    "logo": {      "url": "https://api.reelly.io/vault/ZZLvFZFt/xgOZFvxlhhmKdM5wdAPG-9faK80/NR3kSA../Frame+15.png",      "metadata": {        "mime": "image/png",        "size": 704163,        "width": 500,        "height": 500      }    },    "status": "active",    "social_links": [],    "phone": null,    "email": "[email protected]",    "working_hours": null,    "offices": [      {        "id": 977,        "developer": 218,        "country": null,        "region": null,        "city": null,        "address": "25th Floor, Binary Tower, Business Bay, Dubai, U.A.E",        "working_hours": [          {            "days": "Monday - Friday ",            "time_range": " 9 AM - 6 PM"          },          {            "days": "Saturday ",            "time_range": "9 AM - 2:30 PM"          },          {            "days": "Sunday ",            "time_range": "Day off"          }        ],        "is_main": false,        "email": null,        "name": null      }    ]  }]

Filters

This endpoint does not support query filters for developers (such as by status or region). It always returns the complete list of developers accessible to the client.

Typical Use Cases

• Building a catalog of developers with logos and descriptions.
• Populating dropdowns or selector components with developer names and IDs.
• Displaying developer profile pages with contact details, office locations and descriptions.
• Using office information to show developer presence by geography (e.g. Dubai-based offices).

Notes

• The response is a plain array of developer objects (no count / next / previous fields).
• Some fields can be null, for example phone, email, working_hours, or country inside an office.
• The status field is an enum (active, inactive, archived) that can be used to filter or highlight developers on the client side (filtering itself is performed client-side for this endpoint).
• JSON is the primary and recommended format. Although a format query parameter is defined in the specification, only JSON is guaranteed to preserve the full structure of developer objects.

language

Description

Specifies the language used for localized text fields in the developers list response.

When this parameter is provided, the API returns all supported translatable text fields in the requested language. Fields without available translations fall back to English (en-us).

Translatable text fields

For this endpoint, the following field is translated:

• description

The following fields are not translated and always return in English:

• name
• working_hours
• offices[].name
• offices[].region
• offices[].city
• offices[].working_hours[].days
• offices[].working_hours[].time_range

Supported Languages

Available language codes:

GET /api/v2/clients/projects/languages

Confirmed languages with translated content: en-us (default), ar, de, fr, he, hi, it, pl, ru, tr, zh.

Meta

Request and Response Examples

Request with French language:

GET /api/v2/clients/developers?language=fr

Response (excerpt):

json

{  "id": 507,  "name": "4Direction Developers",  "description": "Fondée en 2006, 4Direction est passée d'une petite société de courtage à un acteur fiable et influent du marché immobilier de Dubaï..."}

Notes

• The language parameter affects only the description field for this endpoint.
• Developer names, office names, and working hours remain in English regardless of the language parameter.
• If a translation is not available for the description field, English is returned as a fallback.
• The parameter does not affect filtering, sorting, or pagination — only the representation of text values.

Developer Details

Request

GET /api/v2/clients/developers/id

Description

Returns full, extended information about a specific developer.

This endpoint provides significantly richer data compared to the general developer list:

The response includes:

• Developer profile — name, description, website, branding (logo)
• Offices — full geography, addresses, working hours, optional office contacts
• Projects — all associated projects with their attributes (construction status, sale status, completion dates, location details, size & price ranges, cover images)
• Statistics — aggregated metrics such as total number of projects and number of active projects

This endpoint is designed for building detailed developer profile pages, analytics dashboards, and enriched UI components where a full developer context (team, offices, portfolio, brand assets) is required.

Response Example

{  "id": 567,  "name": "Maas Developers",  "website": "https://www.maas.ae/",  "description": "Maas Developers is committed to enhancing Dubai’s real estate market...",  "logo": {    "url": "https://api.reelly.io/vault/.../logo.jpg",    "metadata": {      "mime": "image/jpeg",      "size": 2866,      "width": 150,      "height": 150    }  },  "offices": [    {      "id": 816,      "country": null,      "region": null,      "city": null,      "address": "1903 Ubora Commercial Tower...",      "working_hours": [        { "days": "Monday - Saturday", "time_range": "9 AM - 5 PM" },        { "days": "Sunday", "time_range": "Day off" }      ],      "is_main": false,      "email": null,      "name": null,      "office_contacts": [        {          "id": 774,          "name": "Liliana",          "display_name": "Liliana",          "phone": "971506029598‬",          "role": "sales_manager",          "languages": ["English", "Russian", "Ukrainian", "Turkish", "French"],          "contact_type": "whatsapp",          "whatsapp": "https://wa.me/971506029598",          "social_links": []        }      ]    }  ],  "social_links": [],  "projects": [    {      "id": 2844,      "name": "Maas Azur Residence",      "construction_status": "under_construction",      "sale_status": "on_sale",      "overview": "##### Project general facts...",      "short_description": null,      "completion_date": "Q3 2026",      "completion_datetime": "2026-09-30T11:46:46Z",      "units_count": 55,      "location": {        "id": 1084,        "country": "United Arab Emirates",        "region": "Dubai",        "district": "JVC (Jumeirah Village Circle)",        "latitude": 25.0626189513071,        "longitude": 55.208867617759175      },      "min_price": 775881.987075,      "max_price": 1822941.0069,      "min_size": 339.49267925508,      "max_size": 1022.7080711484,      "price_currency": "AED",      "area_unit": "sqft",      "cover_image": {        "url": "https://api.reelly.io/vault/.../image.jpg",        "metadata": { "mime": "image/jpeg", "size": 1919391, "width": 1500, "height": 1043 }      },      "updated_at": "2025-10-03T18:17:30.555808Z"    }  ],  "statistics": {    "projects_total": 1,    "projects_active": 1  }}

Path Parameters

If an invalid or non-existent ID is provided, the API returns:

{ "detail": "Not found." }

language

Description

Specifies the language used for localized text fields in the developer details response.

When this parameter is provided, the API returns all supported translatable text fields in the requested language. Fields without available translations fall back to English (en-us).

Translatable text fields

For this endpoint, the following fields are translated:

• description
• offices[].country.country.name — country name is translated when the country object is present

The following fields are not translated and always return in English:

• name
• working_hours
• offices[].name
• offices[].region
• offices[].city
• offices[].working_hours[].days
• offices[].working_hours[].time_range
• office_contacts[].name
• office_contacts[].display_name
• office_contacts[].languages[]
• projects[].name
• projects[].construction_status
• projects[].sale_status

Supported Languages

Available language codes:

GET /api/v2/clients/projects/languages

Confirmed languages with translated content: en-us (default), ar, de, fr, he, hi, it, pl, ru, tr, zh.

Meta

Request and Response Examples

Request with French language:

GET /api/v2/clients/developers/619?language=fr

Response (excerpt):

json

{  "id": 619,  "name": "ARY & MAZ Developments",  "description": "ARY & MAZ se positionne comme une force pionnière dans le secteur immobilier haut de gamme de Dubaï...",  "offices": [    {      "id": 1284,      "country": {        "id": 219,        "country": {          "code": "AE",          "name": "Émirats arabes unis"        }      },      "region": "Dubai",      "city": "Dubai",      "name": "Office"    }  ]}

Notes

• The language parameter affects the description field and nested country names.
• Developer names, project names, office names, and contact information remain in English.
• The embedded projects[] array does not include translated project content in this endpoint; to retrieve translated project data, use the dedicated Project endpoints with the language parameter.
• If a translation is not available for a field, English is returned as a fallback.
• The parameter does not affect filtering, sorting, or pagination — only the representation of text values.

Typical Use Cases

1. Build Developer Profile Pages

Use this endpoint to display full developer information, including:

• Logo and branding
• Detailed description
• Portfolio of projects
• Office locations
• Contacts

2. Show Developer's Active Projects

The projects array already includes construction_status and sale_status, allowing:

• Filtering for under construction
• Filtering for on sale
• Highlighting completed projects

3. CRM or Partner Dashboard

The endpoint provides a unified data structure that is ideal for:

• Lead routing based on developer
• Sales team dashboards
• Developer comparison views

4. Analytics & Reporting

The statistics block allows you to:

• Show total number of projects
• Highlight the developer’s portfolio scale
• Rank developers by activity or volume

Notes

• The endpoint always returns rich, complete developer information in a single call.
• The response includes the developer’s entire project list — there is no need to call /projects separately unless project-level filters are required.
• Some office fields (country, email, name) may be null, which is expected for some developers.
• JSON is the only format guaranteed to preserve full data integrity.

GET /developers/id/logo — Developer Logo

Request

GET /api/v2/clients/developers/id/logo

Description

Returns the developer’s logo asset — a lightweight endpoint intended for UI components that only require branding information without loading the developer’s full profile.

This endpoint is optimized for cases where the client needs to display logos in lists, cards, map popups, or other compact UI elements.

It returns:

• Developer ID and name
• Logo metadata (URL, MIME type, size, dimensions)

If a developer does not have a logo uploaded, the endpoint still returns the developer’s ID and name, with the logo field set to null.

This endpoint is significantly faster and lighter than requesting full developer details.

Response Example

{  "id": 547,  "name": "SCC Vertex Development",  "logo": {    "url": "https://api.reelly.io/vault/ZZLvFZFt/csTWVPH_ojSBfmAR0cNguypl6KQ/PvLEQQ../Frame+6.png",    "metadata": {      "mime": "image/png",      "size": 689825,      "width": 500,      "height": 500    }  }}

Example: Developer Without a Logo

{  "id": 63,  "name": "32Group",  "logo": null}

Path Parameters

Invalid IDs return:

{ "detail": "Not found." }

Query Parameters

language

Description

Specifies the language code for the response. This parameter is accepted by the endpoint for consistency with other API endpoints, but has no effect on the response content.

The /developers/id/logo endpoint returns only id, name, and logo fields. None of these fields are translatable.

Meta

Typical Use Cases

1. Rendering Developer Logos in Lists

Ideal for:

• Catalog pages
• Project cards that show developer branding
• Partner directories
• Dropdown selectors with logos

2. Map UI and Tooltips

Allows fast loading of:

• Logos shown on map markers
• Tooltip previews
• Hover interactions

3. Lazy Loading / Performance Optimization

When the UI needs:

• Only the logo
• Not the full developer description, projects, or office details

This endpoint avoids the large payload of /developers/id.

Notes

• Logo URLs reference the Reelly CDN and are safe for direct embedding in web and mobile applications.
• Images always include metadata, allowing clients to optimize rendering (e.g., aspect-ratio placeholders, pre-sizing).
• If no logo is available, the API explicitly returns "logo": null — clients should provide a fallback icon.
• The endpoint guarantees a consistent JSON response even when assets are missing.

GET /developers/logos — List All Developers with Logos

Request

GET /api/v2/clients/developers/logos

Description

Returns a lightweight list of all registered developers along with their logos.

This endpoint is designed for UI components that need to display a brand directory without loading full developer profiles.

Each item includes:

• Developer ID
• Developer name
• Logo metadata (URL, MIME type, size, dimensions) or null

The payload is intentionally minimal — no office information, website, social links, or project statistics.

This endpoint is ideal for high-performance scenarios such as:

• Logo walls
• Autocomplete lists
• Partner selection dialogs
• Developer filters in property search interfaces
• Preloading assets for UI rendering

Response Example

[  {    "id": 63,    "name": "32Group",    "logo": null  },  {    "id": 507,    "name": "4Direction Developers",    "logo": {      "url": "https://api.reelly.io/vault/ZZLvFZFt/8-XEjA4gjpLtBsL4u-XTPMRSseA/c1UTzA../Screenshot_1.png",      "metadata": {        "mime": "image/png",        "size": 27252,        "width": 597,        "height": 597      }    }  },  {    "id": 315,    "name": "7 Sens",    "logo": {      "url": "https://api.reelly.io/vault/ZZLvFZFt/EprlCEawG8nDXpLc25B4fZoFD24/dIRT6w../%D0%A1%D0%BD%D0%B8%D0%BC%D0%BE%D0%BA+%D1%8D%D0%BA%D1%80%D0%B0%D0%BD%D0%B0+2024-02-22+%D0%B2+13.30.52.png",      "metadata": {        "mime": "image/png",        "size": 570246,        "width": 764,        "height": 674      }    }  },  {    "id": 590,    "name": "7th Key Development",    "logo": {      "url": "https://reelly-backend.s3.amazonaws.com/1080x1080_cabea3c3b336434dbe126da6f943e377.webp",      "metadata": {        "mime": "image/webp",        "size": 14134,        "width": 1080,        "height": 1080      }    }  }]

Query Parameters

The response always returns the complete developer logo dataset.

language

Description

Specifies the language code for the response. This parameter is accepted by the endpoint for consistency with other API endpoints, but has no effect on the response content.

The /developers/logos endpoint returns only id, name, and logo fields. None of these fields are translatable:

• id — integer identifier
• name — developer name (not translated)
• logo — image URL and metadata

Meta

Notes

• Developer names are not translated and always appear in English.
• For translated developer content, use the /developers or /developers/id endpoints with the language parameter.

Typical Use Cases

1. Developer Directory / Brand Wall

Displaying all developers in a gallery or list with optional logos.

2. Search Bars & Autocomplete

Populating dropdowns where the user selects a developer to filter projects.

3. Map UI Preloading

Preloading all branded assets to avoid layout shifts or additional requests.

4. Project Cards & Tooltips

UIs that need quick access to logos without loading full developer objects.

Notes

• Logos may be null. Clients should provide default or placeholder icons.
• Image URLs point to the Reelly CDN and are optimized for external consumption.
• Metadata allows clients to apply aspect-ratio placeholders and responsive rendering.
• The list includes all developers, regardless of activity or presence of projects.
• Ordering is not guaranteed; clients should sort the list if needed.

Developer Offices

Description

The offices section represents the physical offices associated with a developer.

Each office describes a real-world location where the developer operates, including address details, working hours, and contact information. A developer may have zero, one, or multiple offices.

This section is primarily intended to support:

• displaying developer contact and location information,
• building office location blocks on developer profile pages,
• enabling client-side logic for choosing a primary or nearest office.

Structure Overview

The offices field is an array of office objects:

"offices": [  {    "id": 816,    "country": null,    "region": null,    "city": null,    "address": "1903 Ubora Commercial Tower, Business Bay, Dubai, UAE",    "working_hours": [...],    "is_main": false,    "email": null,    "name": null,    "office_contacts": [...]  }]

Office Object Fields

Notes

• A developer may have zero, one, or multiple offices.
• Location-related fields (country, region, city) are optional and may be partially populated.
• The working_hours array may contain multiple entries to represent different schedules.
• The is_main flag can be used by clients to prioritize or highlight a primary office in the UI.
• Office data is informational only and is not used for filtering in