v2.4.2

HTTP routes

This page lists the main deployed HTTP surface. SQS-driven local replay harnesses are documented on the relevant service pages and in OpenAPI with x-drive-deployment: local-test-http.

Auth key

MarkerMeaning
API keyRequires X-Api-Key at API Gateway.
Publicprivate: false in serverless.yml; handler may still perform its own token/signature checks.
Local harnessHTTP-shaped local replay path; deployed trigger is SQS or another event source.

Route groups

ServiceDeployed HTTP operationsLocal harnessesPrimary purpose
ads10Tagless ad payload generation.
autograb100Vehicle lookup, price gauge, residuals, valuation.
cachewarm20Cache-warm schedule creation and queueing.
canbus20Queue and write CAN bus/Timestream events.
cfs30Cars-for-sale external list and counts.
cloudflare10Add Cloudflare redirection.
geo20Country and city GeoIP lookup.
leads138Lead ingestion, config, public webhooks, queue entry points.
marketing61Insider contact/subscription/transactional email.
marketplace80Utility endpoints for marketplace colours, phone, click-to-call, finance, insurance.
ml10Image labels.
oly10Lease calculator.
purge60Cache purges, transitions, PurgeBot.
root10robots.txt.
social40Disqus and sharedcount.com counts.
syndication40Google/Facebook indexing and syndication feeds.
udp10Snowflake proxy.

High-risk route notes

ServicePathNote
leads/leads/in/fb/queuePublic Facebook webhook. GET is verification; POST ingests leadgen events.
leads/leads/in/process, /leads/out/* workersLocal HTTP harnesses only for most worker processors; deployed execution is SQS.
marketing/marketing/email/transactional/processLocal HTTP harness only; deployed execution is SQS from the transactional email queue.
purge/post/transitionValidation failures intentionally return 200 with result: "rejected".
purge/purge/botPublic Slack receiver; handler validates URL and allowed Slack handles before queueing.
social/social/sharecountAPI Gateway method is ANY; GET and POST are both documented.
social/social/commentcount, /social/sharecount-bulkHandlers contain POST branches, but only GET is mounted in serverless.yml.

Full operation detail

Use the per-service Scalar pages for complete request and response schemas:

To regenerate static docs and validate route/spec drift:

bash
cd docs/site
yarn build
Esc