Creator post collection API

Read a tracked creator's collected posts and request an additional collection when a wider history is needed.

What to build with it

  1. Start with the posts already collected for the tracked creator.
  2. Request additional collection only if the existing window is insufficient.
  3. Poll the returned collection ID and merge posts by stable platform ID.

Provider reference: Virlo documentation. Authentication uses a provider-issued Bearer token, stored on your server.

Endpoints and inputs

4 documented operations. Query and path fields are listed separately from JSON request-body fields.

Before you integrate

  • Historical depth can vary, and collection can be separately billed. A post missing from a collection is not proof that it never existed.

Check the provider's current price, allowed use and retention terms before sending requests. An optional field can be absent; the schema alone does not establish its completeness or accuracy.

Give this task to your coding agent

creator-posts-api agent prompt
Help me implement creator post collection api using the documented Virlo API.

Reference: https://allthemapis.com/social-media-apis/creator-posts-api
Provider documentation: https://dev.virlo.ai/docs/tracking
Base URL: https://api.virlo.ai
Starting operation: GET /v1/tracking/creators/{id}/posts

Read the current provider docs and confirm the required inputs before writing code. Load VIRLO_API_KEY from a server-side environment variable and use Bearer authentication. Do not put the key in client code, logs, analytics, or the chat.

Ask me for any missing video URL, creator handle, research intent, or job ID. Do not invent a result. Ask for approval before starting billable lookups, recurring jobs, or destructive changes. For jobs, keep the returned ID and poll with the documented delay instead of starting the job twice. Handle pagination, rate limits, partial results, and missing fields explicitly.

Build the smallest integration for this task:
1. Start with the posts already collected for the tracked creator.
2. Request additional collection only if the existing window is insufficient.
3. Poll the returned collection ID and merge posts by stable platform ID.

Return the code, the environment variables I need, and a short explanation of what was actually retrieved versus inferred. Do not execute paid requests until I approve.

Sources and review dates

Virlo's public documentation and OpenAPI schema reviewed October 27, 2026. Endpoint paths and field names below refer to that provider's API. This is an integration reference, not a measured performance ranking.

Corrections: email faizank@docsalot.dev with an official source.