/pubpeer/publications/feed

POST /api/pubpeer/publications/feed

Price: 20 credits

List the publications PubPeer currently features as recently discussed, newest activity first, each with its title, abstract, journals, authors, comment count and the time of its latest comment

How to use it

Use this to see what PubPeer is discussing now, then feed an `id` to pubpeer/publications for the comment threads themselves — the feed carries counts, not comment text. It is a curated stream, not an index of the site: it reaches 440 publications and there is no way to search or to look a paper up by DOI here, so it cannot answer whether a given paper has comments.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of publications to return (min: 1; max: 440)

Response

• @type string (default: "PubpeerFeedPublication")
• id string required
• url string nullable
• abstract string nullable
• published_year integer nullable
• comment_count integer nullable
• has_author_response boolean nullable
• journal_has_team boolean nullable
• created_at integer nullable
• updated_at integer nullable
• last_commented_at integer nullable
• authors array (default: [])
  • @type string (default: "PubpeerAuthor")
  • id string required
  • display_name string nullable
  • first_name string nullable
  • last_name string nullable
  • email string nullable
  • orcid string nullable
  • affiliations array (default: [])
• journals array (default: [])
  • @type string (default: "PubpeerPublicationJournal")
  • id string required
  • issn 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 — 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.