/dblp/publications

POST /api/dblp/publications

Price: 1 credit

Get one dblp record by its key: title, authors and editors with their dblp author ids and ORCIDs, journal or proceedings, series, publisher, year, volume, issue, pages, ISBNs, the full-text links dblp records, the key of the parent proceedings and the identifiers of related versions

How to use it

`record_type` tells a journal article from a conference paper, a book, a thesis, an artifact and an encyclopedia entry, and `publication_type` marks the records dblp treats as provisional — `informal` for preprints, `withdrawn` for retracted work — so do not read a preprint as a published paper. `crossref_key` is the key of the proceedings volume a conference paper appeared in and resolves through this same endpoint. `reference_keys` is filled only for the handful of old records dblp has reference data for, so an empty one means unrecorded rather than uncited.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• key string required — dblp key of the record, or the address of its dblp page (examples: "conf/nips/VaswaniSPUJGKP17", "journals/cacm/Codd70", "https://dblp.org/rec/journals/cacm/Codd70.html"; minLength: 1)

Response

• @type string (default: "DblpPublication")
• key string required
• url string required
• record_type string required
• publication_type string nullable
• modified_date string nullable
• authors array (default: [])
  • @type string (default: "DblpAuthorRef")
  • name string required
  • pid string nullable
  • orcid string nullable
• editors array (default: [])
  • @type string (default: "DblpAuthorRef")
  • name string required
  • pid string nullable
  • orcid string nullable
• year integer nullable
• month string nullable
• pages string nullable
• volume string nullable
• number string nullable
• journal string nullable
• booktitle string nullable
• series string nullable
• series_url string nullable
• publisher string nullable
• school string nullable
• isbns array (default: [])
• notes array (default: [])
  • @type string (default: "DblpNote")
  • type string required
  • text string required
  • label string nullable
• links array (default: [])
  • @type string (default: "DblpLink")
  • url string required
  • type string nullable
• listing_url string nullable
• stream_id string nullable
• crossref_key string nullable
• reference_keys array (default: [])
• archive_paths array (default: [])
• related_records array (default: [])
  • @type string (default: "DblpRelatedRecord")
  • type string nullable
  • label string nullable
  • key string nullable
  • url string nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — No dblp record with this key Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.