The ORCID Premium Member API (application programming interface) provides instructions for the structure and elements needed within a digital system, for that system to integrate/communicate with the ORCID registry. Institutional members are granted credentials for integrating ORCID with 5 systems. The ORCID Collect & Connect Program provides a 5-step iterative process for meeting best practices in the technical aspects of integration.

Integrations begin in a sandbox environment before receiving production credentials. To get started, register for sandbox credentials, and consult the ORCID US Planning Guide.

Technical Support Resources:

Any software platform that uses person-based data (names, works or affiliations attributed to a person) can benefit from connecting with ORCID via the ORCID API. Many systems either already support ORCID or can be configured locally to connect with ORCID. Some systems do not yet support ORCID. The list below provides ORCID-related information on some commonly used systems in the US (this list is not comprehensive). Questions about this list should be sent to orcidus@lyrasis.org.

Common Systems for ORCID Integration:

  • arXiv - users can authenticate and connect their ORCID iD with their arXiv works, ORCID iD displayed on author page, see documentation.  

  • Banner - does not have ORCID built-in, but can be configured to store ORCID iDs and other data from the ORCID API via a custom ORCID “Create or Connect” application. To request that Banner integrate ORCID functionality directly into their product, please contact them using our email template.

  • Converis - allows for ORCID iD authentication as well as both importing and exporting publications between Converis and ORCID; see documentation. Users can search for publications in Web of Science or ORCID based on ORCID iD. Additional ORCID functionality is expected for future releases, stay tuned for updates.

  • Digital Measures - allows users to authenticate and connect their ORCID iD with their Digital Measures profile, and allows for importing publications data from ORCID into Digital Measures, see documentation. Users should contact Watermark directly to request additional functionality, such as importing additional ORCID data and writing to ORCID, using our email template.

  • DSpace - ORCID is currently not built in out of the box (although there are plans for this in future versions), but DSpace can be configured to work with the ORCID API, and ease of ORCID integration depends on what version of DSpace is being used. For example, see ORCID documentation for DSpace 6.x. Duke University has integrated ORCID into their DSpace instance, DukeSpace, see example and documentation.

  • Editorial Manager - provides support for ORCID; see ORCID’s website for details.

  • eJournalPress - provides functionality for allowing users to sign in using ORCID, options for allowing collection of authenticated ORCID iDs for each author, and allows journals to take advantage of the ORCID reviewer credit functionality for writing peer review activity to users’ ORCID records. Slides showing the ORCID options are available, as well as full detailed documentation of the platformContact EJPress support to turn on ORCID configurations.

  • ePrints - two ORCID plugins are available: ORCID Support (includes manual entry ORCID iD field, and displays iDs on user profile and publication pages) and ORCID Support Advanced (recommended: associates authenticated iDs with user profiles, displays iDs on user profile and publication pages, pulls works data in from ORCID, pushes works and affiliations data to ORCID). See documentation and more information.

  • Esploro – The 2020 development roadmap for Esploro includes integration with ORCID to enable both pushing content from Esploro to ORCID and pulling content from ORCID to Esploro. Once the integration is ready, ORCID functionality can be enabled using institutional member ORCID API credentials, which the customer will need to configure into the system. For more details, contact Esploro.

  • Faculty180 - allows for ORCID authentication and importing publications, employment, education, funding, and biography data from ORCID to Faculty180, see details. Access to the ORCID functionality, if it is turned on for your institution, is available in the “Vitas and Biosketches” menu of Faculty180; further details can be found by searching the Faculty180 help system for “ORCID”. To request more ORCID functionality from Faculty 180, such as writing data from Faculty 180 to ORCID, please contact Faculty 180 using our email template.

  • Fedora - can be configured to work with ORCID, typically as part of a Samvera or Islandora repository. See Samvera and Islandora respectively for details.

  • Figshare - Figshare can associate authenticated iDs with user profiles, display iDs on user profile pages, generate Datacite DOIs with iDs included in metadata, and push works to ORCID via Datacite. See Figshare blog and documentation for details.

  • InfoEd - provides ability for researchers to connect their ORCID iD with their InfoEd profile. Additional future development is anticipated but not specifically scheduled at this time; if you are an InfoEd customer, please contact them using our email template to request additional ORCID functionality such as importing data from ORCID or writing data from InfoEd to ORCID.

  • Islandora - can be configured locally to work with the ORCID API. For Islandora 8 (CLAW) ORCID is on the radar for inclusion; please add comments to the GitHub ticket to help with prioritization. For Islandora 7, the LASIR (Liberal Arts Sprint for Institutional Repositories) project also includes ORCID integration; see LASIR executive summaryGitHub, and the Islandora IR Interest Group page.

  • Open Journal System - an ORCID plugin for OJS version 3 allows authors to authenticate their ORCID iD in their OJS profile and automatically pull in data from their ORCID profile, like their name and iD. An enhanced plugin for OJS 3.1.2 is now available, to allow for publication data to be written from OJS to the author’s ORCID record, see demo. Full documentation for enabling the plugin can be found at https://docs.pkp.sfu.ca/orcid/en/

  • PeopleSoft - does not have ORCID built-in, but can be configured to integrate with the ORCID API via an additional database or enterprise data warehouse. For example, Boston College has integrated ORCID with PeopleSoft, including the ability to authenticate ORCID iDs and write employment data to ORCID from PeopleSoft, see demo (1:55-8:35). To request that PeopleSoft integrate ORCID functionality directly into their product, please contact them using our email template.

  • Pivot - Pivot allows users to authenticate and link their ORCID iD and read information from ORCID, see documentation. To request additional ORCID functionality, such as writing data to ORCID from Pivot, please contact them using our email template.

  • ProposalCentral – ProposalCentral is a cloud-based platform for grant award application and reporting workflows. ProposalCentral allows users to log in using their ORCID iD and connect their authenticated ORCID iD to their ProposalCentral profile. Data is read from ORCID records allowing for re-use of ORCID data in grant applications, while also providing insight about the impact of funding programs beyond the life of granted awards. ProposalCentral also allows funders to write funding award information to researchers’ ORCID records.

  • Pure - Pure allows for exporting/writing publication data from Pure to ORCID, and displays ORCID iDs on user profiles. See demo video. Version 5.13 adds ability to read works from ORCID records and assert/write institutional affiliations and works to ORCID records.

  • Salesforce - does not have ORCID built-in, but may be able to integrate with ORCID via an additional database or enterprise data warehouse. To request that Salesforce integrate ORCID functionality directly into their product, please contact them using our email template.

  • Samvera - can be configured to work with the ORCID API via the Samvera Labs ORCID Gem or a customized approach. University of Virginia has integrated ORCID as a microservice with two of their institutional repositories, see documentation.

  • Symplectic Elements - Elements allows researchers to authenticate & connect their ORCID iD, granting permission to import data from ORCID into Elements. Elements can then search ORCID for any Publication-IDs associated with ORCID works and use them to harvest publications to auto-claim for the researcher. See demo video. Elements also has added the ability to write works and employment affiliations from Elements to ORCID. Watch this webinar recording for more information.

  • Vireo ETD submission - Vireo 3 has a field for ORCID that validates the ORCID iD number and name of a user, see demo. Administrator's view has settings to turn ORCID validation/authentication on or off. ORCID iDs can be exported in repository XML files. Vireo 4 is currently in development. Questions should be sent to the Vireo listserv.

  • VIVO - VIVO can be configured to allow users to authenticate and connect their ORCID iD with their VIVO profile. More information and detailed instructions can be found on the DuraSpace Wikivideo tutorial, and blog post.

