Get a location page

GET/api/content/v1/locations/{slug}

One location page, render-ready: its fields, the copy as markdown and safe HTML, head metadata and JSON-LD.

curl -H "Authorization: Bearer $REVNU_CONTENT_API_KEY" \
  https://revnu.com/api/content/v1/locations/sunderland

Response

{
  "blog": { "creatorName": "…", "locationsBaseUrl": "https://www.example.com/locations", "…": "…" },
  "location": {
    "slug": "sunderland",
    "place": "Sunderland",
    "region": "Tyne and Wear",
    "country": "GB",
    "availability": "available",
    "title": "Milk Delivery in Sunderland",
    "canonicalUrl": "https://www.example.com/locations/sunderland",
    "intro": "markdown",
    "introHtml": "<p>…</p>",
    "sections": [{ "heading": "…", "body": "markdown", "html": "<p>…</p>" }],
    "areasServed": ["SR1", "Roker"],
    "facts": [{ "label": "Delivery days", "value": "Monday, Wednesday, Friday" }],
    "faqItems": [{ "question": "…", "answer": "…" }]
  },
  "headMeta": { "title": "…", "description": "…", "canonical": "…", "openGraph": {}, "twitter": {} },
  "jsonLd": [{ "@type": "Service" }, { "@type": "BreadcrumbList" }, { "@type": "FAQPage" }]
}

Put headMeta in the page head and each jsonLd entry in its own <script type="application/ld+json">. The Service schema names your business as the provider and the place and areasServed as the area served. Render on the server or at build time, like posts: AI crawlers don't run JavaScript.

An unknown or unpublished slug answers 404, the same as an unknown or revoked key. A missing or malformed Authorization header answers 401.