Provenance

What is real here

The marketplace reads one of two worlds, chosen in the header: the test data, fabricated so every feature can be explored, or the live RacingEdge API. This register says, for every destination, whether the screen is built and what it reads live. You are looking at Live API: Listings served by the RacingEdge API for brand RE at stage.racingedge.com.

Destination	Address	Screen	Live API	What it reads, and what it cannot yet
Buy	/	Built	Live	Every filter, count and sort goes to POST /api/listings/live/search, and the counts, year and mileage histograms are its facets. Only ticking several listing currencies at once stays on the test data (the API takes one); there is no price histogram live. A car with a published passport wears its mark (hasPassport on every hit), and "Has a car passport" filters on it (hasPassport: true, counted as a facet).
Listing	/listings/:id	Built	Part live	GET /api/listings/{id} and GET /api/listings/{id}/more, with the member's token so the heart is theirs; the heart saves to the account (POST / DELETE /api/favorites/listing/{id}). The comments (GET /api/listings/{id}/comments) are read once signed in. The owner submits a draft (POST /api/listings/{id}/publish), deletes it (DELETE /api/listings/{id}), or unpublishes a live listing to edit it (POST /api/listings/{id}/unpublish). A member makes, changes and withdraws an offer (POST /api/listings/{id}/offers, …/withdraw); the owner reads the offers (GET /api/listings/{id}/offers) and accepts or declines each (…/accept, …/decline). A buyer opens their chat with the seller (POST /api/chat/listing/{id}); the owner sees every buyer's chat (GET /api/chat?listingId=). On the test data nobody chats. A signed-in member reads the car passport the seller published (GET /api/listings/{id}/passport); on the test data anyone reads the six that private sellers published (Specimen.Passports). Signed out on the live API, a listing whose hasPassport is true says it has one and offers sign-in; nothing of it is read. In the passport's section a buyer asks the car a question (Ask this car: GET /api/listings/{id}/questions/suggested, POST /api/listings/{id}/questions), answered by AI from what the seller published, each statement cited; on the test data five prepared questions a car, answered by code (Specimen.Answers). A car for the track shows the RacingEdge Events track days coming up (GET /api/events/public, anonymous, kept five minutes), each opened in full (GET /api/events/public/{id}) and booked on RacingEdge Connect, a member handed over signed in (POST /api/auth/sso/code, service connect); on the test data, eight made-up events (Specimen.Events).
Car passport	/listings/:id/passport	Built	Live	The seller's car passport, for a listing made from a paddock car (vehicleId): build it (POST /api/vehicles/{id}/passport), read it through (GET …/passport?wait=10), write their own summary or go back to the AI's (PUT …/passport/summary), publish it on the listing or take it off (POST / DELETE …/passport/publish). The AI summary needs "AI helpers working with private data" (PUT /api/settings/ai), offered where it is off. The page draws the record and the Key facts exactly as buyers will read them, and names every place they appear (the listing, Compare). Buyers read it on the listing (GET /api/listings/{id}/passport). Live only: the test data has no paddock, and its six passports are read on their listings, already published.
Saved	/saved	Built	Live	A verified member on the live source sees their account's saved listings (GET /api/favorites/listing), and signing in moves this browser's live shortlist there. Anyone else's are held for this browser only.
Compare	/compare	Built	Live	Two to four listings chosen on the Saved page, side by side, each read afresh (GET /api/listings/{id}); the best price, year, mileage and owners in a row are marked. The ids are in the address, so a comparison can be sent. A signed-in member reads each seller's published car passport beside the page (GET /api/listings/{id}/passport) under "From the car passport", none of it marked best; on the test data anyone reads the six (Specimen.Passports).
Sell	/sell	Built	Live	A verified member's draft is saved to their account (POST /api/listings), with the photos and video uploaded as they are chosen (POST /api/files?context=LISTING_MEDIA) and named in order, the first photo the cover. Submitting saves the draft, then publishes it (POST /api/listings/{id}/publish): it waits for approval. A car from My Paddock (vehicleId) is left out. On the test data the whole flow works in this browser.
Edit listing	/sell/:id/edit	Built	Live	A verified member's draft opens from their account (GET /api/listings/{id} with the token), its photos in order with the cover first, and saves back with POST /api/listings/{id}. A listing that has left draft is not edited here. On the test data, a draft written in this browser.
My listings	/my-listings	Built	Live	A verified member's listings in every status, a tab per status, with the offers and the deal of each (GET /api/listings/my). Signed out or unverified, the page says what to do and asks the API nothing. On the test data, the drafts written in this browser.
Deal	/deals/:listing_id/:offer_id	Built	Live	One deal for its seller or buyer, built from escrow.stage (GET /api/listings/{listingId}/offers/{offerId}): the deposit request, paying it with the fee shown first, the conditions, releasing it, the final balance, handover with the VIN, and cancelling (…/escrow/*). Live only: the test data has no deals.
Saved searches	/searches	Built	Live	The member's saved searches (GET/POST/PATCH/DELETE /api/saved-searches), saved from "Save search" on the search page as the body the search sends; each opens its search, and its alerts (SAVED_SEARCH_MATCH) are switched on or off. Live only.
Chats	/chats	Built	Live	Every listing chat of the member's, buying and selling, the newest message first, with who it is with, the last message and the unread count (GET /api/chat?audience=marketplace). The listings being bought are read beside the page (GET /api/listings/{id}, at most 20) for their titles in the member's language. Read again on a push about a chat. Live only.
Chat	/chats/:id	Built	Live	One listing chat, buyer and seller (GET /api/chat/{id}, …/messages, POST …/messages): text, the buyer's offer as a card the seller accepts or declines from, and private files (POST /api/files?context=CHAT_ATTACHMENT, opened through GET /api/files/{id}/link). The car is named in the reader's language (GET /api/listings/{id}). Read again every ten seconds while open. Live only.
Notifications	/notifications	Built	Live	The member's inbox (GET /api/notifications, a page at a time by its cursor), all or unread, by category, with the unread counts (GET /api/notifications/unread-count); opening one marks it read (POST /api/notifications/{id}/read), and all at once (…/read-all). The switches per category and channel (GET and PUT /api/notifications/preferences). The bell in the header shows the count and the newest, kept up by RacingEdge's socket (/api/ws/notifications), held on the server for each open page. Live only.
Plan	/plan	Built	Live	The member's owner plan, which publishing needs (GET /api/paddock/plan, the catalogue from GET /api/paddock/plans). Choosing one opens Stripe Checkout (POST /api/paddock/plan/checkout); Manage plan opens Stripe's Customer Portal (POST /api/paddock/plan/portal). Stripe returns to RacingEdge Connect's /plan until re-back returns a checkout begun here to this page. Live only.
Account	/account	Built	Live	The member's account currency, GBP, USD or EUR, the same in every RacingEdge application (GET and PATCH /api/auth/me, then POST /api/auth/refresh-token so the token carries it), both AI switches (GET and PUT /api/settings/ai), and the language listings are read in (GET and PUT /api/settings/language). Live only; anyone chooses the language from the footer, kept in the cookie.
Sign in	/sign-in	Built	Live	POST /api/auth/token without a service, for a marketplace token held in the encrypted session cookie. GET /sso redeems a one-time code from another RacingEdge application (POST /api/auth/sso/token). On the test data nobody signs in.