The following show some example queries for the Strise GraphQL API. To experiment with queries, you can use the interactive query executor in the Strise GraphQL Playground.

Generate a token

All queries require the client to be authenticated, which is done by sending your clientId and clientSecret to the generateToken mutation. If you have not yet acquired your client credentials, please request one by sending us a message.

mutation generateToken {
  clientAccessTokenGenerate(
    clientId: "SECRET_ID"
    clientSecret: "SECRET_SECRET"
  ) {
    expires
    token
  }
}

After generating the token, pass it as a Header for subsequent requests:

{
 "Authorization": "Bearer <token>"
}

Search for a company

To make sure everything is configured correctly, a good place to start is to search for a company and see that you get some results.

Run the following to search for Strise AS by its Norwegian organisation number:

query search {
  companyIdentifierSearch(where: {identifiers: ["918330100"], country: "NO"}){
    edges {
      node {
        id,
        name
      }
    }
  }
}

Add a company to monitoring

To start receiving updates on a company it needs to be added to monitoring through the following mutation. You may notice that this mutation expects an entity id as input. As outlined in the description of the ID and in the previous section it can be obtained through search. Once the ID has been obtained the company can be added to monitoring by running the following mutation:

mutation monitorCompany {
  companyAddToMonitoring(
    where: { id: "123-abc-456-def" }
  ) {
    success
    company {
      name
    }
  }
}

API Changelog: 2025-09

This month's update introduces more structured data for adverse media events and clarifies date ranges for Politically Exposed Person (PEP) roles. We've added new fields to the AmsEvent and PepRole types and deprecated their older counterparts to provide a more robust and intuitive API experience. There are no breaking changes.

Adverse Media Screening

• Richer Data for Clustered Media Events The AmsEvent type now includes a clusteredEvents field, which returns a list of the new ClusteredEvent type. Each ClusteredEvent object contains an id and a url, providing a more structured way to access articles belonging to the same news cluster.

  The previous clusteredUrls field, which returned a simple list of URL strings, is now deprecated. Please update your integrations to use the new clusteredEvents field for more detailed information.

• New isCustom Field on AmsEvent A new boolean field, isCustom, has been added to the AmsEvent type. This field allows you to easily identify whether an adverse media event was added manually by a user or discovered automatically by our system.

Politically Exposed Persons (PEP)

• Clearer Date Ranges for PEP Roles To better represent the duration of a politically exposed person's role, we have added startDate and endDate fields to the PepRole type.

  The existing since field is now deprecated in favor of startDate. We recommend updating your queries to use these new, more explicit fields.

API Changelog: 2025-08

This month's update introduces a significant breaking change to how custom company shareholders are managed, splitting them into distinct fields for persons and companies. We've also added a new, more structured way to query for industry codes on companies and included external source URLs for PEP (Politically Exposed Person) data to improve traceability.

Breaking Changes

• New required shareholder fields for custom companies The customCompanyCreate and customCompanyUpdate mutations now require you to specify shareholders in two new distinct, non-nullable fields: personShareholders for individuals and companyShareholders for other companies. This change provides a clearer and more structured way to define the ownership of a custom company. Any integrations using these mutations must be updated to provide these new fields.

  Affected Mutations:

  • customCompanyCreate(where: CustomCompanyCreateInput!)
  • customCompanyUpdate(where: CustomCompanyUpdateInput!)

  New Required Fields:

  • personShareholders: [BusinessPersonOwnershipInput!]!
  • companyShareholders: [CompanyOwnershipInput!]!

Features

• Added structured industry codes for companies You can now query for detailed industry codes on the Company type using the new industriesV2 field. This field returns a list of ConnectIndustryCode objects, each containing the code, its description, and the codeType (e.g., SNI_2007, SIC_2007) from the new IndustryCodeType enum. This provides a more structured alternative to the existing industries field, which returns a simple list of strings.

• Added external source URLs for PEP data To improve data traceability, we've added a new externalUrls: [String!]! field to the PepHit and PepRelation types. This field provides a list of URLs pointing to the original sources for the Politically Exposed Person (PEP) information.

• Added clustered URLs to adverse media events The AmsEvent type now includes a clusteredUrls: [String!]! field. This returns a list of URLs for articles that have been identified as reporting on the same media event, helping you consolidate related news coverage.

API Changelog: 2025-07

This month's update introduces two major features. You can now create, update, and delete your own custom company and person entities directly via the API. We have also added a powerful new automated risk calculation feature for companies, providing a detailed breakdown of their computed risk level.

