Account

GET /v1/account/request-history

Request History API

Bulk-list Account content with full metadata for each item.

TL;DR

The Request History API (Account) returns bulk-list Account content with full metadata for each item. It's a single authenticated GET request to /v1/account/request-history that responds with clean JSON, costs 0 credits, and is cached for 24 hours (repeat calls are free). Start with 100 free credits — no credit card.

What is the Request History API?

The Request History API lets you list items in bulk with metadata from Account with a single REST call. No OAuth, no scraping infrastructure, and no platform SDKs — send the URL, get clean structured JSON back. Results are cached for 24 hours, so repeat lookups are instant and free.

What you get

Bulk list of items with full metadata
View counts, dates, and direct URLs
Configurable result limit
Ideal for monitoring and content pipelines

Try it

Fill in the parameters below and copy a ready-to-run request in your language of choice.

Parameters

limitoptionalintegerMax items to return (default 50, max 500). Billed per result.

API keyoptionalPaste your key to get a ready-to-run snippet. It stays in your browser.

curl "https://api.captapi.com/v1/account/request-history?limit=20" \
  -H "Authorization: Bearer capt_live_..."

Edit the parameters and the code updates instantly. Switch languages and hit copy.

Example response

{
  "success": true,
  "cached": false,
  "creditsUsed": 0,
  "data": {
    "total": 2,
    "items": [
      {
        "title": "Latest upload",
        "url": "https://example.com/a",
        "views": 90120,
        "publishedAt": "2025-01-12"
      },
      {
        "title": "Previous upload",
        "url": "https://example.com/b",
        "views": 75230,
        "publishedAt": "2025-01-04"
      }
    ]
  }
}

Response structure

A successful call returns success, cached, creditsUsed, and a data object with the following fields:

Result

totalNumber of items returned.

Each item

Each item in items contains:

titleItem title.
urlDirect URL to the content.
viewsView count.
publishedAtPublish date (ISO 8601).

Parameters

Name	Type	Required	Description
limit	integer	No	Max items to return (default 50, max 500). Billed per result.

Authentication: send your key as Authorization: Bearer capt_live_.... A typical call costs 0 credits. Repeat calls for the same request are served from cache for free.

Using an AI agent? This endpoint is the MCP tool account_request_history via @captapi/mcp. Set it up →

How it works

1. Sign up — get 100 free credits, no card required.
2. Create a key from your dashboard.
3. Send one request to /v1/account/request-history and parse the JSON response.

Use cases

Content Pipelines

Ingest a channel's catalog in bulk.

Monitoring

Detect new uploads automatically.

Archiving

Snapshot a creator's full library.

Analytics

Aggregate performance across many videos.

Frequently asked questions

What does the Request History API do?+

The Request History API lets you list items in bulk with metadata from a public Account video using one GET request to /v1/account/request-history. It returns clean JSON — no OAuth or scraping setup required.

How many credits does the Request History API cost?+

Each successful call costs 0 credits. Responses are cached for 24 hours, and cached results cost 0 credits. Failed or empty results are never charged.

Do I need a Account API key or OAuth?+

No. A single Captapi key works across every platform Captapi supports — YouTube, TikTok, Instagram, Facebook, Twitter/X, Reddit, Threads, Bluesky, Pinterest, LinkedIn, and Rumble. We handle proxies, rate limits, retries, and authentication for you.

Is the Request History API suitable for production use?+

Yes. It is a stable REST endpoint with predictable JSON, automatic retries, and a shared 24-hour cache. Use it for RAG pipelines, analytics, monitoring, and content automation.

More Account APIs

Credit Balance API Daily Usage API Most Used Routes API

Ready to use the Request History API?

Get started free