POST /api/zenn/scraps
Price: 5 credits
Get Zenn Scrap
Get a Zenn scrap - a running notebook thread - by slug or URL. Returns the title, topics, open/closed and archived state, the author profile, and the whole threaded discussion inline: every comment with its rendered body, plain text, author, like count and replies.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)scrap string required — Scrap slug or scrap URL (examples: "b2b3420a06eb53", "https://zenn.dev/catnose99/scraps/b2b3420a06eb53")@type string (default: "ZennScrap")id integer requiredalias string requiredscrap_title string nullableurl string nullablecreated_at integer nullablelast_comment_created_at integer nullableclosed_at integer nullableis_closed boolean (default: false)is_noindex boolean (default: false)can_others_post boolean (default: false)comment_count integer nullablepositive_comment_count integer nullablelike_count integer nullabletopics array (default: [])@type string (default: "ZennTopic")id integer requiredalias string requiredname string nullableimage string nullableurl string nullabletagging_count integer nullablecomments array (default: [])@type string (default: "ZennComment")id integer requiredalias string nullabletext string nullabletext_html string nullablecreated_at integer nullableupdated_at integer nullablelike_count integer nullableis_pinned boolean (default: false)hidden_reason string nullableuser object nullable@type string (default: "ZennUserRef")id integer requiredalias string requiredname string nullableimage string nullableurl string nullablechildren array (default: [])commented_users array (default: [])@type string (default: "ZennUserRef")id integer requiredalias string requiredname string nullableimage string nullableurl string nullableuser object nullable@type string (default: "ZennUserSummary")id integer requiredalias string requiredname string nullablebio string nullablebio_html string nullableimage string nullableurl string nullablegithub_url string nullabletwitter_url string nullablehatena_id string nullablewebsite_url string nullabletotal_liked_count integer nullableis_support_open boolean (default: false)analytics_id string nullableseller_name string nullableseller_contact string nullableawards array (default: [])@type string (default: "ZennAward")event_alias string requiredevent_title string nullableevent_type string nullableprize_name string nullableprize_rank string nullablearticle object nullable@type string (default: "ZennArticleRef")id integer requiredalias string requiredarticle_title string nullablearticle_type object nullable (see schema ZennArticleType)emoji string nullableurl string nullablepublished_at integer nullablebody_updated_at integer nullablesource_repo_updated_at integer nullablelike_count integer nullablecomment_count integer nullablebookmark_count integer nullableletter_count integer nullableis_pinned boolean (default: false)principal_type object nullable (see schema ZennPrincipalType)user object nullable (see schema ZennUserRef)publication object nullable (see schema ZennPublicationRef)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 — Scrap not found. Verify the scrap slug or URL. 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.