New Features

• Manage Custom Company and Person Entities You can now create, update, and delete custom company and person entities that are not available in public registries. This is useful for managing entities in jurisdictions we don't cover or for creating special-purpose entities. This functionality is supported by a set of new mutations and their corresponding input and payload types.

  • New mutations: customCompanyCreate, customCompanyUpdate, customCompanyDelete, customPersonCreate, customPersonEdit, customPersonDelete.
  • New supporting types: CustomCompanyCreateInput, CustomCompanyUpdateInput, CustomPersonCreateInput, CustomPersonEditInput, CustomCompanyPayload, CustomPersonPayload, ConnectPartialDateInput, LegalFormKind.

• Automated Risk Calculation for Companies The Company type now features a new automatedRiskLevel field. This field returns a RiskCalculationResult object containing the company's calculated risk level, total score, and a detailed breakdown of scores from various risk factors like country, industry, and PEP/sanction screenings.

  • New field: Company.automatedRiskLevel.
  • New supporting types: RiskCalculationResult, RiskScoreResult, CustomRiskFieldScore, RiskLevelSetting, RiskLevelKind.

Field Additions

• Added entityId to AmsEvent The AmsEvent type now includes an entityId field. This provides a direct reference to the ID of the company or person the adverse media event is associated with, simplifying data retrieval and linking events back to their source entity.

API Changelog: 2025-06

This month's update introduces enhancements to our Adverse Media Screening (AMS) capabilities. We've added a new field to the AmsEvent type to provide more detailed context about the topics detected in media articles, allowing for more precise analysis. These changes are non-breaking.

Adverse Media Screening

• Added topicMentions to AmsEvent for detailed topic analysis We've introduced the topicMentions field to the AmsEvent type. This field returns a list of the new AmsTopicMentions type, which groups specific text mentions from an article under their relevant topic. While the existing topics field provides a simple list of topic strings, topicMentions offers a structured way to see exactly which phrases in the text are associated with each identified topic, providing deeper context.

API Changelog: 2025-05

This month's update introduces a significant refactoring of how adverse media topics are represented, a new mutation for editing business person details, and an enhancement to sanction filtering. Please note the breaking change related to the AmsEvent type, which requires an update to any queries fetching topic data.

💥 Breaking Changes

• Refactored Adverse Media Topics from topicMentions to topics The field topicMentions and its associated type TopicMention have been removed from AmsEvent. This has been replaced by a simpler topics field that returns a list of strings. This change simplifies the data structure for easier consumption.

  Action Required: Any queries fetching topicMentions must be updated to use the new topics field.

  Before:

  query GetAmsEventTopics {
    company(where: {id: "..."}) {
      ams {
        topicMentions {
          text
        }
      }
    }
  }
  

  After:

  query GetAmsEventTopics {
    company(where: {id: "..."}) {
      ams {
        topics
      }
    }
  }
  

✨ New Features

• Added Mutation to Edit Business Persons A new editPerson mutation has been added, allowing you to modify the details of a BusinessPerson. This mutation uses the new BusinessPersonEditInput type to specify the person's ID and the fields to be updated (e.g., birthDate), and returns a BusinessPersonPayload.

• New Filtering Option for Sanctions The SanctionInfo.sanctions field now accepts an optional includeSuggestedFalse argument. When set to true, the query will also return sanctions that have been suggested as false matches but not yet confirmed. The default value is false, so existing integrations are not affected.

📈 Improvements & Fixes

• Clarified CountryCode Behavior The description for the CountryCode scalar has been updated to clarify that providing an empty string will be handled as a null value.

• Improved Field Descriptions Documentation for the ams field on BusinessPerson, Company, CustomBusinessPerson, and EntityLike has been standardized and improved for clarity.

API Changelog: 2025-04

This month's update introduces a major enhancement to our Adverse Media Screening (AMS) capabilities. You can now retrieve detailed information about media articles related to an entity, including sentiment analysis and named entity recognition. Additionally, we've improved our PEP screening data by adding aliases to PEP records. All changes are non-breaking.

Adverse Media Screening

• New ams field for detailed media screening results A new ams field has been added to the EntityLike interface, making it available on Company, BusinessPerson, and CustomBusinessPerson types. This field provides access to detailed adverse media articles and is intended to replace the existing amsCount field, which will be deprecated in a future release.

  The ams field returns a paginated list of AmsEvent objects. Each AmsEvent represents a single news article and contains rich data, including:

  • entityMentions: Specific mentions of people or companies within the text.
  • amsPredictions: Sentiment analysis results (e.g., NEGATIVE, NEUTRAL) with confidence scores.
  • topicMentions: Key topics discussed in the article.

  This change introduces several new supporting types: AmsEvent, AmsEntityMention, AmsPrediction, AmsClassificationKind, TopicMention, NamedEntityKind, TextSpan, and the ISODateTime scalar.

