List location pages
Every published location page (one per town or area you serve), with cursor paging. Same key as posts.
Location pages are separate from posts: one page per place you serve or want to win ("Milk Delivery in Sunderland"), written as fields your own template lays out. Your site reads them with the same rvc_ key it uses for posts and serves them wherever your location pages live, /locations/{slug} by default. Ask Revnu to change that address if yours differ. Location pages are turned on per account by Revnu; on other accounts this list is empty.
curl -H "Authorization: Bearer $REVNU_CONTENT_API_KEY" \
"https://revnu.com/api/content/v1/locations?limit=100"Query
| Param | Meaning |
|---|---|
limit |
Default 100, up to 200. |
cursor |
The cursor from the previous page (the last slug it returned). |
Response
{ "blog": {…}, "locations": [summary, …], "cursor": "…" | null }. Each summary carries slug, place, region, country, availability, title, metaDescription, canonicalPath, canonicalUrl, publishedAt and updatedAt. Keep requesting with the returned cursor until it is null. A page missing from the list was unpublished or deleted: remove it from your site and sitemap.
availability is available where you serve today and coming_soon for a place you don't yet. Show your waitlist or sign-up on a coming_soon page.
Keeping cached pages fresh
If your site caches pages (at build time or on a CDN), the rebuild hook in Content API also fires for location pages: { "event": "location.published" | "location.updated" | "location.deleted", "blogSlug", "locationSlug", "updatedAt" }. Purge or rebuild /locations/{locationSlug} and re-fetch it. Post events carry postSlug instead.