Common Systems that do not yet support ORCID:

  • Academic Analytics - Academic Analytics is an ORCID member but currently does not have an authenticated ORCID integration. To request ORCID integration functionality for the future, please contact Academic Analytics using our email template.

  • BePress/Digital Commons - currently BePress does not support authenticated ORCID functionality. Digital Commons allows for manual entry of ORCID iD the in Expert Gallery profile system, however this field is not authenticated so it does not meet best practices. See BePress’ roadmap and update for more info. To request ORCID integration functionality for the future, please contact BePress using our email template.

  • BePress ExpressO - currently BePress ExpressO does not support authenticated ORCID functionality. To request ORCID integration functionality for the future, please contact BePress using our email template.
  • Cayuse - ORCID appears to be on their radar, but Cayuse is not yet integrated with ORCID. To request ORCID integration functionality for the future, please contact Cayuse using our email template.
  • eScholarship - currently does not support ORCID functionality, see more information.

  • Huron - Huron is not yet integrated with ORCID. To request ORCID integration functionality for the future, please contact Huron using our email template.

  • Kuali - Kuali is not yet integrated with ORCID. To request ORCID integration functionality for the future, please contact Kuali using our email template.

  • LawArXiv - currently does not support authenticated ORCID functionality. To request ORCID integration with LawArXiv, please contact them using our email template.
  • ProQuest ETD submission - the ProQuest form has a field for ORCID but it requires manual entry, which does not allow for authenticated connection between ProQuest and ORCID, and allows for mistakes that could be made upon entry. To request that ProQuest make ORCID an authenticated field using the ORCID API, please send this email template to ProQuest.

  • Scholastica - currently does not support authenticated ORCID functionality. To request ORCID integration with Scholastica, please contact them using our email template.

  • SSRN - currently does not support authenticated ORCID functionality. To request ORCID integration with Scholastica, please contact them using our email template.

  • SurveyMonkey - Some institutions would like to use SurveyMonkey to gather authenticated ORCID iDs from their users. SurveyMonkey offers several API integrations, but does not yet offer support for the ORCID API. To request the ability to gather authenticated ORCID iDs via SurveyMonkey, please contact them using our email template.

  • Workday - does not have ORCID built-in, but may be able to integrate with ORCID via an additional database or enterprise data warehouse. To request that Workday integrate ORCID functionality directly into their product, please contact them using our email template.

Other ORCID-integrated Platforms:

  • Environmental Molecular Sciences Laboratory (EMSL) - see demo

  • Hein Online - see documentation

  • Modern Language Association (MLA) - see demo

  • NASA Astrophysics Data System - see documentation

  • Overleaf - see demo

  • SCOPUS - see demo

  • SciTech Connect (US Department of Energy Office of Scientific and Technical Information) - see documentation

  • Web of Science - see demo

  • Zenodo – allows users to log in using ORCID, and enable ORCID iD icon next to their name in the “Authors” information section when they upload works to Zenodo. Authors can import works data from Zenodo to ORCID using the DataCite search & link wizard in the Works section of the ORCID record