Most Used Routes API
Ranked list of which Captapi routes your key calls most (0 credits).
GET request to /v1/account/most-used-routes that responds with clean JSON and costs 0 credits. Account endpoints are always live (never cached). Start with 100 free credits — no credit card.What is the Most Used Routes API?
Ranked routes for your Captapi key over a chosen window — endpoint, request counts, creditsUsed. Live account data — not cached. Free.
What you get
- Live data for your Captapi API key (never cached)
- No credit charge for account endpoints
- Clean JSON ready for dashboards and low-balance alerts
- Useful for monitoring usage and spend
Try it
Fill in the parameters below and copy a ready-to-run request, or open the live Playground to run it against your account (no API key paste).
Parameters
curl "https://api.captapi.com/v1/account/most-used-routes?days=value" \
-H "Authorization: Bearer capt_live_..."
# or: -H "x-api-key: capt_live_..."Edit the parameters and the code updates instantly. Switch languages and hit copy.
Example response
{
"success": true,
"data": {
"days": 30,
"totalReturned": 5,
"routes": [
{
"endpoint": "/v1/instagram/details",
"platform": "instagram",
"requests": 161,
"creditsUsed": 46,
"successfulRequests": 161,
"failedRequests": 0
},
{
"endpoint": "/v1/instagram/basic-profile",
"platform": "instagram",
"requests": 3,
"creditsUsed": 2,
"successfulRequests": 3,
"failedRequests": 0
}
]
}
}Billing metadata is returned in response headers: X-Captapi-Credits (credits charged), X-Captapi-Cache (hit or miss), and X-Captapi-Source. Failed requests (4xx/5xx) are never charged. See the full list of error codes in the error reference.
Response structure
A successful call returns success, cached, creditsUsed, and a data object with the following fields:
Top-level fields
daysDays. Example: 30.totalReturnedNumber of items returned in this response.
Routes
Each item in routes contains:
endpointEndpoint. Example: "/v1/instagram/details".platformPlatform identifier for this response (matches the endpoint's platform).requestsRequests. Example: 161.creditsUsedCredits used. Example: 46.successfulRequestsSuccessful requests. Example: 161.failedRequestsFailed requests. Example: 0.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| days | integer | No | Number of days to include (default 30, max 365). |
| limit | integer | No | Max rows to return (default 20, max 100). Free — does not consume credits. |
Authentication: send your key as Authorization: Bearer capt_live_.... A typical call costs 0 credits. Always live — account endpoints are never cached.
account_most_used_routes 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/most-used-routesand parse the JSON response.
Use cases
Cost hotspots
Rank which Captapi routes burn the most credits for your key.
Product planning
See which integrations your customers actually call.
Frequently asked questions
What does the Most Used Routes API do?+
The Most Used Routes API returns most used routes for your Captapi API key via one GET request to /v1/account/most-used-routes. It returns clean JSON and does not charge credits.
How many credits does the Most Used Routes API cost?+
Account endpoints are free — they do not consume credits.
Do I need a CaptAPI Account API key or OAuth?+
You only need your Captapi API key (Authorization: Bearer). No third-party OAuth is required.
Is the Most Used Routes API suitable for production use?+
Yes. It is a stable REST endpoint with predictable JSON. Account endpoints are always live (never cached) and do not charge credits.
More CaptAPI Account APIs
Ready to use the Most Used Routes API?
Sign up, grab your key, and make your first call in 60 seconds.