POST /api/kharon/resources/search
Price: 5 credits
Search Kharon's resource library — customer stories, guides, reports, white papers, press releases, product notes and award announcements. Narrows by free-text query, content type and sector, and orders by publication date or title. Returns cards with the URL alias, address, title, abstract, publication date, reading time, the call-to-action label the card prints, cover image, tags and named authors.
This is Kharon's own marketing and product material, not its sanctions investigations — for those use /kharon/briefs/search. Pass a returned `alias` to /kharon/resources for the article body, which the cards do not carry. Values inside one filter are OR'd while `types` and `sectors` intersect. The library shares its sector vocabulary with /kharon/events/search but not with the Brief, whose tags are a separate set.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)search string nullable — Full-text query matched by the source across the resource library (examples: "sanctions", "screening", "forced labor"; minLength: 1)types array nullable — Content format; several values widen the result set to their union (one of: "article", "awards", "case_study", "company_update", "customer_story", "guide", "hosted_event", "industry_event", "partnerships", "press_release", "product_insights", "product_launch", "product_update", "regulatory_trends", "report", "use_cases", "webinar", "white_paper")sectors array nullable — Subject tags; several values widen the result set to their union (one of: "aml", "automotive", "banking", "compliance", "crypto", "defense_industrial_base", "evasion", "export_controls", "financial_crimes", "financial_services", "forced_labor", "investment_risk", "meu", "outbound_investments", "public_sector", "research_security", "sanctioned_securities", "sanctions", "summit", "supply_chain", "sustainability", "technology")sort string — Result ordering (default: "newest"; one of: "newest", "oldest", "alphabetical")count integer required — Max number of results to return (min: 1; max: 1000)@type string (default: "KharonResourceCard")id string nullablealias string nullableurl string nullablesummary string nullableread_time string nullabletemplate string nullablecta_label string nullablepublished_at string nullablecreated_at string nullableupdated_at string nullableevent_date string nullableimage object nullable@type string (default: "KharonAsset")id string nullableurl string nullablealt string nullablewidth integer nullableheight integer nullablemime_type string nullabletypes array (default: [])@type string (default: "KharonCategory")id string nullablealias string nullableduration string nullableimage object nullable@type string (default: "KharonAsset")id string nullableurl string nullablealt string nullablewidth integer nullableheight integer nullablemime_type string nullablesectors array (default: [])@type string (default: "KharonCategory")id string nullablealias string nullableduration string nullableimage object nullable@type string (default: "KharonAsset")id string nullableurl string nullablealt string nullablewidth integer nullableheight integer nullablemime_type string nullableauthors array (default: [])@type string (default: "KharonPerson")name string nullableurl string nullablerole string nullablebio string nullablelinkedin string nullabletwitter string nullableimage object nullable@type string (default: "KharonAsset")id string nullableurl string nullablealt string nullablewidth integer nullableheight integer nullablemime_type string nullablepositions array (default: [])@type string (default: "KharonPosition")company string nullablerole string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — No resource matched the query and filters Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.