raw.instagram.hashtag_postsInstagram hashtag posts
https://api.qovia.ai/v1/raw/instagram/hashtag_postsThe newest posts carrying a hashtag, about 30 a page, as the same records as post detail (same ids) with the author's user ID only and no plays, shares or carousel slides; total is how many posts carry the hashtag. Pass the previous page's cursor back unchanged to continue; stop when has_more is false. A hashtag nobody used answers empty and is not charged.
- Price
- $0.001 / call$1 per 1k · fixed price
- Billing
- Charged only for successful, non-empty resultsno free quota
- Scope
raw:instagramThe API key needs this scope- Rate cap
- Account limit onlyYour per-minute limit
Parameters
Only these parameters are accepted; any other one returns 400.
hashtagThe hashtag (without
Max 100 charsPattern^[^\s#@,.!?&/\\]+$Example
travelcursorThe cursor from the previous page's response, unchanged; leave it out for the first page
Max 4000 charsPattern^[A-Za-z0-9_=+/-]+$
Response
A success is HTTP 200 with the shared envelope: request_id, data (this endpoint's data, see the example) and meta (the charge). An empty result is also 200, with meta.empty true, not charged, and data may be an empty structure or null.
Errors
| code | HTTP | Billing | Description |
|---|---|---|---|
scope_denied | 403 | Not charged | This API key lacks the scope the endpoint requires. |
endpoint_unavailable | 503 | Not charged | The endpoint is not available right now (no data source connected yet, or no price configured); nothing ran. |
invalid_params | 400 | Not charged | The parameters failed validation: a required one is missing, a type or format is wrong, an unknown one was sent, or the POST body is not a JSON object. An error in one parameter starts with its name (item_id: …); a missing or unknown parameter starts with params: …. |
rate_limitedRetryable | 429 | Not charged | Over the account's per-minute limit (sliding 60-second window); wait for Retry-After. |
too_many_unbilledRetryable | 429 | Not charged | In the last 10 minutes at least 50 of your calls to data sources, and over 80% of them, came back empty, not found or rejected; slow down. |
insufficient_balance | 402 | Not charged | The balance cannot pay for this call (the free quota is used up, or the endpoint does not use it). |
upstream_busyRetryable | 503 | Refunded | The data source is busy or cooling down; refunded. Retry after Retry-After. |
upstream_timeout | 504 | Refunded | The data source timed out; refunded. |
upstream_error | 502 / 503 | Refunded | The data source failed; refunded. |
upstream_rejected | 400 | Refunded | The data source rejected these parameters (well-formed, but not accepted); refunded. |
not_found | 404 | Refunded | The data source has no such item (deleted, or the ID does not exist); refunded. |
reservation_expired | 504 | Refunded | The call took too long and was refunded automatically; no data is returned. |
Any request can also fail authentication: 401 invalid_api_key, 403 account_disabled, 429 too_many_auth_failures.
Needs an account; playground calls are billed like API calls.