Key features​

• Monitor management: Endpoints for creating and retrieving monitors.
• Organisation monitoring: Endpoints for adding and querying monitored organisations.
• Change tracking: Endpoints for retrieving historical changes at both the organisation and monitor levels.
• Data models: Standardised request and response objects for all endpoints.

Monitor management​

Creating monitors​

At the core of Ongoing Monitoring is the monitor object, the main resource where you define properties that shape how the monitor will track changes to the data of organisations over time.

When creating a new monitor, you define parameters to control the following properties:

Example of request body to the Create monitor endpoint:

POST /info/monitor HTTP/1.1
Host: api.signicat.com
Content-Type: application/json
Authorization: Bearer <AUTH_TOKEN>
Content-Length: 228

{
    "name": "MyMonitor",
    "description": "Example of a Monitor with Trapets",
    "entityType": "Organisation",
    "sources": [
        {
            "name": "trapets"
        }
    ],
    "profiles": [
        "screening"
    ]
}

Retrieving monitors​

After creating a new monitor object, you can fetch the monitor details using the unique monitorId that you received in the initial response. To do this, you pass the monitorId in the URL to the Get monitor endpoint.

For example, let's assume the monitor ID is 01966198-6a9a-76b1-914f-5990e29f0de4.

Request example:

GET /info/monitor/01966198-6a9a-76b1-914f-5990e29f0de4 HTTP/1.1
Host: api.signicat.com
Accept: application/json
Authorization: Bearer <AUTH_TOKEN>

Response example:

{
    "id": "01966198-6a9a-76b1-914f-5990e29f0de4",
    "accountId": "<SIGNICAT_ACCOUNT_ID>",
    "name": "MyMonitor",
    "sources": [
        {
            "name": "trapets"
        }
    ],
    "profiles": [
        "screening"
    ],
    "description": "Example of a Monitor with Trapets",
    "size": 0,
    "entityType": "Organisation",
    "createdAt": "2025-04-18T07:41:40.882576Z",
    "isEnabled": true
}

Next to the defining properties of the monitor, the response contains the following additional fields:

• id: The unique identifier of the monitor object.
• accountId: The identifier of your account in the Signicat Dashboard.
• size: The number of entities (organisations or persons) linked to the monitor. For example, the number of organisations to monitor.
• createdAt: Creation timestamp of the monitor object.
• isEnabled: A boolean field to indicate if the monitor is active.

Organisation monitoring​

To start tracking changes to an organisation, you must add an organisation object, as an entity, to an existing monitor by sending a POST request to the Add organisation endpoint. You define the monitor ID in the URL /info/monitor/{{monitorId}}/organisations.

Request example:

POST /info/monitor/{{MONITOR_ID}}/organisations HTTP/1.1
Host: api.signicat.com
Content-Type: application/json
Authorization: Bearer <AUTH_TOKEN>
Content-Length: 186

[
  {
    "organisationNumber": "23432342",
    "source": "trapets",
    "country": "NOR",
    "companyName": "Signicat",
    "referenceKey": "402d1ce2-ce71-4f9b-b252-3fa90fef0de4"
  }
]

In the body of the request, you must define the following required parameters:

• organisationNumber: The company registration number.
• source: The data source to use when tracking changes to the organisation.
• country: Country code (ISO 3166-1 alpha-3).
• companyName: The name of the organisation to monitor.
• referenceKey: A time-sortable UUIDv7 string to uniquely identify the entity object. UUIDv7 offers a precise timestamp that you can use to filter changes.

Retrieving latest organisation data​

You can fetch the most recent snapshot of an organisation data by using monitorId and referenceKey.

Request example:

GET /info/monitor/{{MONITOR_ID}}/organisations/{{REFERENCE_KEY}} HTTP/1.1
Host: api.signicat.com
Accept: application/json
Authorization: Bearer <AUTH_TOKEN>

Response example:

{
  "country": "NOR",
  "name": "Organisation Name",
  "added": "2025-04-18T11:39:44.5169694Z",
  "lastUpdate": "2025-04-19T11:39:44.5169712Z",
  "organisationNumber": "12345678",
  "operationalStatus": null,
  "externalId": "1454-15",
  "alias": "Organisation Alias",
  "legalForm": "Other",
  "screening": {
    "matchStrength": 100,
    "listType": "SANCTION",
    "source": "EU_GLOBAL"
  }
}

The shape of the response varies depending on the profile you choose. For an overview of the properties, see the Get organisation endpoint.

Tracking changes​

A change refers to an observed change to a set of attributes of a monitored entity.

You can retrieve information about changes related to an individual entity within a monitor, or across all the entities for a given monitor.

Retrieve changes per organisation​

Retrieves all modifications for a given organisation (using monitorId and referenceKey). The endpoint returns information about the changed attributes, type of change and an overview of previous and new values.

Retrieve changes per monitor​

Retrieves all changes across organisations in a monitor (using monitorId).

To learn more, you can contact us by creating a support ticket in the Signicat Dashboard.