PEP Screening

• Added aliases to PEP records The PepHit type now includes a new aliases field. This field returns a list of alternative names associated with the Politically Exposed Person, improving the ability to confirm a match.

API Changelog: 2025-03

This month's update focuses on enriching the data available for Politically Exposed Person (PEP) screenings. We've introduced several new fields to the PepHit type to provide more comprehensive details on potential matches. Additionally, we've added support for custom sanction sources and improved the clarity of our documentation for the Review type.

New Features

• Enhanced PepHit Type for Richer PEP Data To provide more detailed information on Politically Exposed Person (PEP) matches, the PepHit type has been expanded with several new fields:

  • name: String: The full name of the matched person.
  • dateOfBirth: PartialDate!: The date of birth of the matched person. This uses the new PartialDate type, which can represent incomplete dates (e.g., just a year and month).
  • countries: [Country!]!: A list of countries associated with the person.

• New CUSTOM Sanction Source The SanctionSource enum now includes the CUSTOM value. This is used to identify sanctions that have been manually added by users within your organization, distinguishing them from official list sources like OFAC or the EU.

Improvements

• Improved Review Field Descriptions To improve clarity and provide better guidance, we've added detailed descriptions to the following fields on the Review type:
  • id: Now explicitly described as "The id of the review."
  • pdf: The description now clarifies that this field provides the review as a base64 encoded PDF and explains that it is generated asynchronously. As a result, the field may be null if the PDF is not yet ready.

API Changelog: 2025-02

This month's update includes one breaking change with the removal of the Subscription type. We've also introduced new fields to support sanction match verification and a new review trigger for risk level changes. Additionally, we have clarified the descriptions for several fields related to the PEP/RCA verification feature to make their behavior more explicit.

💥 Breaking Changes

• Removal of Subscription Type The root Subscription type has been removed from the API. Any operations that relied on this type are no longer supported and will result in a validation error. Please remove any usage of Subscription from your client integrations.

✨ New Features

• Verify Sanction Matches The Sanction type now includes a confirmedMatch: Boolean field. This field allows you to see a user's verification status for a specific sanction match. It will return true or false if verified, and null if the match has not yet been reviewed. Note that this field will only return data for users who have access to the sanction verification feature.

• New Review Trigger for Risk Level Changes A new enum value, RISK_LEVEL_VALUE, has been added to ReviewTriggerStatementKind. This allows you to identify review triggers that were initiated due to a change in an entity's risk level.

改善 Improvements

• Clarified Behavior for PEP/RCA Verification Fields The descriptions for several fields and arguments related to PEP/RCA data have been updated to clarify that their functionality is dependent on a user having access to the PEP/RCA verification feature. This makes the expected behavior more predictable for all users. The affected fields are:
  • PepHit.confirmedMatch
  • PepHit.custom
  • PepInfo.confirmedPepStatus
  • PepInfo.confirmedRcaStatus
  • The includeSuggestedFalse argument on PepInfo.hits

API Changelog: 2025-01

This month's update introduces a significant enhancement to how Politically Exposed Person (PEP) data is structured, providing more granular and verifiable information. We've also added more detailed fields for sanctions data and made other quality-of-life improvements across the API. While there are no breaking changes, we have deprecated several fields on PepInfo and encourage you to update your integrations.

Enhanced PEP & Sanction Details

• Richer PEP/RCA Data with PepHit Type We've refactored how PEP and RCA (Relatives and Close Associates) data is exposed to provide more detailed records. The PepInfo object now contains a hits field that returns a list of the new PepHit type. Each PepHit represents a distinct data source match for an individual, allowing you to see multiple PEP roles or RCA relationships separately.

  As part of this change, the roles and relations fields on PepInfo are now deprecated. Please update your integration to use the roles and relations fields inside each PepHit object instead.

  Additionally, PepInfo now includes confirmedPepStatus and confirmedRcaStatus fields to reflect any manual verification performed by users.

• Additional Sanction Information The Sanction type has been enriched with more contextual data. You can now retrieve the following new fields:

  • sanctionedSince: The date the sanction was applied.
  • program: The specific sanction program the entity is listed under.
  • sourceUrl: A direct URL to the sanction data from the source.

