MGA Gambling Enforcement Notices & Changes

Collect factual observations from the Malta Gaming Authority enforcement register. Use the data to maintain a regulatory research feed, review changes in due-diligence workflows, or link historical notices to your own operator records.

Each run reads the complete register and returns one row per notice occurrence. Supply a previous complete snapshot to detect changes. A notice date is the date in its register heading: later updates inside the body can have different dates.

This Actor does not determine whether an operator is currently licensed, whether a notice remains legally effective, or whether a licence has been reinstated. An absent notice does not establish clearance. Check the linked regulator record for the legal context.

First run

{}

There is no API key, URL list, or licence filter to configure. The source is fixed to the official public MGA enforcement register. On September 10, 2026, the source contained 161 notice occurrences in 160 distinct date-title groups. Counts and availability can change.

Compare with an earlier observation

1. Run the Actor and check that OUTPUT.deliveryComplete and OUTPUT.sourceComplete are both true.
2. Download the complete SNAPSHOT JSON from that run's key-value store.
3. On the next run, paste that JSON into Previous SNAPSHOT JSON. For API input, use { previousSnapshot: JSON.stringify(snapshot) }.
4. Read COMPARISON together with the newly collected notice rows.

The prior snapshot must be complete, use this Actor's schema, fit within 4 MiB UTF-8, and finish before the new observation starts. It is validated for consistency; buyer-supplied JSON is not independently authenticated as a prior Actor run.

Output

The Dataset mixes factual rows (recordType=gambling_enforcement_notice) with unbilled diagnostics (recordType=diagnostic). Notice rows include:

Field	Meaning
noticeDate, noticeTitle	Date and title from the register heading
licenceReferences	MGA and legacy LGA references mentioned in the body, not verified operator licences
sourceUrl	Official register URL with the observed accordion anchor
sourceHtmlSha256, observedAt	Digest of the actual fetched HTML and UTC observation time
headingGroupId, sameHeadingOccurrences	Shared date-title group and its number of occurrences
id, anchor, sourceIndex	Identity and position within this observation; not stable regulator identifiers or chronology
bodyContentDigest	SHA-256 of whitespace-normalized visible body text; original prose is not exported
currentLicenceStatus	Always not_determined

SNAPSHOT contains the complete current rows, source verification, timing and a consistency digest. COMPARISON contains before/after occurrence facts grouped by date and title:

• newly_observed_heading: a heading was not present in the supplied previous snapshot.
• no_longer_observed_heading: a prior heading was not observed now.
• heading_group_content_changed: body digests, mentioned references or occurrence counts changed within the group.
• anchors_changed_content_unchanged: identical content was found at different observed anchors.

Duplicate headings remain separate occurrences. Comparisons use multisets, including duplicate counts, and do not arbitrarily pair originals with amendments. A title edit produces an unlinked absence and addition. Changes in whitespace alone do not change the body digest; page HTML may still change. The Actor does not explain the legal meaning of a text change.

Charges and completeness

The initial FREE-tier price is $0.001 per delivered notice occurrence, plus $0.005 per start. A 161-notice observation therefore requests $0.166 in Actor events at that tier. Check the Store pricing panel for the current price, your tier and any other platform charges.

Every current occurrence is charged, including unchanged notices and duplicate headings. Comparison has no separate event charge. Diagnostics request no result event; a platform start charge may still apply even when the source or input fails.

The Actor checks the effective run budget before collecting and before each paid row. If the remaining budget only covers part of the register, it stops with outcome=budget_stopped, retains the delivered rows and withholds the complete SNAPSHOT and COMPARISON. A successful platform status alone does not prove complete output: check OUTPUT.

Full artifacts are written only after all current notice events are confirmed. The row's billing.settlement=unconfirmed_at_write describes the moment of the Dataset write; confirm settlement using the run event counters and OUTPUT.confirmedResultEvents. If a write, charge or export response is uncertain, the Actor stops without retrying that operation. Some rows or exports may already exist, and late failures may leave OUTPUT absent. Inspect the existing run before launching another billed run. Automatic resurrection is unsupported.

Source limits

The fixed HTTPS fetch uses normal TLS verification and does not follow redirects. Responses are limited to 2 MiB and 25 seconds; parsing runs in a separate process with a 30-second limit. A missing notice body, malformed heading, empty register or more than 1,000 headings causes a source failure instead of a falsely complete snapshot. The complete snapshot is limited to 4 MiB and comparison exports to 9 MiB.

Source layout changes and temporary unavailability can interrupt collection. The observation verifies where the bytes came from; it does not audit the regulator's assertions, confirm current licence status, or establish a licence reference's relationship to an operator. For issue reports, include the run URL and diagnostic code; do not post credentials or private customer data.