Companies
This guide covers common workflows for managing companies in Strise Connect: looking up companies, adding them to monitoring, and handling alerts.
Look up a company
Use companyIdentifierSearch to find a company by its national identifier (for example, an organisation number):
query CompanyIdentifierSearch {
companyIdentifierSearch(where: { identifiers: ["918330100"], country: "NO" }) {
edges {
node {
id
name
}
}
}
}The returned id is used in all subsequent operations for
that company.
If the company isn't found in a public registry, you can create one manually using the customCompanyCreate mutation.
Add a company to monitoring
To start receiving alerts on a company, add it to monitoring
using the
companyAddToMonitoring mutation.
The id is the Strise entity ID obtained from search:
mutation MonitorCompany {
companyAddToMonitoring(where: { id: "<company_id>" }) {
success
company {
name
}
}
}Fetch monitoring alerts
After a company is monitored, you can query for alerts using the alerts query. Alerts are triggered when changes are detected, such as new PEP or sanction hits:
query GetAlerts {
alerts(where: { first: 10 }) {
edges {
node {
id
alertKind
createdAt
state
}
monitoredEntity {
... on Company {
id
name
}
}
}
pageInfo {
hasNextPage
endCursor
}
}
}You can filter alerts by entity kind to only retrieve alerts for companies or private persons:
query GetCompanyAlerts {
alerts(where: { first: 10, entityKind: COMPANY }) {
edges {
node {
id
alertKind
state
}
}
}
}Resolve alerts
Use the alertUpdate mutation to mark alerts as resolved or unresolved:
mutation ResolveAlerts {
alertUpdate(where: {
ids: ["<alert_id_1>", "<alert_id_2>"],
state: RESOLVED
}) {
success
}
}Generate sandbox alerts
In sandbox environments, use sandboxAlertGenerate to create test alerts for validating your alert-handling logic:
mutation GenerateTestAlert {
sandboxAlertGenerate(where: {
entityId: "<company_id>",
alertKind: SANCTION,
action: ADD
}) {
success
}
}