/dblp/publications/search

POST /api/dblp/publications/search

Price: 5 credits

Search dblp publications by free text and by type, open-access state, year, venue, venue stream and author. Each result carries the dblp key, title, authors with their dblp author ids, venue, year, volume, issue, pages, DOI and the link dblp records for the full text

How to use it

dblp indexes computer science only, so a paper outside that field will not be here however it is spelled. Words are prefix-matched, which quietly widens a query: append `$` to a word to stop that. `author` and `venue` must be dblp's own spelling — take them from an earlier result or from /dblp/authors/search rather than guessing, since a name dblp does not use returns an empty result instead of an error. Feed a result's `key` to /dblp/publications for the full record.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string nullable — Free-text words matched against title, author and venue. The last word of each term is treated as a prefix, so `transform` also matches `transformer`; end a word with `$` to match it whole, and separate alternatives with `|` for OR (examples: "attention is all you need", "quantum|photonic"; minLength: 1)
• publication_type string nullable — Restrict to one publication type, spelled as the `type` field of a result (one of: "Conference and Workshop Papers", "Journal Articles", "Parts in Books or Collections", "Books and Theses", "Editorship", "Reference Works", "Data and Artifacts", "Informal and Other Publications", "Withdrawn Items")
• access string nullable — Restrict by how the full text can be reached: `open` for a freely readable version, `closed` for one behind a publisher, `unavailable` when dblp knows of no version (one of: "open", "closed", "unavailable")
• year integer nullable — Restrict to one publication year (examples: 2020; min: 1900)
• venue string nullable — Restrict to a venue by its short name as it appears in a result's `venues` (examples: "NeurIPS", "Commun. ACM"; minLength: 1)
• stream_id string nullable — Restrict to one venue stream, the identifier /dblp/venues/search returns as `stream_id` (examples: "conf/nips", "journals/cacm"; minLength: 1)
• author string nullable — Restrict to one author, written exactly as dblp spells that author's name, including the four-digit suffix dblp adds to distinguish namesakes (examples: "Geoffrey E. Hinton", "Xiaopeng Zhang 0009"; minLength: 1)
• count integer required — Number of publications to return (examples: 50; min: 1; max: 10000)

Response

• @type string (default: "DblpPublicationHit")
• key string required
• url string required
• type string nullable
• access string nullable
• year integer nullable
• venues array (default: [])
• volume string nullable
• number string nullable
• pages string nullable
• publisher string nullable
• doi string nullable
• electronic_edition_url string nullable
• authors array (default: [])
  • @type string (default: "DblpAuthorRef")
  • name string required
  • pid string nullable
  • orcid string nullable
• score integer 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 — The entity was not found, or a precondition failed 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.