Custom HTTP

Call your own HTTPS APIs from an enrichment column. Product label: HTTP request (Appenda mark, not the wordmark).

Overview

Custom HTTP is BYOK only (0 Appenda credits). You store an encrypted workspace API key, map table fields to request inputs, and project JSON response fields into the column.

The capability appears in the Enrichments catalog with a Connect action.

Connect a key

1. Open Enrichments or add HTTP request from a table.
2. Choose Connect and paste your provider API key.
3. Appenda stores the key for the selected workspace connection.

Appenda ops secrets (Infisical) are separate from workspace customer keys.

Configure a column

1. Pick method, URL template, and headers (HTTPS only; fail-closed).
2. Map required inputs from source fields — rows missing required values skip or error per field rules.
3. Map optional inputs — empty optional fields are omitted or sent null when allowed.
4. Choose which response JSON paths populate the column or nested result view.

Advanced auth and retry knobs stay minimal in v1.

Run and inspect

Runs follow the same Run a column scopes, approval ladder, Stop semantics, and Version control commit as catalog enrichments.

Open a cell for the result inspector: status chip, hierarchical JSON, copy actions.

Related

• Enrichments
• Run a column
• Trust model

FAQs