v2.4 - 2026-06-15
Added
- Added
reverse_companiesto export lead API responses.- Available on
GET /exports/{id}/leads. - Returned when reverse sourcing is enabled and candidate final-client companies are found.
- Each company includes standard company fields plus optional
probabilityandexplanation.
- Available on
v2.3 - 2026-06-04
Added
- Added
config.setting.enable_icebreakerto API configuration payloads.- When enabled, Mantiks generates an explanation and icebreaker for each lead.
- Added
config.company.enable_reverse_sourcingto API configuration payloads.- When enabled, Mantiks searches recruiting-sector job offers and tries to identify the final client.
- Added the
GET /jobs/{id}/reverse-sourcing-agentendpoint.- Starts reverse sourcing for a specific job.
- Returns candidate companies with
company_id,probability, and optionalexplanation.
v2.2 - 2026-04-28
Added people.persona_strategy to API configuration payloads.
API callers can now choose the persona matching behavior with the same values used internally by Mantiks:
best: keep the best matching personaall: include all matching personas
v2.1 - 2026-04-21
Changed
- Updated
Search Configin the public API:- Renamed
people.persona_idtopeople.personas_ids - Changed the field type from a single string to an array of persona IDs
- Renamed
Why
- This aligns the API config format with the existing model, where multiple personas can already be selected.
Migration
Before:
{
"people": {
"persona_id": "special-best-fitting"
}
}
After:
{
"people": {
"personas_ids": ["special-best-fitting"]
}
}
