Permalink
Browse files

s/him/them

  • Loading branch information...
georgeclaghorn committed Feb 6, 2018
1 parent 59467f6 commit f723f922a3b4287dcd883690cd91527036154a45
Showing with 2 additions and 2 deletions.
  1. +2 −2 sections/authentication.md
@@ -39,7 +39,7 @@ OAuth 2
For a full app integration, you wouldn't want to get into the business of asking
customers for their passwords -- or storing them! -- so we offer a simple way to
ask a user for access to their account. You get an API access token back without
ever having to see their password or ask him to copy/paste an API key.
ever having to see their password or ask them to copy/paste an API key.
1. [Grab an OAuth 2 library](http://oauth.net/code/).
2. Register your app at [integrate.37signals.com](https://integrate.37signals.com). You'll be assigned a `client_id` and `client_secret`. You'll need to provide a `redirect_uri`: a URL where we can send a verification code. Just enter a dummy URL like `http://myapp.com/oauth` if you're not ready for this yet.
@@ -72,7 +72,7 @@ The typical flow for a web app:
Authorization: Bearer YOUR_OAUTH_TOKEN
6. To get info about the Basecamp ID you authorized and the accounts you have access to, make an authorized request to `https://launchpad.37signals.com/authorization.json` (or `/authorization.xml`). (See
6. To get info about the Basecamp ID you authorized and the accounts you have access to, make an authorized request to `https://launchpad.37signals.com/authorization.json` (or `/authorization.xml`). (See
Implementation notes:

0 comments on commit f723f92

Please sign in to comment.