Skip to main content
GET
Get Columns

Credits and plans

PAYG is Pay-as-you-go. AYCE is All-you-can-eat.

When to use Columns

Discover supported fields before writing a filter or choosing output columns. This catalog covers person, job, and company fields available on contact records. Use Company Columns for company-only requests.

Example

Set REVENUEBASE_API_KEY to your API key.
Response excerpt captured from the local test API on October 13, 2026. One catalog entry is shown; the actual response includes the other fields.

Read the catalog

The example is an excerpt; the actual catalog contains additional fields. sourceType describes the source field type. snowflakeType is a legacy alias of the same value.

Fetch picker values in one request

Without include=values, the request returns field metadata. Add include=values to warm all available filter pickers in one call instead of making a separate request for every field. Cache the catalog in your application and refresh it periodically. X-Cache reports a cache hit or miss when present. Open-ended text, such as job titles and company names, is searched rather than enumerated. For one bounded vocabulary, use Column Values.

Limits and next steps

Contact and company routes share the default 10 requests per second per user. Wait for the reset time or Retry-After when rate limited; coordinate requests across your workers and API keys. Build a search filter from the returned fields, then Count the audience.

Authorizations

X-Key
string
header
required

Query Parameters

include
string | null

Set values to embed available picker vocabularies in one catalog request.

Response

Successful Response

The response is of type Response Get Columns V1 Columns Get · object.