API Integration

The FourYourSafety API provides programmatic access to Twitter/X intelligence data tracked by the FYS browser extension. All endpoints return JSON and are available under:

https://fouryoursafety.fun/api/

Authentication

• API Key required in request headers:

Authorization header

Authorization: Bearer YOUR_API_KEY

• Keys are tied to usage credits.

• Unauthenticated requests will return 401 Unauthorized.

---

Endpoints

Get Deleted Tweets

Retrieve a list of deleted tweets from a given user.

Endpoint

GET /api/deleted-tweets

Query Parameters

• user (string, required) – Twitter username

• limit (int, optional, default: 20) – Number of tweets to fetch

Example Request

Request

GET https://fouryoursafety.fun/api/deleted-tweets?user=CryptoInfluencer&limit=5
Authorization: Bearer key

Example Response for deleted tweets fetching (fictitious information)

Response

{
  "user": "CryptoInfluencer",
  "deleted": [
    {
      "id": "172839293",
      "text": "Buy this token now: QxO2...pump",
      "timestamp": "2025-10-01T12:34:56Z"
    },
    {
      "id": "172839294",
      "text": "Partnership incoming...",
      "timestamp": "2025-10-01T13:21:11Z"
    }
  ]
}

---

Get Contract Addresses

Fetch contract addresses mentioned in tweets from a user.

Endpoint

GET /api/contract-addresses

Query Parameters

• user (string, required)

• limit (int, optional)

Example Request

Request

GET https://fouryoursafety.fun/api/contract-addresses?user=ZssBecker

Example Response for CA tweets (fictitious information)

Response

{
  "user": "ZssBecker",
  "addresses": [
    {
      "ca": "0x98ab76...",
      "tweetId": "987654321",
      "timestamp": "2025-10-02T09:10:00Z"
    }
  ]
}

---

Get First Followers

List the earliest followers of a new account.

Endpoint

GET /api/first-followers

Query Parameters

• user (string, required)

• page (int, optional) – For pagination

Example Request

Request

GET https://fouryoursafety.fun/api/first-followers?user=NewProjectX&page=1

Example Response for first followers (fictitious information)

Response

{
  "user": "TotallyNotFarming",
  "first_followers": [
    {"username": "cupseyy", "followed_at": "2025-09-29T10:05:00Z"},
    {"username": "ga__ke", "followed_at": "2025-09-29T10:07:45Z"}
  ]
}

---

Get Profile Changes

Track bio and username history.

Endpoint

GET /api/profile-changes

Query Parameters

• user (string, required)

Example Request

Request

GET https://fouryoursafety.fun/api/profile-changes?user=TokenShiller

Example Response for bio changes (fictitious information)

Response

{
  "user": "TokenShiller",
  "changes": [
    {
      "field": "bio",
      "old": "Lover of cats and memes",
      "new": "Early investor in $TRUMP",
      "changed_at": "2025-09-25T08:00:00Z"
    },
    {
      "field": "username",
      "old": "TokenShiller",
      "new": "TRUMP_God",
      "changed_at": "2025-09-26T09:30:00Z"
    }
  ]
}

---

Get Key Followers

Identify notable accounts in a user’s follower network.

Instantly find out if any notable figures in CT are following the project you're eyeballing, this usually gives you a clear indication of alpha or not. See reputable traders following? Then you're most likely on the right track.

Endpoint

GET /api/key-followers

Query Parameters

• user (string, required)

Example Request

Request

GET https://fouryoursafety.fun/api/key-followers?user=CryptoGuru

Example Response for key followers (fictitious information)

Response

{
  "user": "loof",
  "key_followers": [
    {"username": "cupseyy", "score": 9291},
    {"username": "ga__ke", "score": 10292}
  ]
}

---

Error Codes

• 200 OK – Successful request

• 400 Bad Request – Invalid query parameters

• 401 Unauthorized – Missing or invalid API key

• 404 Not Found – Resource not found

• 429 Too Many Requests – Rate limit exceeded

• 500 Internal Server Error – Unexpected server error

---

Rate Limits

• Free Tier: 100 requests / day

• Pro Tier: 10,000 requests / day

• Exceeding limits returns 429 Too Many Requests

---

Example Workflow

1

Fetch deleted tweets for a project account

Use the deleted-tweets endpoint to retrieve tweets that were removed.

2

Cross-check if any contract addresses were mentioned

Use the contract-addresses endpoint to find on-chain addresses mentioned in those tweets.

3

Analyze first followers of the same account

Use the first-followers endpoint to inspect early followers for patterns or suspicious accounts.

4

Monitor profile changes over time

Use the profile-changes endpoint to track bio and username history that might indicate rebrands or impersonation.

5

Rank key followers to determine insider clusters

Use the key-followers endpoint to identify notable accounts and cluster insiders or influential followers.

This workflow allows traders to detect suspicious patterns and researchers to archive data systematically.