Tumblr Search API

AI prompt

Paste this into your AI assistant. It already holds this endpoint's parameters, response fields and an example request, so the assistant can ask what you need and then write the scraper.

Please help me write a data collection script with the EveryInfra Tumblr Search endpoint (tumblr/search).

Endpoint contract:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to tumblr and action to search, and put the parameters inside params.
- Required parameters:
  - keyword: Public post search term for search. The compatibility keyword input for tag actually queries by tag and cannot be treated as an identical search entry point.
- Optional parameters:
  - post_type: Single post type for search, tag, or user_posts: any for unrestricted, text, photo, video, quote, link, or audio. This is not an array, and profile does not use this filter.
  - limit: The most rows to return in this call, an integer from 1 to 200. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: id, url, text, post_type, author_username, author_name, author_url, note_count, posted_at, tags.
- Example request body:
{
  "platform": "tumblr",
  "action": "search",
  "params": {
    "keyword": "film photography"
  }
}
- Price: $1.39 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.

Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.

Request parameters

Code samples

curl -X POST 'https://api.everyinfra.com/api/v1/social' \
  -H "Authorization: Bearer $EVERYINFRA_API_KEY" \
  -H 'Content-Type: application/json' \
  --data-raw '{
  "platform": "tumblr",
  "action": "search",
  "params": {
    "keyword": "film photography"
  }
}'

[OpenAPI definition (JSON)]Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.

Response example

{
  "id": "req_…",
  "platform": "tumblr",
  "action": "search",
  "results": [
    {
      "id": "（已隐去）",
      "url": "https://www.tumblr.com/blog/view/heyscola/828814013050798080",
      "text": "Hudson Yards, 2026",
      "post_type": "text",
      "author_username": "（已隐去）",
      "author_name": "（已隐去）",
      "author_url": "https://www.tumblr.com/（已隐去）",
      "note_count": 0,
      "posted_at": "2026-09-26T10:30:37+00:00",
      "platform": "tumblr",
      "tags": [
        "black and white",
        "manhattan",
        "35mm"
      ]
    },
    {
      "id": "（已隐去）",
      "url": "https://capturedbykat.tumblr.com/post/828810369369882624/above-the-rio-grande-ii-orilla-verde",
      "text": "// Above the Rio Grande II // Orilla Verde Recreation Area, NM Olympus Infinity Stylus, Seattle Film Works expired film, August 2026",
      "post_type": "text",
      "author_username": "（已隐去）",
      "author_name": "（已隐去）",
      "author_url": "https://capturedbykat.tumblr.com/（已隐去）",
      "note_count": 0,
      "posted_at": "2026-09-26T09:32:42+00:00",
      "platform": "tumblr",
      "tags": [
        "rio grande",
        "orilla verde",
        "film photography"
      ]
    }
  ],
  "count": 20,
  "billing": {
    "charged": …,
    "charged_usd": …,
    "balance_after_usd": …,
    …
  },
  "quota": { … }
}

Response fields

Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.

FAQ

Errors and billing

401

Missing or invalid key. Authentication runs before parameter checks, so unauthenticated requests never see the parameter schema.

422

Wrong parameter name or value. The error lists the parameters and allowed values this capability accepts and the closest match; it happens before any charge.

402

Insufficient balance. Top up first.

429

The account's per-minute request limit was reached (all of its API keys count together; a key's own lower limit applies first). Wait for Retry-After and try again; a rate package in the console raises the limit.

503

Could not complete right now. Any charge for the call goes back to your balance automatically, and the billing receipt in the response states the actual outcome, including when it is not yet known. Do not resend blindly.

200 empty

The request completed without data and is not charged (billing.reason = empty_result_refunded).

Official references

Used only to check objects and terms. They do not imply authorization or endorsement of EveryInfra by the platform.

• Tumblr: Differences Between Keyword Search and Tag Pages ↗

  Official documentation separates search pages from tag pages: search pages discover content by words, whereas tag pages aggregate posts containing a specific tag. Blog recommendations, sorting options, and search operators on Tumblr web pages are not automatically supported or verified parameters for this endpoint.

  Checked 2026-09-04

• Tumblr: Notes Across Post Types Are Not Separate Like Counts ↗

  Official Tumblr documentation defines notes as the combined likes, reblogs, and comments received by a post. Changing the post type does not automatically split note_count into three separate metrics in this endpoint, nor can the total interaction count be interpreted as unique user counts.

  Checked 2026-09-04