Ameba Post Scraper

Ameba Post Scraper — Export public Ameba post details with article text, HTML, media, themes, tags, and like, comment, and reblog counts. Add supported inputs and start a run to get structured public data without providing a Ameba account.

Export a public Ameba staff announcement with article text, images, source links and visible reaction counts in one record for editorial reference.

At a glance	Details
📥 Input	Enter full public post URLs such as https://ameblo.jp/staff/entry-12590320297.html.
📤 Output	One post per success row, with source input retained
📄 Pagination	One lookup per unique input; nested values stay in that result row.
🔐 Login required	No
⚡ Processing	Up to 5 HTTP requests concurrently with automatic retries
💾 Delivery	One Apify dataset view, useful flat columns and complete nested JSON

What the ameba post scraper collects 📊

Export public Ameba post details with article text, HTML, media, themes, tags, and like, comment, and reblog counts.

Data can include:

• Source identity and public links
• Available id, url, ameba id, blog id, title, text, html, published at
• Original input retained with every result
• One consistent success or failed record format

How to collect posts from Ameba 🚀

1. Enter one or more supported inputs in inputList.
2. Review the supported input format.
3. Start the Actor.
4. Open the Posts dataset view and review the individual records.
5. Export the dataset or retrieve it from your application.

{
  "inputList": [
    "https://ameblo.jp/staff/entry-12590320297.html"
  ]
}

One lookup per unique input; nested values stay in that result row.

Ameba posts data and complete output 📦

Field	Type	Meaning
input	string	Original submitted input.
status	string	Result status: success or failed.
id	string or null	Stable identifier of this result.
url	string or null	Public result URL.
ameba_id	string or null	Ameba blog ID / username.
blog_id	string or null	Numeric Ameba blog ID.
title	string or null	Public blog or post title.
text	string or null	Available article or comment text with markup removed.
html	string or null	Available article or comment HTML.
published_at	string or null	Publication timestamp.
updated_at	string or null	Last update timestamp when provided.
theme_id	string or null	Ameba theme/category ID.
theme_name	string or null	Public theme/category name.
thumbnail_url	string or null	Article preview image URL.
tags	array or null	Public tags.
images	array or null	Article image URLs with available alt text and dimensions.
images[].url	string or null	Public source URL.
images[].alt	string or null	Alt when exposed by the public response.
images[].width	integer or null	Image width in pixels when supplied.
images[].height	integer or null	Image height in pixels when supplied.
embed_urls	array or null	Video, audio, or iframe URLs found in the public article HTML.
is_reblog	boolean or null	Whether the source labels the post as a reblog.
source_blog_id	string or null	Numeric source blog ID.
source_post_id	string or null	ID of the source article.
is_member_only	boolean or null	Whether this public list record refers to an approved-members-only article.
likes_count	integer or null	Public like count.
comments_count	integer or null	Public comment count including replies.
reblogs_count	integer or null	Public reblog count.

Nested arrays and media references stay in their parent record. Downloading source media files is not part of this Actor.

Every top-level output field appears in these complete examples. The success example is normalized from a public response. Long strings and arrays are shortened here; the Actor keeps the complete available values. Values are a snapshot and can change. Nested arrays remain inside their parent result.

Representative success result with every output field (long text and arrays shortened for readability):

{
  "input": "https://ameblo.jp/staff/entry-12590320297.html",
  "status": "success",
  "id": "12590320297",
  "url": "https://ameblo.jp/staff/entry-12590320297.html",
  "ameba_id": "staff",
  "blog_id": "10000276667",
  "title": "【改善のお知らせ】コメントで絵文字が使えるようになりました",
  "text": "いつもAmebaをご利用いただきましてありがとうございます。\n\nAmebaプロダクトマネージャーの田熊です。\n\n皆さまより多数ご要望いただいておりましたコメントでの絵文字利用について、\n\nAmebaアプリ、スマートフォンブラウザ、パソコンにてご利用いただけるよう改善いたしました。\n\nこれからは、絵文字でも気持ちを伝えることが可能になりますので、ぜひたくさんご利用ください。\n\n■絵文字の利用方法\n\nご利用の端末に搭載されている標準の絵文字が利用できます。\n\n※Amebaオリジナル絵文字はご利用いただけません\n\nスマートフォン：スマートフォン内キーボー...",
  "html": "<p><a href=\"https://stat.ameba.jp/user_images/20200417/16/staff/fc/e7/p/o1200060014744950765.png\"><img alt=\"コメントで絵文字が使えるようになりました\" contenteditable=\"inherit\" height=\"600\" src=\"https://stat.ameba.jp/user_images/20200417/16/staff/fc/e7/p/o1200060014744950765.png?caw=800\" width=\"12...",
  "published_at": "2020-04-17T17:00:00.000+09:00",
  "updated_at": "2021-09-22T02:21:57.000+09:00",
  "theme_id": "10000022341",
  "theme_name": "改良・改善",
  "thumbnail_url": "https://stat.ameba.jp/user_images/20200417/16/staff/fc/e7/p/o1200060014744950765.png",
  "tags": [],
  "images": [
    {
      "url": "https://stat.ameba.jp/user_images/20200417/16/staff/fc/e7/p/o1200060014744950765.png?caw=800",
      "alt": "コメントで絵文字が使えるようになりました",
      "width": 1200,
      "height": 600
    },
    {
      "url": "https://stat.ameba.jp/user_images/20200417/16/staff/fb/58/p/o1600120014744952033.png?caw=800",
      "alt": "コメントで絵文字が使えるようになりました",
      "width": 620,
      "height": 465
    }
  ],
  "embed_urls": [],
  "is_reblog": false,
  "source_blog_id": null,
  "source_post_id": null,
  "is_member_only": false,
  "likes_count": 2211,
  "comments_count": 165,
  "reblogs_count": 52
}

