Verification API

Verify students

Institution-verified login in two API calls — no document uploads, no password handling, no credentials stored.

Try

Powers verification for teams at

HubSpotDelivery HeroH&MKaDeWe

Built on global identity infrastructure

Studid is a registered service provider in DFN-AAI and eduGAIN, the international federation connecting 70+ national research and education identity federations.

Federations
70+
Institutions
User data stored
None
Integration time
8 min

How it works

Your user clicks "Sign in with your university". We handle everything in between.

No document uploads, no password handling, no SAML expertise on your side. The university's own login page — including any institutional MFA — becomes your proof of academic affiliation.

Your appredirects the user2 API calls. No SAML.SStudidbrokers SAMLUniversitysigns the loginuser's SSO+ institutional MFA

The user always authenticates at their own institution — Studid never sees their password, and neither do you.

1

Create a verification

Your backend calls the Stud API with a secret token, a callback URL, and a service name. You get back a verification ID and a link. Two lines of code.

POST /v2/auth/verification

2

User authenticates at their institution

Redirect the user to the link. They pick their institution from our searchable directory and log in through their existing institutional SSO — complete with whatever MFA their university requires.

SAML flow handled by Stud

3

Check the result

After the user returns to your callback URL, poll the verification status endpoint. You get an institution-verified identifier and the institution's identity. Done.

GET /v2/auth/verification/{id}

Why Studid

Institutional login beats document uploads

Don't ask users to photograph transcripts or student ID cards. Let them prove their academic status with the institutional login they already use every day.

Global reach

Thousands of institutions across 70+ federations — from Germany's DFN-AAI to the US InCommon and Japan's GakuNin.

No SAML knowledge needed

Two API calls: create a verification, then check the result. We handle metadata, certificate exchange, and protocol.

No user data stored

No document uploads, no password collection, no identity data retained. Users authenticate with their institution — you never see credentials.

Institution-verified

Every login is backed by the institution's identity provider and MFA. You get a verified institutional identifier, not a self-attested claim.

Free. No catch.

No accounts, no API keys, no rate-limited tiers. The verification API is free now and will remain free.

FAQ

Frequently asked questions