Automate CORE
HumDay reads CORE’s own published API description and derives 18 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What CORE is
You can use the CORE API to access the resources harvested and enriched by CORE. If you encounter any problems with the API, please report them to us . Overview The API is organised by resource type. The resources are articles , journals and repositories and are represented using
API host: core.ac.uk
What HumDay can do in CORE
9 documented operations change something in CORE.
- POSTBatch operation for search through all resources
/search - POSTBatch operation for search through articles
/articles/search - POSTBatch operation for search through journals
/journals/search - POSTBatch operation for searching through repositories
/repositories/search - POSTBatch operation for retrieving articles by CORE ID
/articles/get - POSTBatch operation for retrieving journals by ISSN
/journals/get - POSTGet all near duplicate articles
/articles/dedup - POSTGet articles by similarity to a text
/articles/similar - POSTBatch operation for retrieving repositories by CORE repository ID
/repositories/get
What HumDay can read from CORE
These are the operations a schedule or a trigger can watch.
- GETSearch through all resources
/search/{query} - GETSearch through all documents
/articles/search/{query} - GETSearch through journals
/journals/search/{query} - GETSearch through all repositories
/repositories/search/{query} - GETFind journal by ISSN
/journals/get/{issn} - GETGet article by CORE ID
/articles/get/{coreId} - GETGet repository by CORE repository ID
/repositories/get/{repositoryId} - GETGet article history by CORE ID
/articles/get/{coreId}/history - GETGet fulltext PDF by CORE ID
/articles/get/{coreId}/download/pdf
How automating CORE works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live CORE account.
- Grant access, then go live. You approve the specific CORE operations it may use — and only those.
Automate CORE with these
- Monarchinitiative BioLink164 operations
- UniCourt Enterprise158 operations
- OSF APIv2 Documentation156 operations
- IllumiDesk143 operations
- Figshare136 operations
- MCW Rat Genome Database100 operations
- U.S. EPA Enforcement and Compliance History Online (ECHO) Detailed Facility Report (DFR)94 operations
- OpenFEC91 operations
- NBA Stats83 operations
- Thebluealliance The Blue Alliance65 operations
- eDRV57 operations
- Collegefootballdata College Football Data51 operations
Categories
Questions about CORE automation
- Can HumDay connect to CORE?
- Yes. HumDay reads CORE's own published API description and derives the operations from it, so there is no hand-built connector to wait for. 18 operations are documented.
- Do I need to write code to automate CORE?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your CORE account.
- What can HumDay do in CORE?
- 9 of the 18 documented operations change something in CORE, and 9 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my CORE account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to CORE is held behind that approval.
Where this came from
The operations above are read from a published API description for CORE at core.ac.uk/api-v2/doc. Descriptions are the provider’s own words, not ours. Last published 2019-07-22.