All integrations
CORE logo

CORE

Research & Academia

Search and read CORE, the world's largest aggregator of open-access research: over 300 million papers harvested from institutional repositories, preprint servers, journals and publishers, deduplicated and enriched. Find papers and the repositories holding them, turn a DOI into a link to a free copy, pull PDFs and the parsed structure of a paper, count a field's output by year, author or publisher, and find the researchers working on a topic. Free, with an optional API key that raises the daily allowance and unlocks full text.

26 actions

Actions

Steps your workflow can run in CORE.

Search worksSearch CORE's collection of open-access papers. A work is the paper itself, with the copies harvested from different repositories deduplicated into one record, so this is the search for 'find me papers about X'. Filter by author, title, DOI, publisher, year, publication date, document type, repository, and whether CORE holds the full text.
Search outputsSearch the raw records CORE harvested, exactly as each repository supplied them. Use this rather than the works search when the question is about a particular copy: which repository holds it, what licence it carries, what the repository called it.
Search data providersSearch the repositories, preprint servers, journals and publishers CORE harvests from. Filter by country, by the software the repository runs, by metadata format, or by whether it is a repository or a journal.
Search journalsSearch the journals in CORE's collection by title, subject, ISSN or publisher. Journal records come from DOAJ members, Open Journal Systems repositories and publishers CORE aggregates directly.
Count works by fieldBreak a set of works down into counts instead of listing them: how much was published per year on a topic, which authors publish most on it, which repositories hold it, what document types it comes in. One call answers a question that would otherwise take thousands of paged results.
Count outputs by fieldBreak a set of harvested outputs down into counts by subject, contributor, language, or the date they were deposited or accepted. Deposit dates say when repositories actually took material in, which publication dates do not.
Count data providers by fieldCount the repositories CORE harvests, grouped by the software they run. The open-access repository landscape in one call: how many run DSpace against EPrints against OJS, optionally narrowed to one country.
Count journals by subjectCount the journals matching a search, grouped by subject: the subject map of a field's publishing landscape.
Get a workFetch one research work in full: title, abstract, authors, identifiers, journal, publisher, links, and the parsed full text. Takes a CORE ID, a DOI or a core.ac.uk link.
List a work's outputsList every harvested copy behind one work, the same paper as each repository holds it. Use it to find which repositories have a version, to compare their metadata, or to pick a copy whose licence allows what you want to do next.
Get a work's datesThe lifecycle dates CORE holds for a work: deposited, accepted, published and last updated. Useful for measuring how long a repository takes to make accepted work available.
Download a work's PDFDownload a work's PDF and keep it as a document a later step can read, attach or send on.
Get a work's parsed structure (TEI)Download the TEI XML CORE produced from a work's PDF: the paper taken apart into sections and headings, figures and tables, and a reference list with each citation split into author, title, year and DOI.
Get an outputFetch one harvested output in full: one repository's copy of a paper, with the metadata that repository supplied, its OAI identifier, its licence, its set memberships and its Sustainable Development Goal labels.
Get an output's datesThe dates CORE holds for one harvested output: deposited, published, accepted, created and last updated.
Get an output's harvest historyEvery version of an output's metadata CORE has harvested, so a workflow can see when a repository corrected a title, added a DOI or changed a licence, and when nothing has changed in years.
Download an output's PDFDownload one harvested output's PDF and keep it as a document.
Get an output's raw XML recordDownload the raw XML metadata record for an output, exactly as the repository's OAI-PMH endpoint served it, before CORE normalised anything.
Get a data providerFetch one repository or journal in full: its name and institution, its OAI-PMH endpoint and metadata format, the software it runs, its location, and its ROR and OpenDOAR identifiers.
Search a data provider's outputsSearch inside one repository's holdings, or list them all. The one CORE search that takes a sort order, so it is the way to ask a repository what it has added most recently.
Get a data provider's statisticsHow much content a repository has contributed: metadata records, and how many of those CORE holds full text for. Ask for more and you get the deposit history over time, the per-source breakdown, or one OAI set.
Get a journalFetch one journal by ISSN or by its CORE identifier: title, publisher, language, subject list, every identifier CORE holds for it, and the data provider supplying it.
Get a journal's statisticsHow much of a journal CORE holds: metadata records, records with full text, and how many carry a DOI.
Find a free copy by DOIGiven a DOI, find a link to a freely readable copy. CORE looks through its own index and then outside it, so this answers 'is there a version anyone can read' for a paper that is otherwise behind a paywall. A DOI with no free copy is reported rather than failing, so a reading-list workflow can branch on it.
Find related worksFind research related to a paper, or to a description of one. Point it at a CORE record, at another identifier, or at nothing but a title and an abstract, which makes it a literature search for a paper that has not been written yet.
Find experts on a topicFind the researchers publishing on a topic. Describe it the way you would for related works and CORE answers with people rather than papers: reviewers for a submission, collaborators for a grant, the group already working on your question.

Connect in a few clicks

Authenticate once and every action and trigger for the app is ready to drop into a workflow. No glue code, no maintenance.

Automate across your stack

Chain apps together with triggers, actions, and logic that move data between your tools automatically, so work happens without you.

Secure by default

Credentials are encrypted and scoped per workspace. Connect the tools your team already trusts with confidence.

Automate CORE with Lodol.

Connect CORE and build your first workflow in minutes. No credit card required.

Free plan available · No credit card required