Choose a public contact page
Contact discovery reads one public page of static HTML and organization markup. An official contact, support or about page is a useful starting point. The request accepts a URL and returns published emails, explicit phone contacts, social links and suggested contact pages, with up to 50 results per category.
Suggested contact pages are links for you to inspect. pageflock does not fetch them automatically. Running discovery on another page is a separate request and a separate one-credit charge when successful.
Published does not mean verified
A published email means the address appeared in the fetched page. The returned source evidence helps you check where it came from. It does not prove that the mailbox accepts mail, that the address still belongs to the organization, or that the recipient has agreed to receive a message.
pageflock does not generate guessed addresses, perform mailbox verification or visit social profile pages through this endpoint. A social link identifies a link in the source, not verified ownership. Keep those distinctions in your own application’s labels.
Handle an empty result
A successful page with no contacts uses one credit. The page may not publish contact information, or its contact widget may require JavaScript. Check the original source and any suggested public contact pages before trying another request.
Keep the source URL with each contact you retain, and refresh information when your use case needs current evidence. Choose a retention period and respect requests to remove contact information from your own downstream systems.
POST /api/pageflock/v1/contacts
{"url":"https://www.w3.org/Consortium/contact"}