/naver/cafe/posts

POST /api/naver/cafe/posts

Price: 10 credits

Get one public Naver Cafe post: title, full text, images, attachments, board, author and level, view and comment counts, cafe, and for second-hand listings the product with price, condition, delivery and regions

How to use it

Posts of member-only boards are not readable without membership and answer 412. For the comments use naver/cafe/posts/comments.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• post string required — Naver Cafe post URL or cafeId/articleId pair (examples: "https://cafe.naver.com/f-e/cafes/14358379/articles/3404863", "https://cafe.naver.com/campingfirst/3404863", "14358379/3404863"; minLength: 1)

Response

• @type string (default: "NaverCafePost")
• id string required
• cafe_id string required
• article_id string required
• url string required
• text string nullable
• images array (default: [])
• attachments array (default: [])
  • @type string (default: "NaverCafePostAttachment")
  • kind string nullable
  • name string nullable
  • url string nullable
  • size integer nullable
• tags array (default: [])
• menu_id string nullable
• menu_name string nullable
• head string nullable
• author string nullable
• author_level string nullable
• author_image string nullable
• view_count integer nullable
• comment_count integer nullable
• repost_count integer nullable
• scrap_count integer nullable
• is_notice boolean nullable
• is_trade boolean nullable
• product object nullable
  • @type string (default: "NaverCafePostProduct")
  • id string nullable
  • url string nullable
  • name string nullable
  • description string nullable
  • brand string nullable
  • price integer nullable
  • currency string nullable
  • condition string nullable
  • sale_status string nullable
  • payment_type string nullable
  • categories array (default: [])
  • images array (default: [])
  • deliveries array (default: [])
    • @type string (default: "NaverCafePostDelivery")
    • method string nullable
    • fee integer nullable
    • remote_area_fee integer nullable
    • fee_payer string nullable
  • regions array (default: [])
    • @type string (default: "NaverCafeTradeRegion")
    • code string nullable
    • name string nullable
  • keep_count integer nullable
  • accepts_offers boolean nullable
  • created_at integer nullable
  • updated_at integer nullable
• cafe_name string nullable
• cafe_alias string nullable
• cafe_image string nullable
• cafe_member_count integer nullable
• created_at integer nullable

Errors

• 422 — post is not a Naver Cafe post URL or cafeId/articleId pair 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 such Naver Cafe post, it was deleted, or it is visible to cafe members only 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.