668
edits
Privacy/BestPractices/OAuth: Difference between revisions
Jump to navigation
Jump to search
→Making API Calls
| Line 23: | Line 23: | ||
The resulting access token is the user-specific credential that can be used to make API calls. | The resulting access token is the user-specific credential that can be used to make API calls. | ||
=== | === Authenticating API Calls === | ||
To make OAuth-credentialed API calls, the consumer adds authentication information to the HTTP calls it makes. This authentication information ranges from adding the access token as a GET parameter (OAuth 2.0 bearer tokens), to canonicalizing the request and signing it with HMAC using a combination of the <tt>consumer_secret</tt> and <tt>access_token_secret</tt> (OAuth 1.0 HMAC). | To make OAuth-credentialed API calls, the consumer adds authentication information to the HTTP calls it makes. This authentication information ranges from adding the access token as a GET parameter (OAuth 2.0 bearer tokens), to canonicalizing the request and signing it with HMAC using a combination of the <tt>consumer_secret</tt> and <tt>access_token_secret</tt> (OAuth 1.0 HMAC). | ||