Skip to main content

MENA Net Director Source

The MENA sources fetch model catalogs, per-variant feature catalogs, inventory listings and dealer locations for the Middle East and North Africa markets. Mercedes serves these markets through Net Director. The client modules live in packages/ai_public_api/src/ai_public_api/mercedes/mena/.

Authentication​

No per-partner credentials. The configurator endpoints use a static x-api-key, and the listing and locations endpoints a static UUID and auth token. All of these come from the public site.

Endpoints​

SourceEndpoint
nd_configuratormercedes-configurator.netdirector.auto: filter classes, selectables names, per-baumuster selectables
nd_listingproduction-api.search-api.netdirector.auto/api/vehicle-search (getCount and getAll)
nd_locationsgetAllLocations GraphQL query

Endpoints not used​

EndpointWhy
search-api.netdirector.auto/v3.5/search/<softwareId>/buy-new (REST)Returns the same vehicles as the GraphQL search in a different envelope.
extras.api.netdirector.auto/api/extras/<groupSoftwareHash>Dealer-fit warranty and protection plans, not factory-fit equipment.
finance.api.netdirector.autoPer-stock finance quotes. No current use.
Vehicle detail page HTML (/<country>/en/stock/<stockId>-…/)equipment[].label on the listing has the same items.
Buy-new page DOM (data-vehicle-context cards)The GraphQL listing has the same data.

Markets​

MENA_MARKETS maps each market's URL slug to its ISO country code. The slug is the canonical key. Dubai and Abu Dhabi are separate listing markets that share one configurator fetch, so the listing and the configurator have different granularity.

Eight markets have stock: Dubai, Abu Dhabi, KSA, Qatar, Kuwait, Bahrain, Oman and Lebanon, about 1,170 vehicles in total. Jordan, Iraq and Palestine serve an empty Net Director shell from their buy-new pages, so they have listing_active=False.

The configurator locale is <language>_<country>. The country half filters which models appear. Qatar's catalog has 45 baumusters and the UAE's has 73. Saudi Arabia has one model the UAE does not. The language half localizes display strings only.

Inventory listings come back in English for every locale. The endpoint takes no language parameter and ignores Accept-Language. The Arabic MENA pages translate on the client, so there is no server-side Arabic inventory text to collect. Arabic catalog strings do come from the configurator under ar_* locales.

Stock scope comes from the buy-new page​

No public endpoint returns a market's GraphQL stockScope. The source fetches each country's /buy-new/ page and decodes the base64 data-js-context blob in the HTML.

Configurator quirks​

  • The views parameter accepts only one value. ALL, OPTIONS, DETAIL and the rest all return HTTP 400.
  • The selectables-names URL has an upstream typo, seletables with one l.
  • A configurationId can contain literal # characters, which must be URL-encoded.
  • The per-baumuster feature catalog returns about 350 to 413 components per variant in one unpaginated response.
  • Lebanon, Jordan, Iraq and Palestine return a 65-byte stub instead of a catalog.

Feature sources​

Three sources have feature data at different levels.

  • nd_listing's equipment[].label is the per-vehicle factory specification, and its features is a controlled keyword vocabulary (AIRCONDITIONING, ALLOY, UPHOLSTERYLEATHER) set on every vehicle.
  • nd_configurator selectables is the per-baumuster catalog. Each component has its code, taxonomy, selected, standard, fixed and hidden flags, images and price information. The client splits every response into one row per vehicleComponents entry and repeats the envelope on each row. A row is then about 11 KB instead of 600 KB, and the table can be browsed from a SQL client. About 900 HTTP calls per partition expand to about 310,000 rows.
  • nd_configurator selectables-names is a region-wide dictionary of about 4,200 OEM codes to English labels. Selectables uses about 45% of them. Most of the rest are engineering and pre-installation codes that never appear in MENA. A few customer-facing Digital Extra: … codes appear only here. The endpoint has no Arabic equivalent.

Fields in the schema that are always null​

  • Tech specs: engine.*, performance.*, technical.acceleration, maxSpeed, the efficiency values, emission.*, dimensions.*, weight.*, ncap.*.
  • Per-VIN option codes: equipment[].code, identifiers.baumuster, nccConfigId, mpvCode, oemVehicleCode, cap, wheel, upholstery, interiorDescription, colour.exteriorRoof.
  • Order dates: consignmentDate, purchaseAtDate, availability.leadTime.

range.* and electricAttributes.* are null on the petrol vehicles sampled and were not tested on a BEV.

There are two consequences of the missing per-VIN option codes. The selectables-names dictionary has no join key onto inventory, so it is a standalone raw table. COSY renders cannot be built either, because they are keyed by baumuster plus option codes. A vehicle's images array holds dealer-uploaded photos on Net Director's S3 bucket instead. The transformed tier recovers wheel, upholstery and trim descriptors by keyword extraction over equipment[].label and colour.interior.

No MENA endpoint prices an individual option. The listing options preview, the configurator and the detail pages all omit per-option prices.

Dealer hierarchy​

Each vehicle includes the location block of its rooftop: hash, the full address, coordinates, phoneNumber and openingHours. It also has groupHash, franchiseHash and companyHash[] at the top level. The dealer entity can be built at rooftop, group, franchise or company level. Build it with one row per rooftop, keyed on location.hash, and keep the other three hashes on the row so downstream code can aggregate by them.

A country's stockScope names hashes at whichever level that market routes through. It therefore gives a lower bound on the rooftop count. Some countries route through a single franchise or group, and the number of rooftops underneath is unknown. Count the distinct location.hash values over the listing rows to get the real number.

Why locations has its own source​

The listing feed names only the dealers that hold stock. getAllLocations returns every rooftop, including service centers and certified pre-owned showrooms that never appear in inventory-derived dealer data.