REST API

REST API overview

Plain HTTP and JSON over E2 Roofing Jacksonville's verified review data. No SDK, no key, no account. Make a request, get JSON back.

Base URL

All endpoints are served under a single origin. Relative paths in this documentation are resolved against it.

https://e2roofingreviews.com

Authentication

There is none. Every endpoint is public and read-only. Do not send an Authorization header — it is ignored. See Authentication for the full policy.

Content types

Responses are application/json (the JSON Feed endpoint returns JSON Feed v1.1, also JSON). Request bodies are only used by the MCP endpoint, which expects application/json. There is no XML or form-encoded variant for the read endpoints.

Conditional requests

Dataset and incremental endpoints emit an ETag (and, where applicable, a Last-Modified) header. Send the value back on the next request to avoid re-downloading unchanged data: a match returns 304 Not Modified with an empty body.

# First request — note the ETag in the response
curl -i "https://e2roofingreviews.com/api/reviews/since/2025-01-01"

# Subsequent request — echo the ETag back
curl -i "https://e2roofingreviews.com/api/reviews/since/2025-01-01" \
  -H 'If-None-Match: "<etag-from-first-response>"'
# → HTTP/1.1 304 Not Modified  (no body, no bandwidth)

Next

• Full API reference — every endpoint, parameter, and example.
• Interactive playground — run queries against live data in the browser.