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
      }
    }
  }
}

API Changelog: 2025-12-19

This release includes a documentation improvement to clarify the behavior of the country filter when searching for persons. There are no breaking changes.

Improvements

• Clarified behavior of PersonSearchInput.country The country field on the PersonSearchInput object now includes a description. This clarifies that the filter will be ignored if a developer provides a country code for a registry that is not supported by the API. This helps explain search results that might otherwise seem unexpected.

API Changelog: 2025-12-19

We've updated our API to support the new SNI 2025 industry classification standard. This is a non-breaking change that enhances our company data capabilities.

Improvements

• Added SNI_2025 to IndustryCodeType A new enum value, SNI_2025, has been added to the IndustryCodeType enum. This represents the upcoming Swedish Standard Industrial Classification for 2025. You may encounter this value in the codeType field when querying for company industry information via the Company.industriesV2 field. As this is a non-breaking addition, existing integrations will not be affected, but we recommend updating clients to recognize this new value.

API Changelog: 2025-12-17

This update introduces a more robust and detailed way to handle entity addresses. We have added a new addresses field to all entity types, which provides a comprehensive list of addresses, each categorized by its type (e.g., postal, registered). The previous address field is now deprecated in favor of this new, more structured approach.

Improvements

• Enhanced Address Information To provide more comprehensive and structured address data, we have introduced a new addresses field on Company, BusinessPerson, CustomBusinessPerson, and the EntityLike interface.

  This new field returns a list of all available addresses for an entity. To help distinguish between them, we've also added:

  • A new addressKind field to the Address type.
  • A new AddressKind enum with possible values: POSTAL, REGISTERED, TRADING, and VISITING.

  The existing address field is now deprecated and will be removed in a future version. We recommend updating your integrations to use the new addresses field to access this richer data and ensure future compatibility.

API Changelog: 2025-12-17

This update introduces enhancements to the EntityIdentifier type by adding a description field as well as a new UNKNOWN enum value to EntityIdentifierKind.

New Features

• Added UNKNOWN emum value to EntityIdentifierKind. When the identifier cannot be determined to be of type PRIMARY or SECONDARY the identifier kind will be UNKNOWN.

• Added description field on type EntityIdentifier. The description field provides additional details on the type of identifier.

API Changelog: 2025-12-16

This update introduces significant enhancements to our monitoring and alerts capabilities, providing more specific types and new filtering options. We've also improved the usability of adverse media screening fields. This release includes several breaking changes related to the alerts feature that require developer attention. The alert queries are still subject to change and breaking changes should still be expected.

Breaking Changes

• Argument type for Query.alertData has changed. The alert argument on the Query.alertData field now accepts a value of type AlertId! instead of ID!. The new AlertId scalar provides a more specific identifier for alerts, improving type safety. You must update your queries to use this new type.

• Type of monitoredEntity fields changed to MonitoredEntityLike. The monitoredEntity field on the AlertConnectionEdge and MonitoringChange types has been updated from EntityLike! to the new, more specific MonitoredEntityLike! interface. This change ensures that only entities that can be monitored are returned in this context.

New Features & Enhancements

• Introduced MonitoredEntityLike interface for better type safety. We've added a new interface, MonitoredEntityLike, to specifically represent entities that can be monitored. The Company and PrivatePerson types now implement this interface, distinguishing them from other entities in monitoring-related queries.

• Filter alerts by entity kind. The alerts query now accepts a new entityKind argument within the AlertsWhereInput object. You can use this to filter alerts for a specific type of entity, such as COMPANY or PRIVATE_PERSON, using the new EntityKind enum.

• Improved pagination for ams fields. The pageInfo argument on PrivatePerson.ams (and other fields implementing EntityLike or MonitoredEntityLike) is now optional and includes a default value of { size: 20, offset: 0 }. This simplifies querying for the first page of adverse media events as the argument is no longer required. We've also added more detailed descriptions to the field and its arguments to clarify its usage.

API Changelog: 2025-12-10

This update introduces two non-breaking changes to improve data modeling. We've added a new field to the Company type to identify reference-only records and a new status to the DocumentStatus enum for better tracking of document uploads.

Features