• PEP Role Start Date The PepRole type now includes a since field, which provides the date the person assumed that specific role.

General API Improvements

• Related Entities in Company Review Triggers The CompanyReviewTriggerEvent object now includes a relations field. This field returns a list of related entities that are relevant to the event, giving you more context about what caused the review to be triggered.

• More Flexible Private Person Search The country field in the PrivatePersonIdentifierSearchInput is no longer a required field. This allows you to search for a person by an official identifier without needing to specify their country.

API Changelog: 2024-12

This month's update enhances the information available for Politically Exposed Persons (PEPs). We've added a new field to provide more specific details about a PEP's role, allowing for more comprehensive screening. This change is non-breaking and adds new functionality without affecting existing queries.

Enhancements

• Added details field to PepRole A new details field of type String has been added to the PepRole object. This field provides further context about a person's role, supplementing the existing description. For example, while the description might be "Member of Parliament," the new details field could specify the constituency or term dates, offering more granular information for your compliance processes.

API Changelog: 2024-11

This month's update introduces a powerful new Risk Signals feature, allowing you to identify and understand potential risks associated with entities more effectively. We've also added several documentation improvements across the schema to enhance clarity and developer experience.

New Features

• Introducing Risk Signals We've added a new riskSignals field to the Company, BusinessPerson, PrivatePerson, CustomBusinessPerson types, and the EntityLike interface. This field provides structured information about potential risks associated with an entity. To support this, we've introduced several new types:
  • RiskSignals: The top-level object containing a list of RiskSignals.
  • RiskSignal: Represents a specific risk that has been identified.
  • RiskFactor: A specific data point that contributes to a RiskSignal, including information about when it occurred and the path to the risk.
  • PathConnection and PathConnectionEdge: New types used within RiskFactor to describe the path of relationships from the queried entity to the source of the risk.

Schema Improvements

• Added Descriptions for Clarity To improve developer experience and inline documentation, we've added descriptions to several existing types and input fields:
  • EntityConnection: Description added to clarify how it represents entity relationships.
  • PersonSearchInput.gender: Clarifies the purpose of the gender filter.
  • PrivatePersonIdentifierSearchInput.identifiers: Specifies that this field is for the identifiers being searched.
  • SizePageInfoInput.offset and SizePageInfoInput.size: Descriptions added to clarify their use in pagination.

API Changelog: 2024-10

There were no changes to the GraphQL API in October 2024.

API Changelog: 2024-09

This month's update introduces significant enhancements to our Politically Exposed Person (PEP) and Sanctions data, providing more detailed and structured information. We've also added a new query to retrieve review reports. As part of these changes, several boolean fields have been deprecated in favor of richer object types, and the privatePersonUpdate mutation has been made more flexible.

New Features

• Enhanced PEP and Sanctions Information We've replaced the simple pep and sanctioned boolean fields with new, more detailed object types: pepInfo and sanctionInfo. These new fields provide structured data, such as the specific sanctions an entity is listed on, the sanctioning body, and the specific roles that qualify a person as a PEP. This change affects the BusinessPerson, Company, CustomBusinessPerson, and PrivatePerson types.

  The following new types have been added to support this feature:

  • PepInfo, PepRole, PepRelation
  • SanctionInfo, Sanction, SanctionSource

• New Query for Retrieving Reviews You can now fetch a completed review directly using the new review root query field. This query accepts a review ID and returns the Review object, which includes a pdf field containing the Base64 encoded review report. A new Base64EncodedFile scalar has been added for this purpose.

Deprecations

• Deprecated pep and sanctioned Fields The pep and sanctioned boolean fields on BusinessPerson, Company, CustomBusinessPerson, PrivatePerson, and the EntityLike interface are now deprecated. Please update your integrations to use the new pepInfo and sanctionInfo fields to access richer data and ensure future compatibility.
  • Use pepInfo instead of pep.
  • Use sanctionInfo instead of sanctioned.

Improvements

• More Flexible privatePersonUpdate Mutation The privatePersonUpdate mutation is now more flexible. The name, nin, country, and address fields in the PrivatePersonUpdateInput are no longer required. This allows you to perform partial updates on a PrivatePerson without resubmitting all of their existing details.

• Clarified amsCount Description The description for the amsCount field on BusinessPerson, Company, CustomBusinessPerson, PrivatePerson, and EntityLike has been updated to clarify that the count is an approximation. The new description is: "This is an approximation and the actual number may be lower, but never higher."