Company Titles Launcher
List job titles associated with a company before choosing roles for a contact search.
output.titles; no polling is needed. Save input.task.job_id as a fallback if you need to retrieve this result later through Company Titles Finder.Use titles to plan a search
- Request the company’s available titles.
- Select the roles relevant to your workflow.
- Pass those titles in
title_liststo Search Contact. - Use Contact Enrichment for selected contacts when you need emails or phone numbers.
Example request
company_linkedin instead of domain.
Normalized or raw titles
By default, titles are trimmed, deduplicated, and sorted by title text. Useraw_titles: true to preserve duplicates and whitespace variants. Null and whitespace-only titles are excluded in both modes.
For stored titles "Engineer", "Engineer ", "Engineer", and "Manager":
Pagination and usage
Each page returns up to 50,000 titles. Ifoutput.has_more_pages is true, repeat the request with the same inputs and increment page_number. Valid page numbers run from 1 to 100.
When a company resolves and at least one active title is returned, the lookup is billed at the contracted Company Titles rate. Read output.usage for the job’s cost breakdown.Body
Company Titles request payload.
- Option 1
- Option 2
Request payload for Company Titles.
At least one of domain or company_linkedin must be provided.
When raw_titles is omitted or false, titles are stripped, deduplicated, and ordered ascending by title text. When raw_titles is true, every eligible title is returned exactly as stored, including exact duplicates and whitespace variants, ordered ascending by title text. NULL and whitespace-only titles are excluded in both modes. For stored values "Engineer", "Engineer ", "Engineer", and "Manager", default mode returns ["Engineer", "Manager"]; raw_titles: true returns ["Engineer", "Engineer", "Engineer ", "Manager"].
Optional custom key-value metadata echoed on job input and output (useful for correlating internal source metadata). On create requests, omit the field or send JSON null when no custom fields are needed; both are stored as {}. When present, the value must be a JSON object with keys matching ^[A-Za-z0-9_-]+$ and values that are a string (max 1000 characters), number, or boolean. Empty string, arrays, and other non-object types return HTTP 400. On job GET responses, input.task.custom_fields is always an object ({} or populated).
Response
Company Titles result returned successfully.
Company Titles response with job state, input, and optional output.