• New isReferenceOnly field on Company A new boolean field, isReferenceOnly, has been added to the Company type. This field will be true for company records that are created as a reference from another entity's relationship data (e.g., a shareholder from an unsupported country). These reference-only companies exist to complete the graph but have limited data available. You can use this flag to identify and handle these partial records appropriately in your application.

• New IN_PROGRESS status for DocumentStatus The DocumentStatus enum now includes the value IN_PROGRESS. This new status indicates that a document upload has been initiated and is currently in the process of being uploaded. This provides more granular tracking between the PENDING and SUCCESS/FAILED states.

API Changelog: 2025-12-09

This update introduces a new mutation for creating private persons, providing more control over the data enrichment process. As this is a non-breaking change, all existing integrations will continue to work without modification.

New Features

• New privatePersonCreateNoEnrich mutation A new mutation, privatePersonCreateNoEnrich, has been added to create a private person entity. Unlike the existing privatePersonCreate mutation, this new field does not automatically enrich the created person with data from external registries. It creates the person record using only the data you provide in the PrivatePersonCreateInput. This is useful when you have already verified the person's details, for example, by using the privatePersonRegistrySearch query, and want to create an entity with that exact data.

API Changelog: 2025-12-08

Improvements to the privatePersonSearch query

• Added a new hasNin field to the PersonSearchInput query input that can be used to filter private persons that does or does not have a nin (national identification number).
• Added pagination information in the search response, PageInfo, making it easier for the client to go through all the pages matching the query.
• Order results by name ascending

API Changelog: 2025-12-05

This update introduces a new query, privatePersonRegistrySearch, allowing you to look up private individuals directly in official national registries. This provides a way to find and verify person data using a combination of identifiers before creating them in Strise.

New Features

• New privatePersonRegistrySearch query

  The query uses the new PersonRegistrySearchInput type, which requires name and country, and accepts optional fields like nin (national identifier number), birthDate, and address details to refine the search. You must provide Name combined with one of the following: National ID Number, Birth Date, or an Address (requires Street Name with either Zip Code or House Number) to get a result.

  A successful search returns a ConnectPrivatePersonRegistrySearchResource object containing the person's details from the registry, such as their name, birth date, address, and official identifier.

  Example Query:

  query FindPersonInRegistry {
    privatePersonRegistrySearch(
      where: {
        name: "John Doe",
        country: "NO",
        birthDate: "1990-01-15"
      }
    ) {
      name
      birthDate
      address {
        addressLine
        city
        zipCode
      }
      identifier {
        value
        kind
      }
    }
  }
  

API Changelog: 2025-11-28

This update expands our Adverse Media Screening (AMS) capabilities by incorporating a new data source. This change is non-breaking, but you may want to update your client to handle the new event kind.

Additions

• New Adverse Media Source: Dow Jones The AmsEventKind enum, which specifies the origin of an adverse media event, now includes the value DOW_JONES. When querying for adverse media via the ams field on an entity, you may now receive AmsEvent objects where the eventKind field is DOW_JONES.

API Changelog: 2025-11-27

Listing tags is now available for companies and private persons

New Features

• Added tags field to Company and PrivatePerson types. This enables you to query for a list of tags added to these resources

API Changelog: 2025-11-05

New Features

• Added shareholders and holdings fields to Company, and holdings to BusinessPerson New fields to retrieve shareholder and holding information for companies have been added. These fields return lists of Ownership objects, providing details about the direct shareholders and holdings of a company.

  In each Ownership object, you can find:

  • entity: The Company or BusinessPerson that is the shareholder, or Company that is being held.
  • totalSharePercentage: The total direct share percentage held by/in the entity.
  • shareClasses: A list that contains information about the share class and the share percentage held.
  • editMetadata: Metadata about potential edits that have been done to the item.

• Added beneficialOwners field to Company, and beneficialOwnerships field to BusinessPerson These fields contain information about a company's beneficial owners and a business person's beneficial ownerships, respectively. They return lists of BeneficialOwnership objects, which include:

  • entity: The Company or BusinessPerson that is the beneficial owner/owned entity.
  • reasons: A list of reason enum values explaining why the entity is considered a beneficial owner.
  • editMetadata: Metadata about potential edits that have been done to the item.

For all these fields, you can use the ignoreEdits parameter to see the original, unedited data.