Complete failed result:

{
  "input": "invalid input",
  "status": "failed",
  "id": null,
  "url": null,
  "ameba_id": null,
  "blog_id": null,
  "title": null,
  "text": null,
  "html": null,
  "published_at": null,
  "updated_at": null,
  "theme_id": null,
  "theme_name": null,
  "thumbnail_url": null,
  "tags": null,
  "images": null,
  "embed_urls": null,
  "is_reblog": null,
  "source_blog_id": null,
  "source_post_id": null,
  "is_member_only": null,
  "likes_count": null,
  "comments_count": null,
  "reblogs_count": null
}

A failed row preserves input, sets status to failed, and sets every other top-level field to null. The run log records the reason. Optional successful fields can be null or empty when Ameba does not supply them. Object fields are exposed through useful columns in the single Posts view; arrays are not expanded into extra result rows.

Input requirements and pagination settings ⚙️

Parameter	Type	Required	Default	Rules
inputList	array of strings	Yes	None	Enter full public post URLs such as https://ameblo.jp/staff/entry-12590320297.html. At least 1 item.

Enter full public post URLs such as https://ameblo.jp/staff/entry-12590320297.html.

Examples of supported inputs: https://ameblo.jp/staff/entry-12590320297.html.

Duplicate normalized inputs are processed once. Within the collection for one source input, repeated records are removed while distinct interactions or objects remain separate. The same object returned for different source inputs retains its source relationship.

There is no result-page setting. Each unique target is looked up individually, and nested fields remain within that result row.

Ameba posts use cases 🎯

Extract an Ameba service announcement

Export a public Ameba staff announcement with article text, images, source links and visible reaction counts in one record for editorial reference.

Review engagement on an Ameba creator article

Collect an Ameba creator article with its public text and visible like, comment and reblog totals. The counts describe the time of the request.

Audit media links in selected Ameba articles

Export selected public Ameba articles with text, image references and embedded links. Review the media inventory in your export without downloading files.

Pricing and saved-result behavior 💰

Check the Actor’s Pricing tab for the active pricing model and current rate. Store settings can change, so this README does not claim a fixed price or runtime.

Under dataset-item pricing:

• Each successful result represents one post for its source input.
• An invalid or unavailable input, an input with no accessible results, or an exhausted request can produce a failed row.
• Retry attempts and supporting requests do not create extra dataset rows by themselves.
• Nested media, profile information and other arrays remain part of their parent row.
• A normal empty continuation after earlier successes creates no additional row.
• Saved failed rows are not assumed to be free; check their treatment in the active pricing configuration.

More inputs can produce more saved rows. Start with a small run and check actual usage before increasing the workload.

Ameba posts API 🔌

Replace $ACTOR_ID with the identifier shown in this Actor’s API tab and $APIFY_TOKEN with your Apify token.

curl -X POST "https://api.apify.com/v2/acts/$ACTOR_ID/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"inputList":["https://ameblo.jp/staff/entry-12590320297.html"]}'

Download the dataset in JSON, CSV, Excel or other formats available in the Console, or retrieve it through the Apify API. Use schedules, webhooks and Apify integrations to connect results to Google Sheets, Make, Zapier, cloud storage or your own application. These connections are configured separately by the user.

Reliability, retries, and public-data limits ⚠️

Collection uses pure HTTP with up to five concurrent requests. Invalid syntax and confirmed missing, removed or unavailable targets stop without unnecessary retries. Temporary network or proxy failures, timeouts, blocking responses, malformed data, throttling and server errors allow up to five total attempts per request.

Successful earlier pages remain saved if a later request fails. A normal end after saved results is not retried. An input with no accessible results can receive a failed row; that alone does not prove that its underlying source does not exist. An exhausted later request can add a failed row while preserving previous output.

Member-only and unavailable posts are skipped. Count values reflect the time of the request. Media links are exported without downloading the files.

Ameba controls public availability, ranking and optional fields. Result counts can be affected by duplicates, removed content and changes during a run. A page budget is a collection limit, not a promise of exhaustive coverage.

An invalid string within a valid input list does not stop other inputs. Invalid overall configuration, such as a non-string list item or a wrong page-count type, exits before source requests. Startup failures, unavailable dataset storage or an unrecoverable result-save error can still stop the whole run. A failed save is not retried as a new scraping request.

Frequently asked questions ❓

What does one Ameba Post Scraper result represent?

Each successful row represents one post. The source input is retained, and nested fields stay in the same row.

Which source limits apply?

Member-only and unavailable posts are skipped. Count values reflect the time of the request. Media links are exported without downloading the files.

Does it download media files?

No. Where available, the Actor returns media URLs and metadata within the result row.

Does it require a Ameba account or personal cookies?

No. You do not need to provide a Ameba account, password or personal session cookie. Collection uses HTTP without opening a browser.

What happens to invalid or unavailable inputs?

Invalid individual inputs are recorded as failed without a source request. Confirmed missing or unavailable targets stop without unnecessary retries. Temporary failures allow up to five total attempts per request; other inputs and earlier saved results remain available.

Can I export results or run the same input again?

Yes. Export the default dataset or retrieve it through the Apify API. You can create an Apify schedule and connect completed runs to your own workflow.

Support, responsible use, and related actors 🛟

For a reproducible issue, use the Actor’s Issues tab and provide the run ID, approximate time, a safe public input, expected behavior and actual result. Include the mode or page budget when relevant. Never share access tokens, personal cookies or proxy credentials.

Use public data responsibly and follow applicable privacy, copyright, contractual and platform requirements before storing, analyzing or redistributing collected information.