/dblp/authors/search

POST /api/dblp/authors/search

Price: 1 credit

Find dblp authors by name. Each result carries the author id, the name dblp uses, earlier spellings of it and any affiliation or award dblp records for that person

How to use it

dblp splits people who share a name into separate profiles and distinguishes them by a four-digit suffix on the name and a trailing dash-digit on the id, so a common name returns several genuinely different people — use the `notes` affiliation to pick one rather than taking the first. Pass the `pid` to /dblp/authors for that person's bibliography.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• query string required — Author name to look for. The last word of each term is treated as a prefix, so `hint` also matches `hinton` (examples: "Geoffrey Hinton", "codd"; minLength: 1)
• count integer required — Number of authors to return (examples: 20; min: 1; max: 10000)

Response

• @type string (default: "DblpAuthorHit")
• name string required
• url string required
• pid string nullable
• aliases array (default: [])
• notes array (default: [])
  • @type string (default: "DblpNote")
  • type string required
  • text string required
  • label 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.