Twitter Follow Check API - Best-Effort Recent Relationship

Supply required user for the source account and follows for the target account. The read offers a best-effort follow-relationship check and is explicitly limited for large accounts or older relationships. Accepted identifier formatting and exact result fields have not been live-verified; validate a public account pair before building a parser. Use a positive match as supporting evidence, but treat a negative result as inconclusive rather than definitive proof that the source does not follow the target. This endpoint checks a relationship and does not create or remove a follow.

API Features

Directional account-pair input user identifies the source and follows identifies the target, preserving the direction of the requested relationship.

Recent-follow suitability The documented limitations make this check more appropriate for recent connections than long-established relationships.

Large-account uncertainty Coverage can be unsuitable for large accounts, so absence of a positive match must not be treated as proof of no follow.

Relationship check without mutation This read inspects a possible connection; it does not subscribe the source account to the target or remove a subscription.

Live API Demo

GET /api/project/twitter/check-follow

API Response (JSON)

{}

curl -X GET 'https://api.opendata-api.com/api/project/twitter/check-follow?key=<API_KEY>&user=<user>&follows=<follows>'

curl -X GET 'https://api.opendata-api.com/api/project/twitter/check-follow?key=<API_KEY>&user=<user>&follows=<follows>'

📢

Need Help?

If you encounter API issues or need other API requirements, please contact us.

Use Cases

Add supporting evidence for a recently established public account relationship in a manual audit.
Spot-check a recent connection between smaller public accounts after validating identifier format.
Route inconclusive relationship checks to a human reviewer instead of rejecting a participant automatically.
Test whether this limited check suits an account-pair workflow before choosing broader following-page collection.

Frequently asked questions

Which direction does the follow check inspect?

Required user selects the source account and required follows selects the target account. Accepted identifier formatting and result fields need validation with a public account pair. The read does not create or remove a follow.

Does a negative follow check prove there is no relationship?

No. This best-effort check has documented limits for large accounts and older relationships. A validated positive match can support a review, but a negative result is inconclusive rather than definitive proof of no follow.

Related operations

Guides

View Subscription Plans →

Check a Recent Follow Relationship