API Changelog: 2025-11-03

We've introduced a new way to retrieve information about corporate roles. You can now query for the roles held by a specific BusinessPerson or see all the roles associated with a Company. This is a non-breaking feature addition.

New Features

• Added roles field to Company and BusinessPerson types A new roles field is now available on the Company and BusinessPerson types. This enables you to query for corporate role information, such as finding the CEO of a company or listing a person's board positions.

  This change introduces two new types: Role and RolePeriod.

  • The roles field returns a list of Role objects. Each Role includes the roleTitle, an isActive flag, the associated entity (the person or company), and a period object.
  • The RolePeriod object specifies the from and to dates for the role's tenure.
  • You can use the includePrevious: true argument to fetch historical roles in addition to current ones.

API Changelog: 2025-10-29

This update introduces a new capability to send customer-facing forms directly via the API. You can now trigger a form to be sent to a specific recipient's email and associate it with a company in your system. This is useful for processes like customer onboarding or information gathering.

Features

• Added ability to send customer-facing forms A new sendForm mutation is now available. It allows you to programmatically send a predefined customer-facing form to an email recipient.

  To use this mutation, provide the companyId, the formId of the form you wish to send, and the recipient's details in the SendFormInput. Upon success, the API will return a SendFormPayload containing success: true and the unique formInstanceId for the form that was sent.

  This change introduces the following new types and fields:

  • Mutation: sendForm(where: SendFormInput!): SendFormPayload!
  • Input Type: SendFormInput, which requires companyId, formId, recipientEmail, and recipientName.
  • Payload Type: SendFormPayload, which returns a success boolean and the new formInstanceId.
  • Scalar IDs: CustomerFacingFormId to identify the form template, and FormInstanceId to identify the specific instance that was sent.

API Changelog: 2025-10-21

This update introduces a more structured way to access company industry codes. We have deprecated the industries field on the Company type and replaced it with the new industriesV2 field. This is a non-breaking change, but we encourage all developers to migrate to the new field to take advantage of the richer data.

Improvements

• Company.industries field deprecated in favor of industriesV2 The industries field on the Company type is now deprecated and will be removed in a future API version. This field returned a simple list of strings representing industry codes.

  To provide more detailed information, we have introduced the new industriesV2 field. This field returns a list of ConnectIndustryCode objects, each containing the industry code, its description, and the codeType (e.g., NACE, SIC).

  We recommend updating your queries to use industriesV2 to access this more structured and informative data.

API Changelog: 2025-10-16

This update improves how you access Adverse Media Screening (AMS) data. We are deprecating the amsCount field on all relevant entities and introducing a more powerful ams field. This change allows you to retrieve detailed information about media events instead of just an approximate total count. This is a non-breaking change, but we encourage you to migrate to the new field.

Adverse Media Screening

• Deprecated amsCount in favor of new ams field The amsCount integer field is now deprecated on the EntityLike interface and its implementing types: Company, BusinessPerson, and CustomBusinessPerson. It will be removed in a future release.

  We have introduced a new ams field which returns a paginated list of AmsEvent objects. This provides rich details for each adverse media article, such as the title, summary, publisher, and publication date. The new field provides more accurate and detailed results.

  Please note that the number returned by the deprecated amsCount may differ from the number of events returned by the new ams field due to improvements in our screening and event clustering logic.

  Action Required: Please update your integrations to use the ams field to fetch detailed adverse media events.

  # DEPRECATED
              query GetAmsCount($id: CompanyId!) {
                company(where: {id: $id}) {
                  amsCount
                }
              }
              
              # RECOMMENDED
              query GetAmsEvents($id: CompanyId!) {
                company(where: {id: $id}) {
                  # Query for the list of events
                  ams(pageInfo: {size: 10, offset: 0}) {
                    id
                    title
                    published
                    summary
                  }
                }
              }
              

API Changelog: 2025-10-14

This update expands our data coverage by introducing new legal form types for companies registered in Finland. This is a non-breaking change that allows for more precise classification of Finnish entities.

Improvements

