Skip to content
    API & Integrations

    API Keys & External Application Integration

    Why and how to connect your own dashboards, scripts and platforms to SeqOps with API keys, and read your SeqOps data through read-only endpoints.

    Why do customers need API key integration?

    There are four common scenarios where customers would want to integrate SeqOps into their own applications and platforms.

    1. Integrating with existing dashboards

    Customers may already use platforms such as Grafana, ServiceNow, Power BI, or internal NOC dashboards. Instead of opening another application or switching between multiple browser tabs, they want to see SeqOps security statistics alongside their existing operational data.

    2. Building customized dashboards and visualizations

    Every customer has different reporting requirements and visualization preferences. Some may want separate views for individual customers, regions, environments, or severity levels. Rather than building a different dashboard for every customer's preference, SeqOps provides the data through APIs, allowing customers to design their own dashboards, charts, and widgets.

    3. Enabling machine-to-machine communication

    Not every integration involves a human user. Customers may have automated scripts, scheduled jobs, monitoring systems, or ticketing workflows that need to retrieve SeqOps information.

    For example:

    • •A nightly script that exports vulnerability and CVE statistics into a compliance report.
    • •An automated alert or ticket created whenever an agent becomes unhealthy or goes offline.
    • •A scheduled job that retrieves compliance statistics and updates an internal dashboard.

    These integrations need their own credentials because automated systems cannot depend on a human logging in with a username, password, or MFA verification every time they need data.

    4. Supporting MSPs and reseller integrations

    Managed Service Providers (MSPs) and resellers may want to integrate SeqOps data into their own branded platforms or customer portals. They can consume the authorized data through our APIs and present it using their own branding, dashboards, and reporting structures.

    Why API keys instead of shared user credentials?

    API keys provide a dedicated identity for each external application or integration, rather than relying on an individual's login credentials.

    This gives us several advantages:

    • •Identification — Each API key can have a meaningful name identifying the application or integration using it.
    • •IP restrictions — Access can be restricted to approved IP addresses, where supported.
    • •Traceability — We can track usage, including when a key was last used.
    • •Independent revocation — If an integration is no longer required or a key is compromised, we can revoke that specific key without affecting the customer's human user accounts.
    • •Controlled access — We can apply permissions and read-only restrictions to individual integrations.
    • •Auditability — We can track which integration accessed which endpoints and when.

    This approach provides better security, accountability, and control than sharing personal login credentials.

    How does it work in SeqOps?

    1. The customer generates an API key for their external application.
    2. The application uses its credentials to request a short-lived access token.
    3. The access token is included in API requests to authenticate with SeqOps.
    4. The application consumes authorized GET endpoints to retrieve data such as CVEs, vulnerabilities, security frameworks, compliance status, agent health, and other security statistics.
    5. The application processes the JSON responses and displays the information in its own dashboards, reports, or widgets.
    6. When the access token expires, the application requests a new token using its securely stored API credentials and continues retrieving the latest available data.

    The key point: SeqOps provides the data and secure access to it. The customer decides how to consume, visualize, and integrate that data within their own application.

    Good to Know

    • •API keys are created under Settings → API Keys.
    • •Requests your applications make through the API don't count toward your plan's API requests per month.
    • •To send alerts out of SeqOps instead, use a channel or a webhook. See Connecting Slack, Jira, ServiceNow & Teams and Webhook Setup.
    apiapi keysintegrationdashboards

    We use cookies

    We use essential cookies to run this site. With your permission, we'd also like to use analytics cookies to see how the site is used, and functional cookies for chat and videos. Change your choice any time under Cookie settings. Read our Cookies Policy