Skip to content
All APIs

Crossref · Education · 1 endpoint

DOI Lookup

One DOI resolved to its work through Crossref — title, journal, publisher, authors, and the citation counts the registry computes.

Status
Operational
Price
1 credit / request
Rate limit
120 / 60s
Cache
1d
Requests
0

Endpoint

How to call it

GET/v1/papers/doi

Code

Request — cURL

v1

curl https://api.diraz.co.id/v1/papers/doi \
  -H "Authorization: Bearer drz_live_…"

For AI agents

Callable through the MCP server with the same key:

call_api {"endpoint":"doi-lookup","params":{"doi":"10.1038/nature12373","max_age":"60"}}

Parameters

doistring · required
The DOI to resolve. It rides in the query string — DOIs contain slashes.
max_ageinteger (seconds) · optional
Ask for data no older than this. Clamped to the product's own floor, so it can narrow the window but never force a refresh on every call.Default: 300

Example response

200 OK

JSON

{
  "data": {
    "doi": "10.1038/nature12373",
    "title": "Nanometre-scale thermometry in a living cell",
    "container": "Nature",
    "publisher": "Springer Science and Business Media LLC",
    "type": "journal-article",
    "authors": [
      { "given": "G.", "family": "Kucsko" },
      { "given": "P. C.", "family": "Maurer" },
      { "given": "N. Y.", "family": "Yao" }
    ],
    "issued": "2013-07-31",
    "url": "https://doi.org/10.1038/nature12373",
    "reference_count": 30,
    "cited_by_count": 1805
  },
  "meta": {
    "request_id": "req_7Q2fK4mZ",
    "as_of": "2026-08-20T04:05:00.000Z",
    "age_seconds": 42,
    "next_update_at": "2026-08-21T04:05:00.000Z"
  }
}
doi / type / publisher
The identifier, the work's Crossref type, and who published it.
title / container
The work's title and the journal or series it appeared in.
authors[]
Given and family names, in byline order.
issued / url
The publication date Crossref holds, and the DOI's resolver URL.
reference_count / cited_by_count
How many references it lists, and how many works cite it.

Errors

When something goes wrong

Every failure carries a stable machine-readable code and the same meta.request_id a success carries — quote it and we can find your request. Errors are never billed.

401 Unauthorized

JSON

{
  "error": {
    "code": "UNAUTHORIZED",
    "message": "The API key is invalid, expired, or revoked."
  },
  "meta": {
    "request_id": "req_7Q2fK4mZ"
  }
}
UNAUTHORIZEDHTTP 401
Missing, malformed, expired, or revoked API key.
FORBIDDENHTTP 403
The key is valid but lacks the scope this product needs.
VALIDATION_ERRORHTTP 422
A query parameter is the wrong type or out of range.
RATE_LIMITEDHTTP 429
Rate limit exhausted. `Retry-After` says how long to wait.
SERVICE_UNAVAILABLEHTTP 503
No data recent enough to serve. Carries `Retry-After`, and is never billed.

Data freshness

Every response is timestamped

as_of is when the data was published, age_seconds how old it is now, and next_update_at when newer data is expected.

  • Up to date

    200

    Inside its published window. Almost every request.

  • Delayed

    delayed: true

    Newer data is late; you get the latest there is, flagged.

  • Unavailable

    503

    Nothing recent enough. Carries Retry-After, never billed.

Health

Is it up?

  • DOI Lookup

1/1 passing