Email Scraper Health and Metadata for Email Scraper
Use this endpoint to verify scraper status and available modes. It is part of StackDeal's email scraper surface, which starts with a quick proof point and expands into a full workflow.
What does email scraper health and metadata do?
This GET endpoint lets developers verify scraper status and available modes. It is one of the public StackDeal docs pages meant to capture technical intent while still routing evaluators into the broader email scraper workflow.
How to use this endpoint page
A strong endpoint page should make the contract obvious, show what a useful first request looks like, and explain how the output fits into the sample-first StackDeal motion instead of reading like a disconnected API stub.
Understand the route and method
This endpoint uses GET on /email-scraper. Start by clarifying what input it expects and why this route exists inside the broader workflow.
Review a realistic first request
Use a realistic first input like none so the buyer can imagine the endpoint in a real integration or test flow.
Connect the output to StackDeal execution
The result should not stop at the API response. The point is to move the output into StackDeal for enrichment, prioritization, routing, or market execution.
Frequently asked questions
Who is this endpoint best for?
This endpoint is best for developers who need to verify scraper status and available modes and want to keep the result connected to a broader StackDeal workflow.
Should I start with the API or the free sample?
Start with the API if you already know the workflow fits, but the public sample pages are still useful for fast validation and stakeholder buy-in.
Why publish endpoint pages publicly?
Public endpoint pages capture technical search intent, support AI citations, and give evaluators a cleaner trust path before they commit to trial or demo.