Supported providers

The table below lists the social networks and identity providers currently supported by Hybridauth 3 and outlines their enabled features (or capabilities).

A provider or IDP means a social network, identity provider or authentication service. An adapter is the actual PHP class implemented by Hybridauth to abstract a provider’s API.
While OpenID providers do not require an application [1] and thus no action from your part to make their adapters work, OAuth providers requires consumer (or client) websites (e.g., your website) to register an application [2] [3]. Generally speaking those providers will have a dedicated developer’s section or subdomain where you can register yours and apply for a pair of keys (i.e, application credentials ).
When we mention OpenID, we mean the original v1 or v2 protocols. OpenID Connect is an entirely different specification which is built on top of OAuth; many of the OAuth providers are actually using OpenID Connect also.
Adapter Unique Name Specs Authentication User’s Profile User’s Contacts User’s Status User’s Activity Stream
Apple OAuth2      
Amazon OAuth2      
AOLOpenID OpenID      
Authentiq OAuth2      
AutoDesk OAuth2      
BitBucket OAuth2      
Blizzard OAuth2      
Discord OAuth2      
Disqus OAuth2      
Dribbble OAuth2      
Dropbox OAuth2      
Facebook OAuth2  
Foursquare OAuth2    
GitHub OAuth2      
GitLab OAuth2      
Google OAuth2    
Instagram OAuth2      
Keycloak OAuth2      
LinkedIn OAuth2    
Mastodon OAuth2      
Medium OAuth2      
MicrosoftGraph OAuth2    
OpenID OpenID      
ORCID OAuth2      
Paypal OpenID      
PaypalOpenID OpenID      
Reddit OAuth2      
Slack OAuth2      
Spotify OAuth2      
StackExchange OAuth2      
StackExchangeOpenID OpenID      
Steam Hybrid      
Seznam OAuth2      
Strava OAuth2      
SteemConnect OAuth2      
Telegram Hybrid      
Tumblr OAuth1  
TwitchTV OAuth2      
Twitter OAuth1
WeChat OAuth2      
WindowsLive OAuth2    
WordPress OAuth2      
Yahoo OAuth2      
QQ OAuth2      
Some providers such as Paypal and StackExchange may use multiple protocols for their APIs and as naming convention we append the protocol’s name to the adapters (Often the case with OpenID adapters as those might be subject to removal by providers in near future due to deprecation of the OpenID protocol).