POST /api/dblp/authors
Price: 10 credits
Get one dblp author profile by author id: the name dblp uses, earlier spellings of it, ORCID, stated affiliations and awards, external profile links, the complete list of that author's records, and the coauthors dblp has recorded
This returns the author's whole bibliography in one call, so do not page through /dblp/publications/search by author to assemble it. dblp splits people who share a name, and `homonyms` lists the other profiles that share this one's name — check it before treating the bibliography as complete for a person, because works may sit under a namesake's id. An id ending in a dash and a digit is one of those split profiles, while `is_disambiguation_page` marks a placeholder that holds no bibliography of its own.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)pid string required — dblp author id, or the address of the author's dblp page (examples: "10/3248", "c/EFCodd", "https://dblp.org/pid/167/1261-9"; minLength: 1)@type string (default: "DblpAuthor")pid string requiredurl string requiredname string requiredaliases array (default: [])orcid string nullablekey string nullablemodified_date string nullableis_disambiguation_page boolean (default: false)notes array (default: [])@type string (default: "DblpNote")type string requiredtext string requiredlabel string nullableprofile_urls array (default: [])publication_count integer nullablecoauthor_count integer nullablecoauthors array (default: [])@type string (default: "DblpCoauthor")name string requiredpid string nullablealiases array (default: [])community integer nullablehomonyms array (default: [])@type string (default: "DblpHomonym")pid string nullablename string requiredurl string nullablekey string nullablemodified_date string nullableis_disambiguation_page boolean (default: false)notes array (default: [])@type string (default: "DblpNote")type string requiredtext string requiredlabel string nullableprofile_urls array (default: [])publications array (default: [])@type string (default: "DblpPublication")key string requiredurl string requiredrecord_type string requiredpublication_type string nullablemodified_date string nullableauthors array (default: [])@type string (default: "DblpAuthorRef")name string requiredpid string nullableorcid string nullableeditors array (default: [])@type string (default: "DblpAuthorRef")name string requiredpid string nullableorcid string nullableyear integer nullablemonth string nullablepages string nullablevolume string nullablenumber string nullablejournal string nullablebooktitle string nullableseries string nullableseries_url string nullablepublisher string nullableschool string nullableisbns array (default: [])notes array (default: [])@type string (default: "DblpNote")type string requiredtext string requiredlabel string nullablelinks array (default: [])@type string (default: "DblpLink")url string requiredtype string nullablelisting_url string nullablestream_id string nullablecrossref_key string nullablereference_keys array (default: [])archive_paths array (default: [])related_records array (default: [])@type string (default: "DblpRelatedRecord")type string nullablelabel string nullablekey string nullableurl string nullable422 — 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 author with this id 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.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-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.