Subtype Filtering on Enrich: Get Only the Signals You Want, Pay Only for What Returns

Shipped August 27, 2026.

signal_subtypes filtering - previously search-only - now works on both enrich endpoints: POST /v1/companies/enrich and POST /v1/contacts/enrich. Ask for a company's full signal profile and keep only the subtypes you care about, server-side.

Because enrich bills 2 credits per returned signal, the filter directly reduces your spend: fewer signals returned, fewer credits charged. A filter that matches nothing is free - you get a 200 with an empty array and response metadata (never a 404, as long as the entity itself resolves).

Example

Only the AI-investment content tags from Salesforce's recent SEC filings:

POST /v1/companies/enrich
{
  "domain": "salesforce.com",
  "signal_types": ["sec-8k", "sec-10k"],
  "signal_subtypes": ["aiInvestment"],
  "limit": 50
}

Semantics (identical to search)

• OR within the array - a signal matching any value passes. Max 25 values.
• Cross-type - one list applies across all requested signal_types; SEC filing types share content-tag subtypes, so the example above covers both filing types with one filter.
• Case-insensitive against the known vocabulary (hiringsalesroles matches hiringSalesRoles).
• Unknown values never error - they fall back to exact match (typically 0 results) and add a warnings entry with a pointer to the vocabulary. One bad value won't break a batch job.
• The singular signal_subtype is still accepted and unioned with the array.
• Discover valid values per type via the free GET /v1/signals/types (the subtypes map).

Unlike search, there is no 14-day window cap on enrich - single-entity lookups scan the entity's full history.

Also in this release

• MCP: enrichCompany and enrichContact on the Autobound MCP server accept the same parameters. Reconnect your MCP client to pick up the new tool schemas.
• New guide: Subtype Filtering - discovery, semantics, and billing impact across all four entity endpoints, with copy-paste examples.
• Endpoint Reference updated with the new parameters (and the enrich limit default corrected in the docs: it's 20, not 50).
• OpenAPI spec bumped to 2.4.0.

Questions? [email protected]