Skip to main content

Store API Keys and Other Credentials Safely with Secret Values

Use the Secret option in Call API headers and query strings to keep API keys, tokens, and passwords out of your tables and off your users' devices.

Most outside services ask for a credential before they answer a request, like an API key, a bearer token, or a username and password. With Secret values, you can store any of these credentials in your Glide app without putting them in a table or sending them to your users' devices.

What is a Secret value?

A Secret value is text you type straight into the Headers or Query string section of a Call API action or column. When you choose Secret instead of a column:

  • The value is encrypted and stored on Glide's servers, separately from your app. Your app only keeps a reference to it.

  • The value is added to the request on Glide's servers, at the moment the call runs.

  • The value never appears in your tables, in the Data Editor, or in the app your users download.

Where you can use Secret values

  • Call API action, in screen actions and workflows

  • Call API column in the Data Editor

In both places, the Secret option is available for the values in Headers and Query string. It is not available for the Endpoint or the Body, so don't put credentials in those fields.

Built-in integrations that ask for an API key (for example, OpenAI) already store that key the same way. You only need the steps below for services you call yourself with Call API.

How to add a Secret value

  1. Add a Call API action, workflow step, or column, and enter the Endpoint and Method.

  2. In Headers (or Query string), click Add value.

  3. In the name field, type the name the service expects, for example Authorization or x-api-key.

  4. Open the value's menu and choose Secret.

  5. Type or paste the full value exactly as the service expects it, for example Bearer sk-12345…. The value is sent as is, so include any prefix such as Bearer or Basic .

The value saves automatically as you type. There is no separate save button.

Examples

Service expects

Section

Name

Secret value

Bearer token

Headers

Authorization

Bearer YOUR_TOKEN

API key header

Headers

x-api-key

YOUR_KEY

Username and password (Basic auth)

Headers

Authorization

Basic followed by your Base64-encoded username:password

API key in the URL

Query string

api_key

YOUR_KEY

Secret value or column?

Each header or query value is either a Secret or a column. You can't mix the two in one field. Use a Secret for anything that should stay private, and use columns for values that change from row to row.

Secret

Column

Where it's stored

Encrypted on Glide's servers

In your table

Visible in the Data Editor

No

Yes

Can be different per row or per user

No, one fixed value

Yes

Good for

API keys, tokens, passwords

IDs, names, search terms

Who can see a Secret value

  • App users can't see it. It is never sent to their devices.

  • Anyone who can edit the app can open the Call API configuration in the builder and see or change the value. Only give edit access to people you trust with these credentials.

Changing or removing a Secret value

  • To change it (for example, after you rotate a key with the service), replace the text in the field. The new value applies to the next call right away, including in your published app, without republishing. Update it in Glide at the same time you change it at the service so calls don't fail in between.

  • To remove it, delete the header or query row.

Troubleshooting

  • The service answers 401 or 403. Open the Secret value and check that it matches what the service expects, including any prefix (Bearer , Basic ) and with no extra spaces or line breaks.

  • The Secret field is empty in a duplicated app. Type the credential again in the copy. Check every Call API action, step, and column after you duplicate an app that uses Secret values.

  • You need the credential inside the Body. Secret values only work in Headers and Query string. Most services accept credentials in a header, so check the service's documentation for a header-based option.

Did this answer your question?