Skip to main content

​
Overview

Clay’s HTTP API enrichment lets you call any REST API and map the response into your table. This guide walks through connecting any MoltSets tool to Clay.

​
Prerequisites

  • A MoltSets API key — see Authentication for how to create one
  • A Clay table with a column containing the input data your chosen tool requires

​
Setup

​
1. Add an HTTP API enrichment column

In your Clay table, click + Add column and select HTTP API.

​
2. Configure the request

Set the following fields in the HTTP API configuration panel: Method
Endpoint Enter the endpoint URL for the MoltSets tool you want to use. Find the correct URL on the tool’s API reference page. Not sure which tool you need? See I Have X, I Want Y. Headers Replace YOUR_API_KEY with your MoltSets API key. User-Agent is required on every request — MoltSets accepts any non-empty value, so Clay (or any label you prefer) works; requests without it are rejected with 403 Forbidden. Body Enter the request body as shown in the tool’s API reference page. For any fields that should pull from a Clay column, use Clay’s / shortcut to insert a column reference in place of the value.

​
3. Configure the response

In the Response values to return field, enter:
This captures the entire results object from the MoltSets response into the HTTP API column.

​
4. Extract values into their own columns

Add a separate column for each value you want to extract from the response:
  1. Click + Add column and select Formula
  2. Use / to reference the HTTP API column
  3. Select the field you want from the field picker (e.g. results.email)
Repeat for each field you need.
Clay’s HTTP API path traversal stops at one level deep, so entering results.email directly in the Response values to return field will not drill into the nested object. The two-column approach above is the expected workflow.

​
Handling no results

When MoltSets finds no data for a given input, the call still succeeds: HTTP 200, with status set to "not_found" and the fields in results empty or null. No tokens are charged. In Clay, that means the row is not an error row — the HTTP API column fills in with a body like this:
Add a formula column on status if you want to split hits from misses — for example, only run a follow-up enrichment where status is "ok". Filtering on the HTTP status code will not separate them, because both outcomes return 200.
This changed. MoltSets used to return 404 when a lookup found nothing. Tables built to treat a 404 as “no data” should now read status instead. The only 404 left is an unknown or retired tool name in the URL.