• Added new legal forms for Finland We have added 21 new values to the LegalFormKind enum to support a wider range of company legal forms in Finland. This change enhances our data coverage for Finnish entities, enabling more accurate classification when using the customCompanyCreate and customCompanyUpdate mutations.

  While this is a non-breaking change, we recommend updating any client-side logic that handles LegalFormKind to recognize these new values.

  The new values added are:

  • FI_ASH: Resident-administered area
  • FI_ASY: Right-of-occupancy associationy
  • FI_AYH: Non-profit association
  • FI_ETS: Finnish branch of a European economic interest grouping
  • FI_HY: Mortgage Society
  • FI_KOY: Limited liability joint-stock property company
  • FI_KVJ: Public mutual insurance company
  • FI_OP: Co-operative bank
  • FI_OSK: Housing co-perative
  • FI_OYJ: Public Limited Company
  • FI_SCE: European co-operative society
  • FI_SCP: European co-operative bank
  • FI_SE: European Company
  • FI_SL: Branch of a foreign trader
  • FI_SP: Savings bank
  • FI_TYH: Association for carrying on economic activity
  • FI_UNKNOWN: Unknown
  • FI_VALTLL: State-owned company
  • FI_VOJ: Public limited insurance company
  • FI_VOY: Limited insurance company
  • FI_VY: Insurance association

API Changelog: 2025-10-02

This update introduces new fields to the Company type, providing more detailed information on a company's operational status and employee count. These additions are non-breaking.

New Features

• Added company status and employee count information We've enriched the Company type with two new fields to provide more context about a business:
  • The new status field returns a ConnectCompanyStatus object, which describes the company's operational status (e.g., "Active", "Dissolved"), the date the status was set, and an isActive boolean flag.
  • The new numberOfEmployees field returns an EmployeeCountInterval object. This provides a from and to integer value, representing the employee count as a range.

API Changelog: 2025-09-29

This update expands our support for German company data by introducing a new legal form. This is a non-breaking change.

Enhancements

• Added new legal form for German entities We have added a new value, DE_RV, to the LegalFormKind enum. This value represents a "State-conferred Association" (Rechtsfähiger Verein), a type of legal entity in Germany. This change improves our data coverage for German companies.

API Changelog: 2025-09-25

This update introduces enhancements to our review functionality, making it easier to track and retrieve reviews. You can now fetch all reviews for a specific company and see exactly when a review was created. Additionally, it introduces a new way to classify entity identifiers, allowing you to distinguish between primary and secondary identifiers for companies and people. This provides more context and helps in programmatically selecting the most relevant identifier for an entity. There are no breaking changes in this release.

Enhancements

• Retrieve reviews for a company A new reviews field has been added to the Company type. This allows you to directly query all reviews that have been created for a specific company, returning a list of Review objects.

• Added creation timestamp to reviews The Review type now includes a createdAt field. This field provides a DateTime timestamp for when the review was generated, which is useful for auditing and sorting purposes.

• Added kind to EntityIdentifier to classify identifiers We've added a new kind field to the EntityIdentifier type. This field helps categorize an entity's identifiers, making it easier to determine their purpose. The kind field is non-nullable and returns a value from the new EntityIdentifierKind enum:

  • PRIMARY: A primary, official identifier for the entity (e.g., a national organization number).
  • SECONDARY: A secondary identifier for the entity.

  You can now use this field to reliably select the primary identifier for an entity instead of relying on heuristics.

  Example Query:

  query GetCompanyIdentifiers($id: CompanyId!) {
    company(where: { id: $id }) {
      name
      identifiers {
        value
        country
        kind # New field
      }
    }
  }
  

API Changelog: 2025-09-24

This update introduces a significant new feature for visualizing and analyzing company ownership structures. You can now query the new shareholderGraph field on the Company type to retrieve a graph of its owners, including indirect ownership and beneficial owner information. This is a non-breaking change.

Features

