# Teamleader — CRM API: connection

> Canonical URL: https://developers.apideck.com/apis/crm/teamleader/connection

# How to connect Teamleader Focus

Connecting Teamleader Focus takes one action: click **Authorize** and sign in with your Teamleader
Focus login. You don't create, copy or paste any credentials: no client ID, no client secret, no
API key. Vault has no Teamleader settings to fill in either (no subdomain, region or account ID).
Apideck runs the OAuth flow and refreshes the access token automatically afterwards, so the
connection keeps working without you signing in again.

Each unified API you use gets its own connection in Vault, so if you use both the CRM and the Lead
API, authorize both. Sign in with the same Teamleader Focus login each time.

## Prerequisites

- **A Teamleader Focus account.**
- **A Teamleader Focus user who can see the data you want to sync.** The integration acts on
  behalf of the user who authorizes it, so that user needs access to the contacts, companies and
  deals the integration will read or write.
- **The right Teamleader account in mind.** Each connection is tied to the Teamleader Focus
  account you sign in to, so sign in to the one this connection is for.

## Steps

1. Open the Teamleader connection in Apideck Vault and click **Authorize**. Vault redirects you to
   Teamleader Focus.
2. Sign in with the Teamleader Focus account this connection should use.
3. Review the access request and approve it. For the CRM API, Teamleader asks for access to:

   - **Contacts**
   - **Companies**
   - **Deals** (used for opportunities)
   - **Users**

   For the Lead API, it asks only for **Contacts** (leads are Teamleader contacts).

   Notes on contacts, companies and deals don't need any extra permission.

4. Teamleader sends you back to Vault and the connection is authorized.

The application name on the Teamleader approval screen depends on who set up the integration. It
shows **Apideck** when the integration uses Apideck's own credentials. If the provider of your
integration registered their own Teamleader integration, it shows that integration's name instead.

You are never asked for a redirect URL, client ID or client secret. Those belong to the Teamleader
integration held by the provider of your integration. If you set that integration up yourself,
see the
[Teamleader OAuth credentials guide](https://developers.apideck.com/connectors/teamleader/docs/application_owner+oauth_credentials).

## Troubleshooting

**Teamleader shows `invalid_request` with "Check the redirect_uri parameter".**
The Teamleader integration behind this connection doesn't have the Apideck redirect URI
registered. This isn't something you can fix from your Teamleader account: contact the provider
of your integration and let them know. Once they add the redirect URI to their Teamleader
integration, click **Authorize** again.

**Some contacts, companies or deals are missing after connecting.**
The integration can only see what the Teamleader user who authorized it can see. Check that
user's access in Teamleader Focus, or reconnect with a user who has access to the records you
need.

**You connected the wrong Teamleader account.**
Disconnect the connection in Vault, click **Authorize** again and sign in to the correct
Teamleader Focus account. If you connected both the CRM and the Lead API, do this for each
connection.

If the connection still fails, contact [Apideck Support](https://help.apideck.com/en/articles/7774658).


[API reference](https://developers.apideck.com/apis/crm/reference.md) · [Coverage matrix](https://developers.apideck.com/apis/crm/coverage)