BUILT IN PUBLIC

Changelog

What changed for partners, builders and agent developers, newest first.

  1. partner-api

    Opening the Partner API's base address in a browser leads to this site's documentation, instead of a not_found answer.

  2. storefronts

    A storefront registered from 2026-10-13 on serves its catalog, carts and orders from its first call, and gets a partner ID of LivingSocial for Agents' own, shown on its page and returned when you read your registration; a storefront registered earlier keeps the partner ID it has. Reading your own registration works again: from 2026-10-12 15:36 UTC it answered every storefront with the error PARTNER_API_MOVED.

  3. purchases

    A purchase made through LivingSocial and paid on Groupon's checkout shows in the buyer's account on customers.livingsocial.com, with its redemption code, on a page of its own they open on any device once signed in. It is theirs when the shopping session was attached to their email or phone, or when they keep it from the tab that paid.

  4. checkout

    The purchase status can now confirm a paid purchase from the order Groupon records for its cart, before the buyer's browser comes back from Groupon's checkout. When Groupon has not recorded the order, it still waits for that return.

  5. partner-api

    The Partner API has one address, https://api-core.livingsocial.com. Groupon's old partner gateway answers every partner call with 410 Gone and the new address in movedTo. Its old OpenAPI address leads to this site's Partner API document, and its old documentation pages lead to this site.

  6. orders

    A Partner API cart answers grouponOrderUuid, the Groupon order placed from its checkout once Groupon records it. Read that order to confirm the sale, even when the shopper never comes back to your site.

  7. files

    Any web page can read the OpenAPI documents, llms.txt, llms-full.txt and the API catalog: they allow cross-origin reads from every origin (CORS, without credentials). Swagger Editor, Redoc or an agent running in a browser page can load them directly.

  8. search

    Search returns offers in the order Groupon's own search ranks them, each offer read from LivingSocial's catalog.

  9. storefronts

    You upload your storefront's logo as a picture and frame it on the page, instead of typing its address. It is copied to Groupon's image CDN, so Groupon's checkout shows it.

  10. docs

    Name your client in its User-Agent header: the network in front of the API answers the default User-Agent of Python's urllib and of libwww-perl with a 403. The agent API's reference carries curl samples that run as written, for opening a session, searching and adding to the cart.

  11. cart

    A cart line holds 1 to 100 units on both APIs; the agent API allowed 50 before. An option's own limit can be lower.

  12. offers

    An offer's buy.route names the agent API's own route for adding to the cart. Before, it named a route outside the agent API.

  13. docs

    The documentation is split by reader: shopping with an AI assistant, and building on the Partner API. Each path has its own API documentation, View as Markdown gives a path's whole documentation in one file, and this site publishes the Partner API's OpenAPI document.

  14. api

    The agent API and the Partner API run in production at https://api-core.livingsocial.com, the server both OpenAPI documents name.

  15. api

    The agent API's OpenAPI document is generated from the code, so it matches what the API answers. A shopping session can be attached to the person's LivingSocial account by their email or phone.

  16. buying

    Buy links (offerUrl, buyUrl) on every offer, and one-call shopping sessions.

  17. pages

    Every page server-rendered with a Markdown twin; llms.txt, status.json and the changelog feeds.

  18. offers

    Merchant name, fine print and expiry now come with offers.

  19. hosting

    agent.livingsocial.com and customers.livingsocial.com live over HTTPS.

  20. catalog

    Eligible US Groupon offers added to the LivingSocial catalog.