Features/REST API

Secure API authorization

Send API keys and tokens as request headers that are added on the server and never shipped to the visitor's browser.

Authorization for a REST request is done with request headers, for example Authorization: Bearer <token> or an API key header. Headers are stored with the request and added when the server sends it. Because the request runs server side, the visitor only receives the resulting data, not the credentials. Header values can also use variables, for example to pass a value that depends on the page.

How it works

  • Headers are a key/value list on each request (Request Headers). Empty keys or values are dropped.
  • Default header Content-Type: application/json is added only if no header is set.
  • The same header mechanism is used by the native Airtable and Strapi integrations (Authorization: Bearer <key>).
  • There is no built-in OAuth flow for generic REST requests; tokens must be static or provided via properties/variables.

When to use it

  • Call a private API with a Bearer token
  • Use an API key header for a paid data provider

Limitations

  • No OAuth 2.0 flow or token refresh for generic REST requests
  • Header values are shown in plain text in the request editor and in the cURL preview for site admins

Availability

  • Works in Designer.
  • Included in every plan.

How to use it.

  1. Open a request in REST API
  2. Under Request Headers click Add Header
  3. Enter the header name (for example Authorization) and the value (for example Bearer <token>)
  4. Run API to verify

Questions.

Will visitors see my API key?

Is OAuth supported?

Related features.

No card needed

Build it today.Pay when it goes live.

Every feature is unmetered while you build. Checkout opens the first time you publish.