/tumblr/blogs/posts

POST /api/tumblr/blogs/posts

Price: 10 credits

List a Tumblr blog's posts, optionally filtered by type or tag

How to use it

List a Tumblr blog's posts. Returns each post with its type, URL, creation time, tags, note count, title and body text, photos, quote/link/answer/conversation/video/audio fields, and reblog source. Optionally filter by post type (text, photo, quote, link, chat, video, audio) or by a single blog tag. Accepts a blog name, subdomain, or custom domain.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• blog string required — Blog name, subdomain, or custom domain (examples: "staff", "today.tumblr.com"; minLength: 1)
• count integer required — Max number of posts to return (min: 1)
• type string nullable — Filter posts by type (one of: "text", "photo", "quote", "link", "chat", "video", "audio")
• tag string nullable — Filter posts within the blog by a single tag
• post_format string — Return post bodies as raw HTML or as plain text (default: "html"; one of: "html", "text")

Response

• @type string (default: "TumblrPost")
• id string required
• blog_name string nullable
• type string required
• post_url string nullable
• created_at integer nullable
• format string nullable
• reblog_key string nullable
• alias string nullable
• note_count integer (default: 0)
• tags array (default: [])
• is_submission boolean (default: false)
• text string nullable
• images array (default: [])
• image_width integer nullable
• image_height integer nullable
• photo_link_url string nullable
• quote_text string nullable
• quote_source string nullable
• link_url string nullable
• link_text string nullable
• link_description string nullable
• question string nullable
• answer string nullable
• conversation_title string nullable
• conversation array (default: [])
  • @type string (default: "TumblrConversationLine")
  • name string nullable
  • label string nullable
  • phrase string nullable
• video_url string nullable
• video_embed string nullable
• audio_embed string nullable
• audio_plays integer nullable
• audio_title string nullable
• audio_artist string nullable
• reblogged_from_name string nullable
• reblogged_from_url string nullable
• reblogged_from_title string nullable
• reblogged_from_image string nullable
• reblogged_root_name string nullable
• reblogged_root_url string nullable
• reblogged_root_title string nullable
• reblogged_root_image 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 — Blog not found. Verify the blog name or domain. 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.