- Docs
- API reference
- Endpoints and schemas
- KYB API
- Use cases
Get negative news
Get recent negative news about each matched registered entity, in the POST response or through a background task you poll.
https://api.enigma.com/v2/kyb/?package=verify&attrs=negative_newsLook for recent news articles with negative sentiment about each registered
entity Enigma matches. Add negative news to a
Verify a business request,
on either package, or to an
attribute-only request:
like every use case, it is one POST /v2/kyb/ request, and add-ons combine.
Example
Section titled “Example”This request verifies Enigma Technologies and asks for negative news.
curl --request POST "https://api.enigma.com/v2/kyb/?package=verify&attrs=negative_news" \ --header "x-api-key: $ENIGMA_API_KEY" \ --header "Content-Type: application/json" \ --data '{ "name": "Enigma Technologies", "website": "https://enigma.com", "address": { "street_address1": "245 5th Ave", "city": "New York", "state": "NY", "postal_code": "10016" } }'The response, trimmed to the registered entity id and background_task, has
an id to poll and no results yet.
{ "data": { "registered_entities": [ { "id": "4dccd7a5-790c-c4d1-0000-108000000000" } ] }, "background_task": { "id": "f47ac10b-58cc-4372-a567-0e02b2c3d479", "status": "pending", "subtasks": [] }}Poll with that ID.
curl --request GET "https://api.enigma.com/v2/kyb/f47ac10b-58cc-4372-a567-0e02b2c3d479" \ --header "x-api-key: $ENIGMA_API_KEY"When status is complete, stop polling. The subtask’s legal_entity_id
matches the registered entity’s id, so the article is about that entity. The
article is illustrative.
{ "task_id": "f47ac10b-58cc-4372-a567-0e02b2c3d479", "status": "complete", "subtasks": [ { "media": { "legal_entity_id": "4dccd7a5-790c-c4d1-0000-108000000000", "status": "complete", "result": { "negative_news": [ { "url": "https://example.com/news/article", "title": "Example negative news headline", "sentiment": "negative", "sourceName": "Example News", "publishedDate": "2026-05-22" } ] } } } ]}Parameters
Section titled “Parameters”x-api-keyRequiredYour API key. Send it from your server only. See Authentication.
attrsRequirednegative_news, or the same value inproducts. Must be enabled for your account. Values are case-sensitive, and a misspelled one is ignored without an error. See Query parameters.
Negative news has no body field of its own. Enigma looks up news for the registered entities it matches, so send the inputs in Send strong identifiers. All body fields are in Request body, and the rules in Validation.
Response
Section titled “Response”The articles arrive in a top-level background_task object, not in data,
because they can take longer than the rest of the response. Results that are
ready when the POST returns are in the response, and you poll
GET /v2/kyb/{task_id} for the rest.
background_task.idThe task ID to pass to
GET /v2/kyb/{task_id}, ornullwhen there is nothing to poll. See Thebackground_taskobject.background_task.statuspending,completeorfailed. See Status values.background_task.subtasks[]The results that were ready when the POST returned, each in a
mediasubtask whoselegal_entity_idnames the registered entity. Can be empty. See Themediasubtask.
background_task is absent when no registered entity matched or the news
lookup failed for every matched entity. Negative news adds no task to
risk_summary.tasks, so there is no result to branch on.
Request behavior
Section titled “Request behavior”| Topic | Behavior |
|---|---|
| Where to request it | attrs=negative_news with either package, or products=negative_news in an attribute-only request. Both can return background_task. In an attribute-only request, each registered entity holds only its id, and with top_n=1, risk_summary.tasks is empty. |
Match count (top_n) |
Works at any top_n. Enigma looks up news for every registered entity in the response, so each one can get its own result. Other parts of the response change above 1; see When top_n is above 1. |
| Person-only screen | Not available. A person-only screen accepts only attrs=watchlist. |
| Timing | The POST waits for the news lookups to respond before it returns. Results that are not ready by then arrive through the background task. |
Poll for the rest
Section titled “Poll for the rest”- Read
background_taskin the POST response. Whenidis set, keep the subtasks and poll. See What the POST returns. - Call
GET /v2/kyb/{task_id}with thatid, and poll with backoff untilstatusiscomplete. The schedule and thefailedcase are in Poll for results. - Merge the complete subtasks from the POST with the subtasks from the final
GET, keyed by
legal_entity_id. See Combine POST and GET results. - Read each registered entity’s result. See Interpret the results.
Before you rely on it
Section titled “Before you rely on it”- A slower POST. The POST waits for the news lookups, and if a lookup runs past the request time limit, the whole POST can time out. See Timeouts.
- No guaranteed retention. No retention period is guaranteed for a background task. Poll soon after the POST, and store the results you need. See Poll for results.
- A missing result is not a clean result. A registered entity with no
complete subtask carrying its
idhas no negative news result, which is not the same as no negative news. See Interpret the results. - Account enablement. Negative news is an add-on; see Account enablement.
Related
Section titled “Related”- Negative news: the background task, subtask and article objects.
GET /v2/kyb/{task_id}: polling, status values and status codes.- Add-ons: every add-on attribute.