ORCID Member API

The ORCID Member API is the paid, OAuth-scoped tier of ORCID’s API, available only to organizations that hold ORCID membership, that lets a trusted party (an institution, publisher, funder, or recognition service the researcher has authorized) read and write specific sections of a researcher’s ORCID record on the researcher’s behalf. It is what makes ORCID integration possible: a university CRIS pushing a verified employment affiliation, a publisher adding a work at the moment of publication, or a peer-review recognition service logging a completed review — none of which a researcher can enter themselves for that last case. The free ORCID Public API tier, by contrast, is read-public-only: it can look up a record’s visible fields and collect authenticated iDs, but it cannot write anything.

What makes something a Member API integration

An integration is a genuine Member API use, rather than Public API lookup, when all three of the following hold:

• The calling organization holds ORCID membership (direct or consortium), which is what unlocks Member API credentials in the first place — Public API access requires no membership.
• The call writes, updates, or deletes record data (or reads a section, such as private/trusted-parties-visible data, that the Public API cannot see), rather than only reading what is already publicly visible.
• The write is authorized by an OAuth scope token the researcher explicitly granted to that specific trusted party — ORCID’s permission model (public / trusted-parties / private) still governs what happens to the data afterward, and the researcher can revoke access at any time.

Both API tiers are versioned together (currently 3.0) and expose the same underlying endpoints — /record, /works, /employments, /educations, /fundings, /peer-reviews, /qualifications — the difference is entirely about which tier can call them and with what permission.

Worked examples

Example 1 — institutional affiliation assertion. A university’s CRIS or HR system is registered as an ORCID member integration. When a researcher joins, they are prompted to sign in to ORCID and grant the institution write permission. The CRIS then uses its Member API credentials to push a verified employment affiliation onto the researcher’s record, flagged as institution-asserted rather than self-asserted. This is the mechanism behind what CASRAI documents as ORCID record permissions: a reader of the public record can distinguish a claim the researcher typed in themselves from one an accredited organization vouched for.

Example 2 — peer review credit that cannot be self-entered. Per ORCID’s own documentation, peer review items can only be added via the API — a researcher has no form field to add one directly. A journal, publisher, or a third-party recognition service (acting as a trusted party with the reviewer’s authorization) uses Member API write access to log the completed review, grouped under the convening organization’s group tag. Without a Member API relationship somewhere in that chain, verified peer-review credit cannot reach an ORCID record at all.

Counter-example

A grants office searching the public ORCID registry to confirm an applicant’s iD, or a repository doing a one-off lookup of a corresponding author’s public works list, is using the free Public API (or even just the public web search) — no membership, OAuth write scope, or trusted-party relationship is involved. Requiring researchers to hold an ORCID iD, or reading what is already publicly visible on a record, does not require an institution to become an ORCID member at all.

Membership and cost structure

ORCID Inc., the non-profit that operates the registry, sells membership in two structures, per its own published fee schedule (info.orcid.org/membership):

• Direct membership — open to any organization, priced by organization type and revenue band, with a lower-cost “Basic Access” tier and a higher “Premium Access” tier (more API credentials, record-update notifications, Affiliation Manager access). Non-profit and government organizations receive a reduced rate versus commercial organizations, and start-ups below a revenue threshold receive a further reduction.
• Consortium membership — for non-profit/government organizations only, joining through a consortium lead (for example, a national ORCID consortium); per-member fees scale down as consortium size grows, and organizations in lower-income countries receive substantial discounts through ORCID’s Membership Equity Program.

Both membership levels include Member API access; Premium tiers simply grant more API credentials and additional tooling. Fee figures move over time — check info.orcid.org/membership directly for current numbers before quoting one to a budget holder.

Why this matters to a research office

The practical reason a research office cares about Member API access, rather than treating ORCID as “just an iD lookup,” is what it enables operationally:

• Affiliation disambiguation for reporting. Institution-asserted employment/education entries, pushed via Member API, are more trustworthy inputs to funder and government research-output reporting than self-asserted text fields, because they carry the weight of an accredited organization’s authorization.
• Funder acknowledgement and compliance. Funders that require grant-linked publications to carry a verified ORCID iD (several major funders now do) rely on the funding record being pushed or confirmed through a Member API relationship somewhere in the chain — publisher, funder system, or institution.
• CRIS integration. Systems such as Pure, Symplectic Elements, and comparable research-information systems use Member API credentials to keep institutional and ORCID records synchronized in both directions, rather than requiring manual re-entry.
• Open-metadata commitments. Institutional ORCID membership (often via a national consortium) is frequently how a university operationalizes a broader open-research-infrastructure commitment, alongside participation in ROR and Crossref Funder Registry use in metadata deposits.

Frequently asked questions

Does my institution need to be an ORCID member to require ORCID iDs from applicants or researchers?

No. Requiring or collecting an ORCID iD, and reading a record’s publicly visible fields, uses the free Public API and needs no membership. Membership is only required to push institution-asserted data (affiliations, funding, etc.) onto a researcher’s record on their authorization, or to read data the researcher has restricted to trusted parties.

What is the actual difference between the Member API and the Public API?

Both expose the same record sections and are versioned together, but the Public API is free and read-public-only. The Member API is restricted to paying ORCID member organizations and supports authenticated read (including trusted-parties-visible data) and write/update/delete, scoped per record by an OAuth token the researcher grants to that specific organization.

Can a small organization or an individual supervisor get write access without full institutional membership?

ORCID membership is organizational, not individual — an organization (direct or via a consortium) holds the credentials, not a single staff member. Organizations weighing whether integration is worth the fee should look at consortium membership through a national or disciplinary ORCID consortium, which is typically far cheaper per organization than direct membership.

Does Member API access change what is publicly visible on a researcher’s ORCID record?

No. Visibility of any item — public, trusted-parties, or private — is set by the researcher (or defaults set by their institution at account creation) and applies regardless of which API tier reads or wrote it. Member API access controls who can write and who can read restricted data; it does not itself change an item’s visibility setting.

Related terms

ORCID iD · ORCID API · ORCID record · ORCID record permissions · ORCID consortium · ORCID employment · ROR ID · Funder ID

References

• ORCID Inc., “ORCID API Documentation v3.0” (members.orcid.org/api).
• ORCID Inc., “Membership” fee schedule (info.orcid.org/membership).
• ORCID Inc., “ORCID Record” integration guide (info.orcid.org/documentation/integration-guide/orcid-record/).