Add OAuth 2 authentication guide with standard parameters #374
+165
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
sections/authentication.mdwith BC3-specific OAuth 2 docs using standard parameters (response_type=code,grant_type=authorization_code,grant_type=refresh_token) and updated token response includingtoken_type: "Bearer"README.mdto link auth guide locally and add Authentication to the API endpoints indexContext
Auth docs currently live in
basecamp/apiand cover all products with legacy Launchpad OAuth parameters. This imports and adapts them for BC3 only, using the standard OAuth 2.0 parameters added in launchpad#769 and thetoken_typefield from signal_id#314.Legacy parameters (
type=web_server,type=refresh) are noted as still supported but not recommended.Test plan
sections/authentication.mdfollows the section file format (Setext headings, example JSON with markers, cURL blocks)launchpad.37signals.comauthorization/token endpointssections/authentication.md