Tutorial / Authenticating with the Twitter API for enterprise
Which authentication method to use for each API
The following table highlights which authentication method is required for each of the different Enterprise APIs. In the case where two authentication methods are highlighted, the right method to use will depend on the specific endpoint being used and what data is being requested.
| Enterprise API | HTTP Basic |
OAuth 1.0a (user context) |
OAuth 2.0 Bearer Token (application-only) |
| PowerTrack API | ✓ | ||
| Decahose API | ✓ | ||
| Account Activity API | ✓ | ✓ | |
| Full Archive Search API | ✓ | ||
| 30-Day Search API | ✓ | ||
| Historical PowerTrack API | ✓ | ||
| Engagement API | ✓ | ✓ | |
| Compliance Firehose API | ✓ | ||
| Usage API | ✓ |
Additional information on specific authentication requirements is available for each of the following products:
Go to the next article - OAuth 1.0a: how to obtain a user's access tokens
Go back to the tutorial homepage - Authenticating with the Twitter API for enterprise
Ready to build your solution?