Why don’t you integrate with LinkedIn to verify Requesters’ profiles?

Never say never — but for now, we’ve chosen not to use LinkedIn’s Single-Sign-On (SSO) for verification.

Why

The reasons are partly technical and partly about data sharing.
Even lightweight SSO connections involve limited data exchange with LinkedIn, and we prefer to avoid any external dependencies or silent data flows.
Instead, we rely on a manual verification method that’s transparent to both Requesters and Respondents.

How verification works

We use a system of text keys — unique codes that Requesters add to their LinkedIn “About” section.
If you own an internet domain, you'll recognize this works like DNS TXT-record verification for domains:
the “verifier” is the Respondent, who can visit the Requester’s LinkedIn profile and confirm that the key is present.
It’s privacy-preserving, simple, and verifiable by anyone without needing an API connection or third-party app permissions.