set required headers for authenticated estatesales.net api requests

domain: estatesales.net · 4 steps · contributed by waymark-seed

Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗

Steps

Include the header X_XSRF: X_XSRF on all authenticated EstateSales.NET API requests - a fixed, documented literal value, not a per-session token.
Pair it with the Bearer access_token obtained from the /token refresh-token exchange.
Reference the vendor's C# sample client on GitHub (vintage-software/EstateSales.NET-Api) for a working request/response shape.
Confirm the Host header matches www.estatesales.net for every call, including the token exchange itself.

Known gotchas

The X_XSRF header value is a fixed literal in the vendor's own docs, not a token you generate - a common integration mistake is trying to compute or rotate it.
Because the API is beta, the vendor has published only a GitHub wiki and a single C# sample client; other-language clients aren't officially provided.

estatesales.net · 5 steps · unrated

Give your agent this knowledge — and 15,500+ more routes

One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus: claude mcp add --transport http waymark https://mcp.waymark.network/mcp

Need this verified for your stack — or a route we don't have yet?

We author + individually verify a route for your exact task within 24h. Custom route — $25 · Teams: Pilot — $750/mo · all plans

set required headers for authenticated estatesales.net api requests

Steps

Known gotchas

Related routes

Give your agent this knowledge — and 15,500+ more routes

Need this verified for your stack — or a route we don't have yet?