Can I read the feed for several countries at once?

No, country takes one code. Make one call per country, each with its own cursor.

How do I avoid reading the same event twice?

Keep the last next_cursor you processed for each country and start from it, or note the id of the events you stored and skip the ones you already have.

What if I need an event older than 31 days?

Search by company: company_number or company_name is not limited to the 31-day window. See the recipe for a Spanish company with its BORME events.

Is there a push version of this feed?

Yes. Put the companies you care about on monitoring and a signed webhook arrives when one of them has a corporate event, a status change or a sanctions match.

How do I get a country's corporate events day by day?

Call GET /company-events/search with country and no company: you get every event of that country, newest first, from date_from, and you page through with next_cursor. It costs 2 credits a call.

The call

The demo key does not include company events. The feed needs a key of your own with the company_events scope (Starter and above; a trial key has 25 calls on it).

curl 'https://api.prometiam.com/functions/v1/risk-api/company-events/search?country=GB&date_from=2026-11-07&limit=3' \
  -H 'Authorization: Bearer rk_live_...'

The answer

Fetched on 10 November 2026 with a real key. Two of the three events are shown, with the company names, numbers and ids left out:

{
  "data": [
    {
      "id": ...,
      "company_name": "...",
      "company_number": "...",
      "country": "GB",
      "source": "Companies House (UK)",
      "event_type": "other",
      "act_type": "GAZETTE",
      "signal": "other",
      "event_date": "2026-11-10",
      "event_detail": "gazette-notice-compulsory",
      ...
    },
    {
      "id": ...,
      "company_name": "...",
      "company_number": "...",
      "event_date": "2026-11-10",
      "event_detail": "gazette-dissolved-voluntary",
      ...
    },
    ...
  ],
  "pagination": { "count": 3, "has_more": true, "next_cursor": "2026-11-10_2000002167338" },
  "meta": {
    "search_mode": "country_feed",
    "feed_window": { "date_from": "2026-11-07", "date_to": null, "max_days": 31 },
    ...
  }
}

To read the next page, pass the cursor back unchanged and keep the other parameters:

curl 'https://api.prometiam.com/functions/v1/risk-api/company-events/search?country=GB&date_from=2026-11-07&limit=100&cursor=2026-11-10_2000002167338' \
  -H 'Authorization: Bearer rk_live_...'

How to read the answer

Field	What it tells you
`meta.search_mode`	`country_feed` when no company is given. A call with `company_number` or `company_name` is a company search instead.
`meta.feed_window`	The window actually applied: `date_from`, `date_to` and the 31-day maximum.
`event_type`, `act_type`, `signal`	What happened, in the register's own act code and as a normalised type and signal.
`event_date`	The date of the event. For gazette sources, the publication date; for register changes, the day the change first appears in the register data.
`pagination.next_cursor`	The cursor for the next page while `has_more` is true.

Narrow the feed with event_type (for example dissolution, insolvency, address_change) and date_to. A Norwegian call, country=NO, returns register-change events such as status:dissolved with previous_value active and new_value dissolved.

What it costs

Every call costs 2 credits, whatever limit is (1 to 100). A daily job that reads the last day with limit=100 costs 2 credits for each page it needs. Starter EUR 9.99 includes 1,000 credits a month, Professional EUR 29.99 10,000, Scale EUR 99.99 50,000. Errors are free.

Limits

The window is at most 31 days back. date_from defaults to 7 days ago. An older date is a 400.
Gazette events: Spain from the BORME, France from the BODACC, the United Kingdom from Companies House filings and The Gazette, Switzerland also from the commercial-register publications of the SHAB.
Register-change events (name, status, legal form, registered address; share capital in some countries): Ireland, Poland and Norway from 14 October 2026, most other live countries from their first load in September to November 2026. They are dated when the change first appears in the register data, not when the company acted, and they are not gazette notices.
Not every live country has events. The documentation lists the countries and the date each starts; nothing is served before it.

What can go wrong

400 validation_error for a date_from older than the window. Fetched on 10 November 2026 for date_from=2026-01-01: "Without company_name or company_number the event feed covers the last 31 days: date_from must be 2026-10-09 or later".
403 upgrade_required: no company_events scope, or the trial calls are used up.
429: rate limit or credits exhausted.

The free trial lasts 14 days and includes 500 credits. A card is required and nothing is charged during the trial; it then continues as Starter (EUR 9.99/month) unless you cancel.

Frequently asked questions

Can I read the feed for several countries at once?: No, country takes one code. Make one call per country, each with its own cursor.
How do I avoid reading the same event twice?: Keep the last next_cursor you processed for each country and start from it, or note the id of the events you stored and skip the ones you already have.
What if I need an event older than 31 days?: Search by company: company_number or company_name is not limited to the 31-day window. See the recipe for a Spanish company with its BORME events.
Is there a push version of this feed?: Yes. Put the companies you care about on monitoring and a signed webhook arrives when one of them has a corporate event, a status change or a sanctions match.