# Legacy alias of get_smart_follows (Smart Follows / former Alpha ranking)

> **Deprecated.** This route is kept for existing clients; new integrations should use the replacement named in the description.

`GET https://twitterscore.io/api/v1/get_alpha`

Identical to /api/v1/get_smart_follows: same parameters, same response. The web page was renamed from "Alpha" to "Smart Follows"; this path is kept working so existing integrations do not break, but new integrations should call /api/v1/get_smart_follows. The two paths are separate wrappers over one implementation so usage analytics can track the migration; they have separate per-minute rate-limit buckets (`api-get-alpha` vs `api-get-smart-follows`) and separate server-side response caches. See get_smart_follows for the full field reference.
**Nested fields**

- `data[]` (array): Same item shape as /api/v1/get_smart_follows — see that endpoint.

## Parameters

| Parameter | Type | Required | Default | Description |
|---|---|---|---|---|
| `days` | integer (`1`, `7`, `30`) | no | `7` | Period window in days: 1, 7 or 30. Any other integer returns {"success": false, "message": "Days param is only available: 1\|7\|30"}; a non-numeric value falls back to 7. |
| `by` | string (`alpha`, `score`, `followers`) | no | `alpha` | Ranking column: `alpha` = change in new smart followers versus the previous period (new_diff), `score` = current Twitter Score, `followers` = current follower count. Case-sensitive; any other value returns {"success": false, "message": "Sorting is only possible by [score\|followers\|alpha]"}. |
| `sort` | string (`desc`, `asc`, `descending`, `ascending`) | no | `desc` | Sort direction: `asc` or `ascending` (case-insensitive) for ascending, anything else for descending. |
| `bucket` | string (`all`, `vc`, `inf`, `angels`) | no | `all` | Which set of smart followers to count: `all`, `vc` (venture capitals), `inf` (influencers) or `angels`. Case-insensitive; unknown values silently fall back to `all`. |
| `page` | integer | no | `1` | 1-based page number; non-numeric, 0 or negative values are treated as 1. |
| `size` | integer | no | `10` | Rows per page, capped at 100; values below 1 are treated as 1, non-numeric falls back to 10. |

## Example request

```bash
curl -s "https://twitterscore.io/api/v1/get_alpha?days=7" \
  -H "X-API-Key: $TWITTERSCORE_API_KEY" \
  -H "User-Agent: my-app/1.0 (contact@example.com)"
```

```python
import os, requests

r = requests.get(
    "https://twitterscore.io/api/v1/get_alpha",
    params={"days": 7},
    headers={"X-API-Key": os.environ["TWITTERSCORE_API_KEY"],
             "User-Agent": "my-app/1.0 (contact@example.com)"},
    timeout=15,
)
data = r.json()
if not data.get("success", True):      # errors arrive as success=false (see /developers/errors/)
    raise RuntimeError(data["message"])
print(data)
```

```javascript
const r = await fetch("https://twitterscore.io/api/v1/get_alpha?days=7", {
  headers: { "X-API-Key": process.env.TWITTERSCORE_API_KEY,
             "User-Agent": "my-app/1.0 (contact@example.com)" },
});
const data = await r.json();
if (data.success === false) throw new Error(data.message);
console.log(data);
```

## Example response

```json
{
  "success": true,
  "total": 1000,
  "page": 1,
  "size": 1,
  "pages": 1000,
  "days": 7,
  "bucket": "all",
  "data": [
    {
      "twitter_id": "295218901",
      "username": "VitalikButerin",
      "name": "vitalik.eth",
      "profile_url": "/twitter/VitalikButerin",
      "profile_image": "https://twitterscore.s3.amazonaws.com/profiles/VitalikButerin.jpg",
      "blue_verified": true,
      "description": "mi pinxe lo crino tcati",
      "twitter_score": 1000,
      "twitter_score_diff": 0,
      "current_followers": 5812345,
      "followers_diff": 14135,
      "total_alpha_followers": 2417,
      "new_alpha_followers_diff": 36,
      "top_alpha_followers": [
        {
          "name": "Balaji",
          "username": "balajis",
          "image": "https://twitterscore.s3.amazonaws.com/profiles/balajis.jpg",
          "score": 942,
          "verified": true
        }
      ]
    }
  ]
}
```

## Errors

Error codes this endpoint can return (see [Errors](/developers/errors/) for the body format): `api_key_missing`, `api_key_invalid`, `api_access_deactivated`, `api_key_revoked`, `method_not_allowed`, `rate_limited`, `quota_exceeded`, `server_error`.

---

Authentication: `X-API-Key` header (or `Authorization: Bearer`), see [Authentication](/developers/authentication/). Limits: per-minute rate and monthly quota by plan, see [Rate limits](/developers/rate-limits/). Machine-readable definition: [/openapi.json](/openapi.json).