Crypto News Search API
API health
- 24h health
- Normal
- 24h average time
- —
- Healthy / normal
- Available
- Limited
- Mostly down
Last 24 hours
Last 30 days
Search crypto news by keyword and get up to 100 articles ranked by relevance, each with title, summary, outlet, link and publish time.
Price $4.81 per 1,000 requests ($0.004806 per call). Failed calls and empty results are not charged. Synchronous. For slow jobs add "mode": "async" to the body, take the job_id and poll.
AI prompt
Please help me write a data collection script with the EveryInfra Crypto News Search endpoint (crypto_news/search).
How the endpoint works:
- Request: POST https://api.everyinfra.com/api/v1/social with the header Authorization: Bearer <API key>. Read the key from the EVERYINFRA_API_KEY environment variable and never hard-code it.
- In the request body, set platform to crypto_news and action to search, and put the parameters inside params.
- Required parameters:
- keyword: Search words for search, 2 to 100 characters, such as bitcoin ETF; results are ranked by relevance, not date.
- Optional parameters:
- limit: The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. (default: 20)
- Returns a list of records. Main fields of each record: title, summary (A one or two sentence summary, not the…), source (Publishing outlet in upper case, such a…), url (Link to the original article), published_at (Publish time, ISO 8601 UTC), project_name (Project or topic the article is about,…).
- Example request body:
{
"platform": "crypto_news",
"action": "search",
"params": {
"keyword": "bitcoin ETF"
}
}
- Price: $4.81 per 1,000 requests; failed and empty results are not charged.
- For dozens or hundreds of targets, add "mode": "async" to the body: you get a job_id at once and poll GET https://api.everyinfra.com/api/v1/jobs/{job_id} for the result.
- On 422, fix the request using the suggested parameter names and allowed values in the error; on 429 or 503, wait for Retry-After and try again.
Before writing code, ask me which targets I need, how many, which fields, and what output format I want; then confirm the plan and the rough cost with me.Request parameters
| Name | In | Type | Required | Default | Description |
|---|---|---|---|---|---|
Authorization | header | string | Yes | - | Bearer followed by your API key. Create it in the console; never put it in a URL or a code repository. |
platform | body | string | Yes | crypto_news | Platform identifier, fixed value. |
action | body | string | Yes | search | Capability identifier, fixed value. |
keyword | body.params | string | Yes | - | Search words for search, 2 to 100 characters, such as bitcoin ETF; results are ranked by relevance, not date. |
limit | body.params | integer (1–100) | No | 20 | The most rows to return in this call, an integer from 1 to 100. The default applies when you leave it out, and a call can return fewer rows. Larger values return 422 before any charge. |
Code samples
curl -X POST 'https://api.everyinfra.com/api/v1/social' \
-H "Authorization: Bearer $EVERYINFRA_API_KEY" \
-H 'Content-Type: application/json' \
--data-raw '{
"platform": "crypto_news",
"action": "search",
"params": {
"keyword": "bitcoin ETF"
}
}'OpenAPI definition (JSON)Samples read the key from the EVERYINFRA_API_KEY environment variable; copied code never contains your key.
Response example
No sample response is available for these parameters yet. This preview shows the response shape and fields from the API definition, with … as placeholders; it is not the result of a live call.
{
"id": "req_…",
"platform": "crypto_news",
"action": "search",
"results": [
{
"title": …,
"summary": …,
"source": …,
"url": …,
"published_at": …,
"project_name": …,
"platform": …
}
],
"count": …,
"billing": {
"charged": …,
"charged_usd": …,
"balance_after_usd": …,
…
},
"quota": { … }
}Response fields
Business data is in results. The table lists the fields a record can contain; values the platform does not show are never made up.
| Field | Meaning |
|---|---|
title | Title. null when the platform has no titles (for example text-only posts). |
summary | A one or two sentence summary, not the full text; open url to read it. |
source | Publishing outlet in upper case, such as COINDESK or AMBCRYPTO. |
url | Link to the original article. |
published_at | Publish time, ISO 8601 UTC. |
project_name | Project or topic the article is about, such as Bitcoin; absent when none. |
platform | Source platform identifier, the same as platform in the request (for example xiaohongshu, tiktok). |
Errors and billing
- 401
- Missing or invalid key.
- 402
- Insufficient balance. Top up first.
- 422
- Invalid parameter name or value. Fix it using the suggestions in the error. No charge.
- 429
- Per-minute request limit reached. Wait for Retry-After, then try again.
- 503
- Could not complete. The held charge is returned to your balance. If the outcome is unknown, verify it before you retry.
- 200 empty
- No data. No charge.