/ameblo/posts

POST /api/ameblo/posts

Price: 1 credit

Get a single Ameba blog entry by blog ID and entry ID

How to use it

Get a single Ameba blog (ameblo.jp) entry by its owning blog ID and numeric entry ID (or full entry URL). Returns the entry title, HTML body, description, theme, cover and inline images, hashtags, PR and reblog flags, like/comment/reblog counts, entry URL, and creation and update timestamps.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• user string required — Ameba blog ID (URL slug) or blog URL that owns the post (examples: "tsuji-nozomi", "https://ameblo.jp/tsuji-nozomi/"; minLength: 1)
• post string required — Numeric entry ID or full entry URL (examples: "12970909880", "https://ameblo.jp/tsuji-nozomi/entry-12970909880.html")

Response

• @type string (default: "AmebloPost")
• id integer required
• blog_id integer nullable
• user_id integer nullable
• alias string nullable
• post_title string nullable
• text string nullable
• description string nullable
• theme_id integer nullable
• theme_name string nullable
• image string nullable
• images array (default: [])
• hashtags array (default: [])
• is_pr boolean (default: false)
• is_reblog boolean (default: false)
• like_count integer (default: 0)
• comment_count integer (default: 0)
• reblog_count integer (default: 0)
• post_url string nullable
• created_at integer nullable
• updated_at 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 — Entry not found 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.