What’s in This Release
- Public API v1.0, a RESTful interface for reading and updating Cynomi data
- API credentials you create, scope, and revoke from Settings
- Task retrieval with filters, including a last-updated filter for incremental syncs
- Two-way task updates and direct links between Cynomi tasks and external tickets
Public API v1.0 Is Generally Available
The Public API gives external systems a RESTful interface to access and update Cynomi data programmatically. It is built for partners who want Cynomi inside their operational workflows rather than beside them, which in practice means less re-keying and fewer places where the same status lives in two systems and disagrees.
Version 1.0 covers task synchronization, and it works against any PSA or ticketing system, including ConnectWise, Autotask, ServiceNow, and platforms you have built yourself. The API is extensible by design, so the integration work you do now carries forward as more of the platform becomes addressable. The integrations already in Cynomi keep working as they do today.
API Credentials You Scope and Rotate Yourself
Credentials are managed in Cynomi rather than requested from us. A new API Credentials section sits under Service Provider then Settings, where Service Provider Admins create and manage credentials directly. That keeps the access decision with the person who owns the tenant.
Each credential carries two controls that matter for a multi-client environment:
- Client access scope – the set of clients a credential can reach, so an integration built for one part of your book cannot read across all of it
- Permission level – what that credential is allowed to do with the data it can see
Credentials can be rotated, revoked, or deleted at any time. Credentials can be updated directly when an integration changes ownership or a contractor finishes an engagement.
Pull Only the Tasks a Workflow Needs
External systems can retrieve Cynomi tasks through the API, and the filtering is what makes that usable at scale. Results can be narrowed by status, priority, due date, plan, owner, and more, so a workflow pulls the slice it cares about rather than every task across every client and then discarding most of it.
There is also a dedicated filter for last updated time. An integration can ask for only what has changed since its previous sync, which keeps the two systems consistent without moving the whole task set on every run.
Why this matters
The last-updated filter lets integrations retrieve only tasks that changed since the previous sync, reducing unnecessary data retrieval as task and client volumes grow.
Push Updates Back, and Link Tasks to External Tickets
Through automated, bi-directional task synchronization, Cynomi keeps task and ticket status aligned across systems, eliminating manual re-entry and blind spots while helping remediation stay accurate, timely, and fully visible. Integrations can push updates back into Cynomi tasks, including status changes, notes, and evidence file attachments. Cynomi tasks can also be linked directly to the corresponding ticket in the external system, with links visible on the task and in the task list.
What This Changes for Your Delivery Team
A significant part of security delivery effort comes from the administration around the work. Duplicate task updates, evidence asked for in one system and held in another, and two records of the same status to keep in step. The Public API reduces that duplicate administration across the tasks your team executes daily, especially in larger, standardized operations.