The Clay HTTP API is the most underused feature in the platform. Most RevOps teams stop at native integrations. When a data provider is not in Clay’s catalog, the Clay HTTP API connects any external HTTP endpoint as an enrichment column per row. The safety gap is real: no authentication headers, no payload validation, and no error handling creates a workflow that works in testing and fails silently in production.