EasyDown media API response inspector

A successful API response can contain an empty array, omit a media field, or return a field with an unexpected type. Those cases should not collapse into the same “zero files” message in a developer dashboard.

This Actor turns a batch of sanitized media API response fixtures into a small, consistent report. It checks the JSON API-envelope status before inspecting images, videos and audios. It preserves the difference between missing, null, empty, present and unexpected_type. It is a response-inspection utility, not a scraper or downloader.

What you can use it for

Use it to compare captured, sanitized API responses before implementing an importer, check a frontend's empty-state logic, or review response-shape changes in a test dataset. It does not fetch social posts, follow media URLs, or use an EasyDown API key.

Input

Pass a responses array containing 1–100 JSON response fixtures. For example:

{
  "responses": [
    {
      "status": 200,
      "data": {
        "platform": "tiktok",
        "images": [],
        "videos": [{ "quality": "synthetic" }],
        "audios": null
      }
    },
    { "status": 401 }
  ]
}

Use synthetic or sanitized input. Do not submit API credentials, signed media URLs, private response headers, personal information or private-content data to a public example. The Actor needs none of those fields. Apify stores the run input under your account's storage and retention settings.

Output

Each input response produces one dataset row in the same order. response_index is zero-based. result is one of inspected, api_error, invalid_response, invalid_api_status or invalid_data. Each media group has a _state and _count column. Counts are available only for arrays; otherwise they are null.

For the synthetic first response, images are empty with count 0, videos are present with count 1, and audios are null with a null count. The second response is classified as api_error; its media fields remain not_checked rather than being interpreted as successful empty results.

The default dataset can be exported through Apify's normal JSON or CSV controls. A SUMMARY record in the default key-value store reports the response count, inspected count and error-or-shape-problem count. Original input objects and media URLs are not copied into the output.

Scope and limits

The status field is a JSON API-envelope field, not the actual HTTP transport status. Your integration must check HTTP status separately. This utility expects numeric 200 for a successful envelope and an object in data; it does not turn a string status into a number. It counts array entries without validating individual files, URLs, availability, permissions or download safety. A non-empty array does not guarantee downloadable media. An omitted field does not prove that the post has no media.

The inspection logic makes no requests to EasyDown, social platforms or media hosts. It performs no automatic retries and does not trigger EasyDown API billing. The Actor only reads its current input and writes the inspection result to the current run's default Apify storage. Apify platform compute and storage usage remain subject to the runner's plan and available allowance.

EasyDown API context

I build EasyDown. For supported fields and platform endpoints, see the EasyDown API reference. The developer API is paid and uses an account, a Bearer token and credits; new accounts receive 10 trial credits. The separate browser downloader is free. Integrations should use supported public single-post URLs; this utility does not enable private-content access or profile crawling.

This original developer utility and its documentation were drafted with AI assistance. The offline classifier was checked against synthetic fixtures; no claim of live API integration testing is made.