DataCite REST API

Name: DataCite REST API
Brand: DataCite REST API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsPackage Registrybasic13 EndpointsREST

For Agents

Register, update, and resolve research DOIs and pull associated metadata, citation events, and provider/client records from DataCite's PID infrastructure.

Install Jentic One Beta

Connect the DataCite REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the DataCite REST API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with DataCite REST API.

Update or hide an existing DOI's metadata, URL, or state via PUT /dois/{id}

Look up rich citation metadata for any DOI to populate citation widgets and reference lists

GET STARTED

Start building with DataCite REST API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use DataCite REST API for, with concrete tasks.

★ Repository DOI Minting

Institutional repositories use the DataCite REST API to mint DOIs at deposit time, attaching descriptive metadata (creators, title, publisher, resource type) so that newly archived datasets and theses become immediately citable. The POST /dois endpoint accepts a full DataCite XML or JSON metadata payload and returns a registered DOI along with its DataCite Commons landing page. Most repositories integrate this in under a week alongside their submission workflow.

Register a DOI for a new dataset titled 'Coastal Erosion 2026' with creator ORCIDs and resource type Dataset, then return the resolved DataCite Commons URL

Citation Metadata Lookup

Reference managers, citation widgets, and AI research assistants resolve DOIs to structured citation metadata via GET /dois/{id}. The response includes creators, titles, publication year, related identifiers, and funding references — everything needed to format a complete citation in APA, MLA, BibTeX, or CSL JSON. This avoids screen-scraping publisher pages and keeps citations consistent across tools.

Fetch metadata for DOI 10.5281/zenodo.7777777 and return creators, title, year, and resource type formatted as a CSL JSON record

PID Graph Analytics

Research analytics platforms pull DOI activity logs and citation events via /events and /activities to build dashboards showing dataset reuse, software citations, and inter-DOI relationships. The PID Graph exposes typed relationships (IsCitedBy, IsSupplementTo, IsPartOf) so analytics tools can construct citation networks across the global research output graph without scraping publisher sites.

Pull all IsCitedBy events for DOI 10.5281/zenodo.7777777 in the last 90 days and aggregate citing DOIs by publisher

AI Agent Research Assistant

AI agents use Jentic to call the DataCite REST API for research-task workflows: resolving DOIs cited in a draft paper, validating that a dataset DOI is still active before submission, or fetching authoritative metadata to populate a citation. Through Jentic, an agent searches by intent, loads the operation schema, and executes without managing DataCite Basic Auth credentials directly — Jentic isolates the credentials in its vault.

Given a list of 20 DOIs in a manuscript, resolve each via GET /dois/{id} and return a structured table of title, year, and resource type

Key Endpoints

13 endpoints — the datacite rest api lets researchers, repositories, and data providers register and manage digital object identifiers (dois) for research outputs.

METHOD

PATH

DESCRIPTION

POST

/dois

GET

/dois/{id}

Resolve a DOI to its citation metadata

PUT

/dois/{id}

Update metadata or URL on an existing DOI

GET

/clients

List repository clients in the DataCite consortium

GET

/providers

List DataCite member providers

GET

/events

Retrieve PID Graph citation and relationship events

GET

/activities

Audit log of metadata changes for DOIs

POST

/dois

GET

/dois/{id}

Resolve a DOI to its citation metadata

PUT

/dois/{id}

Update metadata or URL on an existing DOI

GET

/clients

List repository clients in the DataCite consortium

GET

/providers

List DataCite member providers

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

DataCite Basic Auth credentials (repository client username and password) are stored encrypted in the Jentic vault. Agents receive scoped session tokens — the raw password never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'register a research DOI' or 'fetch citation metadata') and Jentic returns matching DataCite operations with their input schemas, so the agent can call POST /dois or GET /dois/{id} without browsing DataCite documentation.

Time to first call

Direct DataCite integration: 1-3 days to handle Basic Auth, metadata XML/JSON serialisation, and error mapping. Through Jentic: under 30 minutes — search, load schema, execute.

FAQs

Specific to using DataCite REST API through Jentic.

What authentication does the DataCite REST API use?

The DataCite REST API uses HTTP Basic authentication with a repository client username and password issued by your DataCite member provider. Through Jentic, those credentials are stored encrypted in the MAXsystem vault and injected at call time, so agents never see the raw password.

Can I mint a new DOI with the DataCite REST API?

Yes. POST /dois accepts a DataCite metadata payload (creators, titles, publisher, resource type, and a target URL) and returns a registered DOI. Your client must have a prefix allocation from your provider before the call will succeed.

What are the rate limits for the DataCite REST API?

DataCite does not publish hard rate limits in the spec, but the production service throttles aggressive clients and asks high-volume integrators to coordinate via support. Cache GET /dois/{id} responses where possible and avoid tight loops over /events.

How do I resolve a DOI to citation metadata through Jentic?

Search Jentic for 'fetch citation metadata for a DOI', load the GET /dois/{id} operation, and execute it with the DOI as the id parameter. The response includes creators, titles, publication year, and related identifiers ready to format as BibTeX or CSL JSON.

Is the DataCite REST API free?

Read access to GET endpoints (DOIs, clients, providers, events) is free and public. Writing DOIs requires DataCite membership and a per-repository fee paid through a provider organisation — see datacite.org/membership.

Does the DataCite API expose citation graph events?

Yes. GET /events returns PID Graph events such as IsCitedBy, IsSupplementTo, and IsPartOf relationships between DOIs, which is how analytics tools build dataset citation dashboards.

DataCite REST API

Connect the DataCite REST API to your agent

Capabilities

Start building with DataCite REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs