Skip to main content
Every endpoint uses the same method: Bearer Token with your Secret Key.

Bearer Token

Send your Secret Key (sk_proj_...) in the Authorization header:
This pattern works for all endpoints:
  • Sending: POST /v1/send-email, POST /v1/send-template-email, POST /v1/send-batch, POST /send-email
  • Domains: POST /domains/register, GET /domains/:domain/dns-records, POST /domains/:domain/verify, GET /domains/:domain/status, GET /domains?domain=, POST /domains/:domain/recreate, DELETE /domains/:domain, PUT /domains/:domain/sender, POST /domains/verify-email, GET /domains/verify-email/status
  • Activity: GET /v1/activity, GET /v1/activity/:id
  • Data: POST /v1/leads, POST /v1/events (and the rest of the leads and events API)

Example

How it works

  1. The server extracts the Secret Key from the Authorization header
  2. It validates the key and resolves the associated project
  3. If the key is valid, the projectId is derived automatically — you don’t need to send it

Where to find your Secret Key

  1. Log in to the RQE dashboard.
  2. Select your project.
  3. In the sidebar, open Integrations → API Keys.
  4. Copy your Secret Key (it starts with sk_proj_).
There you’ll also find the Test key (sk_test_*). See API Keys for the differences between Live and Test mode.

Error responses

Missing key or incorrect format (401):
Invalid key (401):

Common errors