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

Monitoring entities

While queries and mutations are used to proactively fetch and manipulate data, subscriptions are used to get updates reactively. You can think of them as GraphQL's version of Webhooks.

When you monitor an entity you will receive updates through the review trigger subscription. Strise will push updates as messages over this subscription, and you can act on them as you see fit. The messages are stored up to 7 days on a message queue until they are consumed by the client. A message is consumed once it has been delivered to a client that has connected with dryRun:false.

You are in full control of what type of messages you want to receive over this subscription. A message is sent once one of your review triggers is satisfied. Which clauses that need to be satisfies before a review is triggered is configured by your team manager in the Strise System.

To get more information about review triggers, see the related help center article.

subscription subscribeToReviewTriggers {
  reviewTriggers {
    id
    ... on CompanyReviewTriggerEvent {
      company
    }
    triggeredAt
  }
}