Changelog

v2.6 - 2026-10-05

Added

• 2026-10-02 — Added optional job filters to API configuration payloads: job.contract_types_include, job.contract_types_exclude, job.work_time, and job.workplace_modes.
• 2026-10-02 — Added company.reverse_sourcing_min_probability, an integer between 0 and 100, defaulting to 70.
• 2026-10-02 — Added setting.launch_weekdays for daily exports (frequency=1).
  • Values range from Monday (0) to Sunday (6).
  • Omitted or null means all days.
• 2026-10-02 — Added configurable webhook headers through setting.webhook.header_name and header_value.
  • header_value is write-only: omit it to preserve the saved value; use null to remove the header.
  • Responses expose header_value_configured instead of the secret.
• 2026-09-30 — Added people.phone.fullenrich_api_key and the fullenrich phone strategy.
  • Added optional config_id to GET /people/{id}/reveal-phone to use a saved search’s Kaspr or FullEnrich key without consuming Mantiks credits.
• 2026-09-16 — Added ?force_update=true to GET /jobs/{id}/reverse-sourcing-agent to retry reverse sourcing.
• 2026-09-15 — Added optional code, details, and request_id fields to API error responses.
• 2026-09-14 — Added POST /searches/webhook/test to send a mocked export payload to the configured webhook.
• 2026-09-14 — Added icebreaker_settings.include_closing_salutation.
• 2026-09-12 — Added optional profile_picture_url to person responses and exported lead contacts.
• 2026-09-10 — Added synchronous batch endpoints:
  • POST /jobs/personas/batch
  • POST /jobs/best-fitting/batch
  • POST /jobs/reverse-sourcing-agent/batch
  • POST /people/reveal-email/batch
  • POST /people/reveal-phone/batch
  • Responses contain ordered results, with a status and response for each item.
• 2026-09-04 — Added action to reverse-sourcing responses: nothing_found, keep_current_company, or reassign_to_company.
• 2026-09-01 — Added optional icebreaker_settings for custom instructions, hiring questions, recruiter information, and candidate context.
• 2026-08-28 — Added optional job.cleaned_job_title and people.icebreaker_object to exported leads.
• 2026-08-03 — Added setting.launch_time and setting.launch_timezone for scheduled searches, and the contact generation seeded export state.
• 2026-06-22 — Added department support to location responses.
• 2026-06-19 — Added GET /credits/balance, returning the authenticated account’s remaining leads_credits.

Changed

• 2026-09-22 — job_url can now be null for jobs without an application URL.
• 2026-09-17 — Reduced synchronous batch limits from 25 to 10 items. Reverse-sourcing batches remain limited to 5 jobs.
• 2026-09-09 — Updated sector documentation and examples to use canonical identifiers, such as software and saas_cloud_services.

Fixed

• 2026-09-08 — Fixed credit charging for API v2 requests when optional backend arguments were omitted.

v2.5 - 2026-06-17

Added

• Added people.persona_id to lead responses from GET /exports/{id}/leads, identifying the matching persona.

v2.4 - 2026-06-15

Added

• Added reverse_companies to 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 probability and explanation.

v2.3 - 2026-06-04

Added

• Added config.setting.enable_icebreaker to API configuration payloads.
  • When enabled, Mantiks generates an explanation and icebreaker for each lead.
• Added config.company.enable_reverse_sourcing to 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-agent endpoint.
  • Starts reverse sourcing for a specific job.
  • Returns candidate companies with company_id, probability, and optional explanation.

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 persona
• all: include all matching personas

v2.1 - 2026-04-21

Changed

• Updated Search Config in the public API:
  • Renamed people.persona_id to people.personas_ids
  • Changed the field type from a single string to an array of persona IDs

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"]
  }
}