• Introduced Shareholder Graph for Company Ownership A new shareholderGraph field has been added to the Company type, allowing you to traverse and analyze complex ownership structures.

  The field returns a ShareholderGraph object, which consists of nodes (the entities) and edges (the ownership links).

  • Nodes (ShareholderGraphNode): Represent companies or individuals in the ownership chain. Each node includes the entity's details, their calculated indirectSharePercentage in the root company, and whether they qualify as a isBeneficialOwner.
  • Edges (ShareholderGraphEdge): Represent the direct ownership percentage between two nodes in the graph.
  • To accommodate data from various sources where ownership is expressed as a range (e.g., 25-50%), ownership percentages are now represented by the SharePercentageInterval type, which provides from and to values.
  • You can control the granularity of the graph by using the minimumSharePercentage argument on the shareholderGraph field to filter out smaller shareholders. Refer to the documentation on this parameter to learn more about how it works. Example query:

  query CompanyOwnershipGraph {
    company(where: {id: "company-id"}) {
      name
      shareholderGraph(minimumSharePercentage: 10.0) {
        rootId
        nodes {
          id
          entity {
            name
          }
          isBeneficialOwner
          shareClasses {
            shareClass
            sharePercentage {
              from
              to
            }
          }
          indirectSharePercentage {
            from
            to
          }
        }
        edges {
          parent
          child
          sharePercentage {
            from
            to
          }
        }
      }
    }
  }
  

            ## API Changelog: 2025-09-23
            
            Today's update introduces several enhancements to provide more context for Adverse Media Screening (AMS) events. We've also added a new country relationship
            type and improved the flexibility of creating and updating custom companies by making the `shareholders` field optional.
            
            ### Enhancements
            
            * **Added More Context to Adverse Media Events**
             We've added several new fields to the `AmsEvent` type to give you a clearer understanding of each media article.
               * `eventKind: AmsEventKind!`: Identifies the source of the event. The new `AmsEventKind` enum can be `GEMINI`, `OPOINT`, or `USER_CREATED`.
               * `createdBy: SimpleUser`: Specifies which user created the event, if applicable. This introduces the new `SimpleUser` and `UserAccountKind` types to
                 represent user information.
               * `behindPaywall: Boolean!`: A new boolean flag that indicates if the article content is behind a paywall.
            
            * **New `REGISTER` Value for Country Relationship**
             The `CountryRelationship` enum now includes `REGISTER` as a new value.
            
             For `BusinessPerson`s, person register countries are now classified as Register instead of Address. Residency, nationality, and citizenship data is included
             when available.
            
             For `Company`, register countries are moved to the new Register kind while other countries are set to Address. These changes are non-breaking but will result
             in country type changes for most entities.
            
            ### Improvements
            
            * **`shareholders` Field is Now Optional for Custom Companies**
             The `shareholders` field on the `CustomCompanyCreateInput` and `CustomCompanyUpdateInput` types is no longer a required list. You can now omit this field
             entirely when creating or updating a company that has no shareholders, whereas previously an empty array (`[]`) was required.
            
            ## 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:*
             ```graphql
             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."

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
    }
  }
}

Sending out forms

In order to send out forms, you can use the sendForm mutation. The mutation takes in the following parameters:

mutation SendForm {
  sendForm(
    where: {
      companyId: "<company_id>"
      formId: "<form_id>"
      recipientEmail: "<email_address>"
      recipientName: "<name>"
    }
  ) {
    success
    formInstanceId
  }
}

You'll need to provide the Strise ID of the company and the form ID of the form you want to send.

Obtaining the company ID

In cases where you only have the company's identifier, use the companyIdentifierSearch query. If you are unable to find a matching company, you can create a new company using the customCompanyCreate mutation.

Obtaining the form ID

You can see all your team's available forms by using the listForms:

query ListForms {
  listForms {
    id
    title
    description
  }
}

Monitoring the form status

The formInstanceId which is returned from the sendForm mutation can be used to monitor the form's status. Use the document query to monitor the form's status:

query GetDocument {
  document(
    where: {
      documentId: "<formInstanceId>"
      companyId: "<company_id>"
    }
  ) {
    id
    fileName
    size
    lastModifiedAt
    contentType
    downloadUrl
    source
    status
  }
}

The status field will indicate the form's status. A PENDING status means that the form is still being processed.

Once status is set to SUCCESS, the form's content can be downloaded using the downloadUrl

Listing all documents of a company

In some cases, a form submission might also include more than one document. To see all documents related to a company, use Company.documents:

query GetCompanyDocuments {
  company(where: { id: "<company_id>" }) {
    documents {
      id
      fileName
      size
      lastModifiedAt
      contentType
      downloadUrl
      source
      status
    }
  }
}

You may also use this field to track the status of a form submission.