Capabilities
| Resource | Sync | Provision |
|---|---|---|
| People | ||
| Projects | ||
| Project membership |
Gather Basecamp credentials
Basecamp authenticates with 3-legged OAuth 2.0. You register an OAuth application, complete the one-time authorization in a browser to obtain a long-lived refresh token, and provide that refresh token to the connector. The connector exchanges it for short-lived access tokens automatically.Register an OAuth application at
launchpad.37signals.com/integrations.
Note the Client ID and Client Secret.
Complete the OAuth authorization flow once to obtain a refresh token
for the account you want to sync. The authorization request goes to
https://launchpad.37signals.com/authorization/new and the token
exchange to https://launchpad.37signals.com/authorization/token.Find your account’s API base URL at
launchpad.37signals.com/authorization.json.
Use the
href of the accounts[] entry whose product is bc3 — it
looks like https://3.basecampapi.com/1234567. If your identity has
access to more than one Basecamp account, pick the one to sync.Configure the Basecamp connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your Basecamp connector is now pulling access data into C1.
Enter the Basecamp credentials:
- Basecamp API base URL: Your per-account API base, e.g.
https://3.basecampapi.com/1234567. - OAuth client ID: The Client ID of your Basecamp OAuth application.
- OAuth client secret: The Client Secret of your Basecamp OAuth application.
- OAuth refresh token: The long-lived refresh token from the authorization flow.