Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

OAuth Apps

Connect servers and integrations to the Feathery REST API with an OAuth app and short-lived access tokens.

OAuth apps are for servers and integrations. They belong to the organization rather than a person, so they keep working when the person who created them leaves. Only Admins can create and manage them.

An OAuth app has a client ID and a secret. Your server exchanges them for an access token that lasts 1 hour, then sends that token with each request.

1

Create an OAuth App

  1. Open your Feathery settings, go to the Developer tab, open OAuth apps, and choose New OAuth app.

  2. Name it after the integration that will use it, and choose the Live or Test mode.

  3. Choose its access. See Scopes.

  4. Choose when the secret expires: 90 days, 180 days, or 1 year.

  5. Click Create, then copy the Client ID and Client secret.

2

Get an Access Token

Exchange the client ID and secret for an access token. Use your region's API host:

curl https://api.feathery.io/oauth/token \
  -u "<client ID>:<client secret>" \
  -d grant_type=client_credentials
{
  "access_token": "fthr_oat_...",
  "token_type": "Bearer",
  "expires_in": 3600,
  "scope": "forms:read submissions:read"
}

You can send client_id and client_secret in the form body instead of the -u header. To get a token with less access than the OAuth app has, add a space-separated scope, like -d "scope=forms:read".

3

Call the API

Send the access token as a Bearer token:

curl https://api.feathery.io/api/form/ \
  -H "Authorization: Bearer <access token>"

Access tokens last 1 hour, and there's no refresh token. Request a new access token before the old one expires, or when a request returns 401.

Rotate a Client Secret

Each OAuth app can have two active secrets, so you can rotate without downtime:

  1. Open the OAuth app under OAuth apps in the Developer tab and choose Add secret. Copy the new secret.

  2. Deploy the new secret to your servers, a few at a time if you can.

  3. Watch Last used for the old secret in the OAuth app's Secrets list. Once it stops changing, revoke the old secret.

Revoking a secret also ends the access tokens it issued. Admins get an email 30 days and 7 days before a secret expires.

Change or Delete an OAuth App

Open the OAuth app to rename it or change its access. Taking access away ends any access token that holds it, so your server requests a new one.

Deleting an OAuth app ends all of its secrets and access tokens right away.

Keep It Safe

See Security and Troubleshooting for best practices and fixes for common errors.

Last updated

Was this helpful?