Skip to main content
POST
/
watchlists
/
{watchListId}
/
triggers
Add trigger to watchlist
curl --request POST \
  --url https://api.tic.io/watchlists/{watchListId}/triggers \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <api-key>' \
  --data '{
  "destination": "<string>",
  "destinationType": "webhook"
}'
{
  "teamWatchListTriggerId": 123,
  "destination": "<string>",
  "destinationType": "webhook",
  "hasBeenValidated": true,
  "lastMessageSentAtUtc": "2023-11-07T05:31:56Z",
  "lastUpdatedAtUtc": "2023-11-07T05:31:56Z"
}
On 2025-05-02 we made a change so creating triggers will monitor all available events and push them invidually. Earlier we required you to instruct which events you wanted to watch. This means that the webhook will contain a payload containing an array of events. Example of how the payload will look like:
Webhook post to your endpoint
[
  {
    "teamWatchListMemberEventId": 1,
    "teamWatchListMemberId": 9029,
    "teamWatchListId": 18,
    "externalId": "MY_NUMBER_1",
    "companyId": 12345678,
    "watchListMemberEventType": "companyAddress",
    "eventDate": "2024-02-02T10:49:24",
    "lastUpdatedAtUtc": "2025-05-02T11:30:09"
  },
  {
    "teamWatchListMemberEventId": 2,
    "teamWatchListMemberId": 9029,
    "teamWatchListId": 18,
    "externalId": "MY_NUMBER_2",
    "companyId": 12345678,
    "watchListMemberEventType": "companyRegistration",
    "eventDate": "2025-04-09T15:21:04",
    "lastUpdatedAtUtc": "2025-05-02T11:30:09"
  },
  {
    "teamWatchListMemberEventId": 3,
    "teamWatchListMemberId": 9029,
    "teamWatchListId": 18,
    "externalId": "MY_NUMBER_3",
    "companyId": 12345678,
    "watchListMemberEventType": "companyIntelligence",
    "eventDate": "2025-04-13T15:47:27",
    "lastUpdatedAtUtc": "2025-05-02T11:30:09"
  },
  {
    "teamWatchListMemberEventId": 4,
    "teamWatchListMemberId": 9029,
    "teamWatchListId": 18,
    "externalId": "MY_NUMBER_4",
    "companyId": 12345678,
    "watchListMemberEventType": "companyFinancialDocument",
    "eventDate": "2025-02-25T08:51:23",
    "lastUpdatedAtUtc": "2025-05-02T11:30:09"
  }
]

​
WatchListMemberEventTypes

The property watchListMemberEventType has the following valid types.
TypeDescription
companyAddressNew information surrounding one or multiple addresses
companyNameNew information surrounding names of the business
companyStatusNew information surrounding status of the business
companyRegistrationNew information surrounding registration of the business (VAT, payroll, tax etc)
companyIntelligenceNew information surrounding intelligence of the business
companyBeneficialOwnerNew information surrounding beneficial owners of the business
companyWorkplaceNew information surrounding one or multiple workplaces owned by the business
companyPersonNew information surrounding company representatives
companyRegisteredOfficeNew information surrounding the companys registered office
companyShareCapitalNew information surrounding the companys share capital
companyPurposeNew information surrounding the company purpose
companyDebtBalanceNew information surrounding changes of the debt balance
companyOrderToPayCaseNew information surrounding one or multiple order to pay cases
companyFinancialDocumentNew information surrounding financial documents such as annual reports
companyCaseNew information surrounding cases (inneliggande ärenden)
personAddressNew information surrounding person addresses
personNameNew information surrounding person name
personStatusNew information surrounding person status
personCompanyNew information surrounding the persons involvement as company representative

Authorizations

​
x-api-key
string
header
required

Path Parameters

​
watchListId
integer
required

The watchlist id

Body

application/json

The payload

​
destination
string
required
Minimum length: 1
​
destinationType
enum<string>
Available options:
webhook,
email,
sms

Response

Created

​
teamWatchListTriggerId
integer
​
destination
string | null
​
destinationType
enum<string>
Available options:
webhook,
email,
sms
​
hasBeenValidated
boolean
​
lastMessageSentAtUtc
string<date-time> | null
​
lastUpdatedAtUtc
string<date-time> | null