Search companies with advanced filters
Search companies with advanced filtering options. Every key in include/exclude must be a recognized filter field (a static filter like id, companyGroup, or campaigns, or a company field id returned by the fields endpoint) — an unrecognized key returns a 400 listing the offending key(s) instead of being silently ignored.
Responses include direct Enginy app URLs when available. Each returned company includes an appUrl field. MCP agents should return those URLs to users whenever they are present in the response.
Required scope:
COMPANIES_READRate limit: 100 requests per minute
Authorizations
Body
Page number for pagination. Minimum value is 1.
x >= 1Number of items per page. Minimum is 1, maximum is 100.
1 <= x <= 100Search term for full-text search across company fields.
Filter conditions to include. Supports special filters like id, companyGroup, campaigns, leadsCount, isCompanyInCRM, and any company field ID returned by the fields endpoint. Filter values should match the field data type returned by GET /v1/companies/fields: text/select fields use arrays of exact values, numeric fields use two-item range arrays like ["10","100"], boolean fields use one-item arrays like [true], and timestamp fields use { "startDate": "...", "endDate": "..." }. Start with id, companyGroup (company list IDs), campaigns, leadsCount, isCompanyInCRM, and any workspace scoring fields such as icpScore or scoreBand when those field IDs appear in the fields response. Unrecognized keys are rejected with a 400 rather than silently ignored. Use GET /v1/companies/fields (MCP tool get_company_field_metadata) to discover valid company field names for fields, include, exclude, and update payloads.
Filter conditions to exclude. Same structure as include. Filter values should match the field data type returned by GET /v1/companies/fields: text/select fields use arrays of exact values, numeric fields use two-item range arrays like ["10","100"], boolean fields use one-item arrays like [true], and timestamp fields use { "startDate": "...", "endDate": "..." }. Start with id, companyGroup (company list IDs), campaigns, leadsCount, isCompanyInCRM, and any workspace scoring fields such as icpScore or scoreBand when those field IDs appear in the fields response. Unrecognized keys are rejected with a 400 rather than silently ignored. Use GET /v1/companies/fields (MCP tool get_company_field_metadata) to discover valid company field names for fields, include, exclude, and update payloads.
Specific company fields to include in the response (comma-separated or array). Use GET /v1/companies/fields (MCP tool get_company_field_metadata) to discover valid company field names.