> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/connector-configuration/typeform.md).

# Typeform

## OAuth app properties

| Property                | Value                                                                                                                                                                |
| ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multi-tenant**        | **Yes.** Any Typeform user can authorize the app, except accounts in Typeform's new EU data center.                                                                  |
| **Vendor review**       | **None.**                                                                                                                                                            |
| **Review time**         | Not applicable.                                                                                                                                                      |
| **Users before review** | No limit.                                                                                                                                                            |
| **App owner**           | Any Typeform account. The app is registered under **Developer Apps** in the organization menu.                                                                       |
| **Regions**             | US accounts and accounts on `api.eu.typeform.com` use the same app. Accounts in the new EU data center (`api.typeform.eu`) have their own OAuth endpoint and tokens. |
| **Client secret**       | No expiry documented. Shown once; it can be regenerated in **Edit app**.                                                                                             |
| **Rate limits**         | 2 requests per second per Typeform account (Create and Responses APIs). Webhooks are not limited.                                                                    |
| **Checked**             | 2026-11-13                                                                                                                                                           |

**Limitations**

* The connector calls `api.typeform.com` only. Accounts in the new EU data center cannot connect.
* With **One Week** tokens and `useRefreshToken` not set, a connected account stops working a week after it was connected. Set `useRefreshToken` to `true`, or choose **Unlimited**.
* Each refresh replaces the refresh token. Typeform publishes no lifetime for refresh tokens.

Sources: [Applications](https://www.typeform.com/developers/get-started/applications/), [Get started](https://www.typeform.com/developers/get-started/), [EU Responses data center](https://www.typeform.com/developers/get-started/responses-data-center/). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

## Register the app

When creating Typeform Oauth2 application (<https://admin.typeform.com/account#/section/apps>), you can choose between access tokens that do expire in a week and access tokens that do not expire.

![Token expiration settings.](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-ec9c47e7fc46ed7a1f957f0e35dd71ffd2f65a09%2Ftypeform-1.png?alt=media)

The token expiration is new in Typeform. Appmixer components before version 4.2 cannot handle it.

If you're registering the Oauth application for version 4.2 or newer, you can decide if you want to use tokens that do expire or not. *Unlimited* is the default behavior of the connector. To use the One Week tokens, set `useRefreshToken` in the Backoffice (see [Backoffice configuration](#backoffice-configuration)).

![](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-988b09419ea5ac22d7792ec97f55cb40e4f7c441%2Ftypeform-3.png?alt=media)

## Backoffice configuration

Configuration ID: `appmixer:typeform` (Backoffice → Configuration; see [Connector Configuration](https://docs.appmixer.com/getting-started/services) for how a configuration is created and how its keys reach the connector).

* `clientId` — Client ID of the Typeform app registered above. Not needed when Typeform is authenticated through the Appmixer Auth Hub.
* `clientSecret` — Client secret of the same app. Not needed with the Auth Hub.
* `useRefreshToken` — Optional. Set to `true` when the app uses **One Week** tokens: the connector then requests the `offline` scope and refreshes the token. Leave it out for **Unlimited** tokens. Any non-empty value turns it on, so remove the key instead of setting it to `false`.

![useRefreshToken set in the Backoffice](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-85b5f6b4126c6c89cdd2bcd77a1c4c335fe21573%2Ftypeform-2.png?alt=media)

The same keys can be set with the CLI (`-u` updates the existing configuration instead of creating it):

```bash
appmixer service-config set appmixer:typeform -u -d '{
  "clientId": "<client id>",
  "clientSecret": "<client secret>",
  "useRefreshToken": true
}'
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.appmixer.com/connector-configuration/typeform.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
