Add Bearer Authentication for Cryvis in Make.com

Cryvis authenticates every extraction request with a Bearer API key:

Authorization: Bearer sk_live_...

In Make, that header lives on HTTP — Make a Request (or an HTTP connection template). Missing or wrong keys return 401 with AUTHENTICATION_ERROR.

Hub: Make.com + Cryvis. Keys: Console → API keys. Docs overview: Documentation.

Create a key

1. Sign in to Cryvis and open API keys in Console.
2. Create a key; copy it immediately (shown once).
3. Store it in a password manager—not in a public scenario blueprint share.

Prefer separate keys for staging vs production Make organizations when you can.

Header on HTTP — Make a Request

Include the word Bearer and a single space. Do not wrap the key in quotes.

HTTP module
  Headers:
    Authorization: Bearer sk_live_...
  Body: multipart ...

Reuse without pasting the key twelve times

Options that scale:

1. Make data store / variable — store CRYVIS_API_KEY; map Bearer {{key}} in each HTTP module.
2. HTTP “Make an API Key Auth connection” (or custom auth connection) — if your Make plan/UI supports API key connections for HTTP, put the key there once and select the connection on each module.
3. Scenario input / team variable — for promotion across environments.

Avoid committing blueprints that embed live keys to git or public Make template galleries.

Rotation procedure

1. Create new key in Console
2. Update Make variable / connection with new key
3. Run one test extraction (invoice or custom)
4. Revoke old key in Console
5. Confirm scheduled scenarios still green

If you revoke first, every incomplete execution fails with 401 until Make is updated—prefer create → update → revoke.

Errors that look like auth but aren’t

Handle 402 separately from 401 in Slack alerts so finance tops up credits instead of rotating keys. Handle API errors.

Security notes

• Restrict Make organization access; HTTP modules expose headers to editors.
• Use Error Handler screenshots carefully—they can include Authorization values in logs.
• Do not put the key in the URL query string; Cryvis expects the header only.

Smoke test

curl -s https://api.cryvis.com/v1/custom-extractors \
  -H "Authorization: Bearer sk_live_..."

Or POST a tiny invoice image to /v1/documents/invoice. Same header Make will send. Full connection pattern: Connect REST API. Multipart after auth works: Send multipart form data.

Checklist

• Authorization header present
• Value starts with Bearer
• Key stored in one rotatable place
• 401 vs 402 alerts distinguished
• Old keys revoked after rotation

With auth centralized, cloning scenarios for Invoice, Receipt, or Custom is mostly URL and field-name changes.