← All use cases

Alumni & community

Confirm alumni status for membership perks and communities, or restore access for your institution's graduates.

The problem

Alumni networks, alumni job boards, and community platforms live and die on one thing: proving you studied at the school. For institutions, that means mailing lists of graduates and manual verification. For platforms that want to serve alumni communities, there is often no way to verify alumni status at all without the institution's cooperation.

The Studid way

Studid lets platforms confirm a user's former (or current) institutional affiliation through the login the user already has. Alumni can keep using their university account — often retained years after graduation — and the university's IdP confirms the affiliation in a signed assertion.

Your integration:

  1. Create a verificationPOST /v2/auth/verification
  2. Redirect the user to their university login through Studid
  3. Check the result — the session tells you which institution they belong to and how (student, alumni, staff)

What you get

  • entityId — the institution the user is (or was) affiliated with
  • authIdentifier — a persistent identifier for mapping to a community account
  • affiliations — role values including alum (former student) and member when the IdP releases them

Why it works for communities

  • Alumni-grade verification — distinguish current students from graduates, or grant access to both
  • Zero document handling — no diplomas, no transcripts, no "upload proof" forms
  • Works after graduation — many IdPs keep alumni accounts active, so alumni verify with the same login they used as students

Note: not every institution releases an alum affiliation to non-REFEDS services. When it's missing, entityId still conclusively identifies the institution — combine it with your own rules (e.g. "graduated after year X") as needed.

Get started

See the integration guide for the full API walkthrough, or try the live demo and verify a real institutional login in under a minute.

Works even without a persistent user ID

Some institutions only issue a transient identifier, so authIdentifier can be null. That is a normal outcome, not a failed login: the user still authenticated at a real institution, and entityId always proves which one. Use it for eligibility and bind the result to your own session token for continuity.

Ready to try it?

Authenticate with your university or research institute — no account needed, takes under a minute.

Read the guide