> 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/highrise.md).

# Highrise

Unfortunately, since August 20, 2018 [Highrise](https://highrisehq.com/) no longer accepts signups.

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

We keep the module in Appmixer for the older customers who have their Oauth2 application. If you are a new Appmixer customer, you won't be able to create the OAuth2 application and therefore use the Highrise module. In that case, you should remove it from the platform.

## OAuth app properties

| Property                | Value                                                                                                                                                                                                   |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Multi-tenant**        | **Yes.** Any existing Highrise account can authorize the app.                                                                                                                                           |
| **Vendor review**       | **None.**                                                                                                                                                                                               |
| **Review time**         | Not applicable.                                                                                                                                                                                         |
| **Users before review** | No limit, but only people who already have a Highrise account.                                                                                                                                          |
| **App owner**           | A 37signals account. Apps are registered at [launchpad.37signals.com/integrations](https://launchpad.37signals.com/integrations).                                                                       |
| **Regions**             | One app works worldwide.                                                                                                                                                                                |
| **Client secret**       | No expiry documented.                                                                                                                                                                                   |
| **Rate limits**         | 150 requests per 5 seconds per IP address and account. Contact search by e-mail: 2 per 10 seconds; `GET /recordings.xml`: 10 per 10 seconds. Over the limit, Highrise returns `503` with `Retry-After`. |
| **Checked**             | 2026-11-13                                                                                                                                                                                              |

**Limitations**

* Highrise has not accepted new signups since 2018-08-20. Existing accounts keep working, and 37signals says it maintains the product for current customers.
* Access tokens last about two weeks; the connector renews them with the refresh token. Highrise publishes no lifetime for the refresh token.

Sources: [Highrise](https://highrisehq.com/), [Highrise API](https://github.com/basecamp/highrise-api), [37signals API authentication](https://github.com/basecamp/api/blob/master/sections/authentication.md). What the rows mean: [OAuth app properties](https://docs.appmixer.com/connector-configuration/oauth-app-properties.md).

## Backoffice configuration

Configuration ID: `appmixer:highrise` (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 your existing 37signals Launchpad integration. Not needed when Highrise is authenticated through the Appmixer Auth Hub.
* `clientSecret` — Client secret of the same integration. Not needed with the Auth Hub.
* `userAgent` — Optional. The `User-Agent` header sent with every request to the Highrise API. Default `AppMixer Dev info@appmixer.com (https://appmixer.com)`, or the value of the `GRIDD_USER_AGENT` environment variable of the Appmixer engine when it is set.

![Change user agent.](https://802996127-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIAGKHlIqVKJe9agnFr14%2Fuploads%2Fgit-blob-d5f2b146eed2a72b5dfc4c72ef3784816399a605%2Fhighrise-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:highrise -u -d '{
  "clientId": "<client id>",
  "clientSecret": "<client secret>",
  "userAgent": "<app name> (<contact e-mail>)"
}'
```


---

# 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/highrise.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.
