> ## Documentation Index > Fetch the complete documentation index at: https://docs.synq.io/llms.txt > Use this file to discover all available pages before exploring further. # ListIncidents ## OpenAPI ````yaml /api-reference/openapi.yaml get /api/incidents/v1 openapi: 3.1.0 info: version: '1.0' title: SYNQ servers: - url: https://developer.synq.io - url: https://api.us.synq.io security: - bearerAuth: [] tags: - name: synq.issues.issues.v1.IssuesService description: IssuesService is a service for managing Issues. - name: synq.issues.v2.IssuesService description: IssuesService is a service for managing Issues. - name: synq.incidents.v1.IncidentsService description: IncidentsService is a service for managing Incidents. - name: synq.alerts.services.v1.AlertsService description: AlertsService provides operations for managing alert configurations. - name: synq.agent.recon.v1.YamlService description: >- YamlService provides stateless conversion between YAML config format and proto. This is useful for UI editors that need to display/edit suite configs as YAML. - name: synq.agent.recon.v1.SuiteDeploymentService description: |- SuiteDeploymentService is the platform plane of reconciliation. SuiteConfigService is the developer/authoring sandbox (edit, version, run ad-hoc with your own credentials — preview-only, no Entity, no Run, no Issue). A deployment is what SYNQ actually runs on the workspace's behalf: a frozen snapshot of a suite config, mapped to workspace-level SYNQ integrations, optionally scheduled or triggerable by API. Identity: every deployment has a stable deployment_id (UUIDv7) assigned on first promote. It survives re-promotes, schedule/mapping changes, and pause/resume. Downstream AssetCommand / RunCommand publication keys off deployment_id so Entity identity does not fragment on promote churn. - name: synq.agent.sre.v1.TriageService description: >- Service for managing issue triage operations, allowing LLM agents to conclude investigations and record evidence during the triage process. - name: synq.agent.sre.v1.LlmService description: Service for evaluating LLM requests and producing structured output. - name: synq.agent.sre.v1.FeatureRequestService description: >- FeatureRequestService allows MCP clients to submit feature requests when users encounter missing capabilities. This is a last-resort service — it should only be used when no existing tool can fulfill the user's request. - name: synq.integrations.v1.IntegrationsService description: |- IntegrationsService manages connections from Coalesce Quality to your data systems (warehouses, databases, and transformation tools). Concurrency: every integration carries an opaque `etag`. Read it from `GetIntegration` / `ListIntegrations`, then pass it back on `UpdateIntegration` / `DeleteIntegration` to ensure you modify the version you last saw. A stale etag is rejected with ABORTED (HTTP 409). Omit the etag for last-write-wins. Quota: each workspace has a limit on the number of integrations. Creating beyond the limit is rejected with RESOURCE_EXHAUSTED. Secrets: credential fields (passwords, tokens, keys) are write-only. They are masked (returned empty) on every read. On update, omit a secret to keep it, send a new value to rotate it, or send an explicit empty string to clear it (where the field is `optional`). - name: synq.auth.iam.v1.IamService - name: synq.monitors.predictions.v1.MonitorPredictionsService description: Access to anomaly detection model predictions and raw metric timeseries. - name: synq.monitors.info.v1.MonitorInfoService - name: synq.monitors.custom_monitors.v1.CustomMonitorsService - name: synq.monitors.history.v1.HistoryService - name: synq.monitors.automated_monitors.v1.DeploymentRulesService - name: synq.entities.executions.v2.EntityExecutionsService description: >- EntityExecutionsService provides read-only access to entity execution history. This service allows customers to retrieve information about all executions that happened on their entities, including execution status, timing, and messages. Use cases: - Retrieve execution history for specific entities - Filter executions by time range, status, or execution type - Get aggregated summaries of execution activity - Track execution trends and patterns - name: synq.datachecks.sqltests.v1.SqlTestsService description: SqlTestsService is a service for managing SqlTests. - name: synq.datachecks.v1.TriggerService description: TriggerService provides synchronous execution of datachecks on entities. - name: synq.datachecks.testsuggestions.v1.TestSuggestionsService - name: synq.extensions.atlan.provider.v1.AtlanProviderService - name: synq.extensions.atlan.integrations.v1.AtlanIntegrationService - name: synq.extensions.atlan.workflows.v1.AtlanWorkflowService - name: synq.savedviews.v1.SavedViewsService description: >- SavedViewsService manages saved views — named, reusable selections over your entities (and other surfaces) with display configuration, sharing and per-user pinning. A saved view is owned by the user who created it. It can be kept private, shared with the whole workspace, or granted to specific users. Reads return, for the calling user, how each view relates to them (mine / shared / granted) and what they are allowed to do with it. Workspace administrators can manage any view in the workspace. - name: synq.platforms.v1.PlatformsService description: PlatformsService is a service for managing Platforms and Integrations. - name: synq.queries.v1.NLQueryService description: >- NLQueryService generates structured Query protos from natural language descriptions using an LLM. - name: synq.schedule.v1.ScheduleService description: ScheduleService provides schedule evaluation utilities. - name: synq.entities.executions.v1.EntityExecutionsService description: 'Deprecated: Use [synq.entities.custom.v1.EntityExecutionsService] instead' - name: synq.entities.status.v1.EntityIncidentsService description: EntityIncidentsService is the service which retrieves entity status. - name: synq.entities.status.v1.EntityIssuesService description: EntityIssuesService is the service which retrieves entity issues status. - name: synq.entities.orchestration.v1.OrchestrationService description: >- OrchestrationService provides information about orchestration relationships between entities. This includes relationships between Airflow tasks and transformation models (dbt, SQLMesh), as well as task-to-task dependencies. - name: synq.entities.coordinates.v1.DatabaseCoordinatesService description: >- DatabaseCoordinatesService is a service for getting database coordinates of Entities. - name: synq.entities.checks.v1.ChecksCategoriesService description: |- ChecksCategoriesService lets workspace admins set explicit category overrides on individual checks. An explicit category is the authoritative category for a check — it takes precedence over the categories computed by the workspace's categorisation rules. It is a public API so customers can manage check categories programmatically; the same service is also mounted on the internal API. The workspace and the acting identity are always taken from the request context, never from the payload. - name: synq.entities.sql_insights.v1.SqlInsightsService description: >- SqlInsightsService exposes analytical information about the SQL used across a workspace's entities. It answers questions such as "which SQL constructs are used in my warehouse, and how often" and "what SQL constructs does this specific entity use", without requiring the caller to re-parse any SQL. - name: synq.entities.custom.v1.RelationshipsService description: >- RelationshipsService allow management of relationships between entities. Relationships can be created, updated, and deleted between 2 custom entities, or between a custom entity and Coalesce Quality native entity.enum There is no option to create relationships between 2 Coalesce Quality native entities (dbt model, BI dashboard, etc.). - name: synq.entities.custom.v1.TypesService description: TypesService is a service for managing custom entity types. - name: synq.entities.custom.v1.GroupsService description: >- It eliminates the need to keep state on client side to remember which assets were already created and which should be deleted. The server will keep track of the current state of the group and client can always send the intended new state. The server will calculate the diff and entities that are no longer present in the group will be removed. Example: 1. group has entities A, B, C at time t1 2. client sends group with entities B, C, D at time t2 3. server will remove entity A from the system and update the current state of the group to B, C, D The service is designed to be idempotent and can be called multiple times with the same state without causing any side effects. - name: synq.entities.custom.v1.EntityExecutionsService - name: synq.entities.custom.v1.EntitiesService description: >- custom.EntitiesService is a service for managing custom entities. Entities can represent various data platform concepts such as services, consumers, applications or data pipelines that are not natively available in Coalesce Quality. Entities are identified by a unique identifier and can be created, updated, read and deleted. - name: synq.entities.custom.v1.FeaturesService - name: synq.entities.impact.v1.ImpactService - name: synq.entities.schemas.v1.SchemaMismatchesService description: >- SchemaMismatchesService provides access to schema drift information between data platform tables and their definitions (e.g., dbt models). - name: synq.entities.schemas.v1.SchemasService description: EntitiesService is a service for retriving any entity. - name: synq.entities.constraints.v1.TableConstraintsService description: >- TableConstraintsService provides access to table constraint and index information. - name: synq.entities.changes.v1.ChangesService description: >- ChangesService provides functionality to track and retrieve all types of changes to data entities. This unified service returns ALL change types for an entity: - Git commits: Changes to code files (dbt models, SQL files) tracked in version control - Schema changes: Database schema modifications (columns added/removed/changed) - SQL definition changes: View/materialized view definition updates detected by Coalesce Quality Changes are returned with structured metadata including: - For git commits: structured statistics (directories, file types, top changes) - For schema changes: detailed column-level diffs - For SQL changes: before/after SQL definitions Use cases: - "What changed in the last week for table X?" → Returns git commits, schema changes, SQL changes - "Show me all commits affecting this dbt model" → Returns git commits with lineage context - "What schema changes happened to this table?" → Returns schema changes detected by Coalesce Quality - name: synq.entities.lineage.v1.LineageService description: |- LineageService allows you to fetch: * Entity level lineage from a starting point of one or more entities. * Column Level lineage from a starting point of multiple columns of a single entity. - name: synq.entities.entities.v1.EntitiesService description: EntitiesService is a service for retriving any entity. - name: synq.entities.annotations.v1.AnnotationsService description: >- AnnotationsService provides operations for managing and querying entity annotations. Annotations are key-value pairs that can be attached to entities for categorization and filtering. - name: synq.entities.code.v1.CodeService description: >- CodeService is a service for retrieving code associated with entities in the system. It provides functionality to access and manage code artifacts such as SQL queries, Python scripts, dbt models, and other code configurations that are part of Coalesce Quality entities. - name: synq.entities.resolve.v1.IdentifierResolveService description: >- IdentifierResolveService resolves identifiers to their Coalesce Quality paths and identities. - name: synq.ingest.airflow.v1.AirflowLogsService - name: synq.ingest.cloudwatch.v1.CloudwatchService - name: synq.ingest.openlineage.v1.OpenlineageService - name: synq.ingest.dwh.v1.DwhService - name: synq.dataproducts.v1.DataproductsService description: DataproductsService can be used to manage data products. - name: synq.git.commits.v1.CommitsService paths: /api/incidents/v1: get: tags: - synq.incidents.v1.IncidentsService summary: ListIncidents operationId: synq.incidents.v1.IncidentsService.ListIncidents parameters: - name: time.field in: query schema: $ref: '#/components/schemas/synq.incidents.v1.ListIncidentsRequest.Field' title: field - name: time.from.seconds in: query description: |- Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive. schema: type: - integer - string title: seconds format: int64 description: |- Represents seconds of UTC time since Unix epoch 1970-01-01T00:00:00Z. Must be from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59Z inclusive. - name: time.from.nanos in: query description: >- Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive. schema: type: integer title: nanos format: int32 description: >- Non-negative fractions of a second at nanosecond resolution. Negative second values with fractions must still have non-negative nanos values that count forward in time. Must be from 0 to 999,999,999 inclusive. - name: sort.sortBy in: query schema: $ref: '#/components/schemas/synq.incidents.v1.ListIncidentsRequest.Field' title: sort_by - name: sort.order in: query schema: $ref: >- #/components/schemas/synq.incidents.v1.ListIncidentsRequest.Sort.Order title: order - name: pagination.cursor in: query description: >- Opaque cursor token for the next page of results. If not provided, returns the first page. This is an encoded token that should be passed as-is from the previous PageInfo.last_id. schema: type: string title: cursor description: >- Opaque cursor token for the next page of results. If not provided, returns the first page. This is an encoded token that should be passed as-is from the previous PageInfo.last_id. - name: pagination.pageSize in: query description: >- Maximum number of items to return in a single page. If not provided, defaults vary per API. schema: type: integer title: page_size minimum: 0 format: int32 description: >- Maximum number of items to return in a single page. If not provided, defaults vary per API. - name: states in: query description: Filter by states schema: type: array items: $ref: '#/components/schemas/synq.incidents.v1.Incident.State' title: states description: Filter by states - name: affectedEntities.dbtCoreNode.integrationId in: query description: >- Opaque identifier of the dbt Core project. Usually the Coalesce Quality integration id (a UUID), but may also be the dbt project name from manifest.json when the integration is configured to identify assets by project name. Treat it as an opaque string, not a UUID. required: true schema: type: string title: integration_id description: >- Opaque identifier of the dbt Core project. Usually the Coalesce Quality integration id (a UUID), but may also be the dbt project name from manifest.json when the integration is configured to identify assets by project name. Treat it as an opaque string, not a UUID. - name: affectedEntities.dbtCoreNode.nodeId in: query description: Dbt node_id that identifies one of dbt DAG nodes (model, test, etc) required: true schema: type: string title: node_id description: >- Dbt node_id that identifies one of dbt DAG nodes (model, test, etc) - name: affectedEntities.dbtCloudNode.projectId in: query description: Your dbt Cloud project id required: true schema: type: string title: project_id description: Your dbt Cloud project id - name: affectedEntities.dbtCloudNode.accountId in: query description: Your dbt Cloud account id schema: type: string title: account_id description: Your dbt Cloud account id - name: affectedEntities.dbtCloudNode.nodeId in: query description: Dbt node_id that identifies one of dbt DAG nodes (model, test, etc) required: true schema: type: string title: node_id description: >- Dbt node_id that identifies one of dbt DAG nodes (model, test, etc) - name: affectedEntities.bigqueryTable.project in: query description: BigQuery project required: true schema: type: string title: project description: BigQuery project - name: affectedEntities.bigqueryTable.dataset in: query description: BigQuery dataset id required: true schema: type: string title: dataset description: BigQuery dataset id - name: affectedEntities.bigqueryTable.table in: query description: BigQuery table name required: true schema: type: string title: table description: BigQuery table name - name: affectedEntities.snowflakeTable.account in: query description: Snowflake account required: true schema: type: string title: account description: Snowflake account - name: affectedEntities.snowflakeTable.database in: query description: Snowflake database required: true schema: type: string title: database description: Snowflake database - name: affectedEntities.snowflakeTable.schema in: query description: Snowflake schema required: true schema: type: string title: schema description: Snowflake schema - name: affectedEntities.snowflakeTable.table in: query description: Snowflake table required: true schema: type: string title: table description: Snowflake table - name: affectedEntities.redshiftTable.cluster in: query description: Redshift cluster schema: type: string title: cluster description: Redshift cluster - name: affectedEntities.redshiftTable.database in: query description: Redshift database required: true schema: type: string title: database description: Redshift database - name: affectedEntities.redshiftTable.schema in: query description: Redshift schema required: true schema: type: string title: schema description: Redshift schema - name: affectedEntities.redshiftTable.table in: query description: Redshift table required: true schema: type: string title: table description: Redshift table - name: affectedEntities.postgresTable.host in: query description: Postgres hostname without port required: true schema: type: string title: host description: Postgres hostname without port - name: affectedEntities.postgresTable.database in: query description: Postgres database required: true schema: type: string title: database description: Postgres database - name: affectedEntities.postgresTable.schema in: query description: Postgres schema required: true schema: type: string title: schema description: Postgres schema - name: affectedEntities.postgresTable.table in: query description: Postgres table required: true schema: type: string title: table description: Postgres table - name: affectedEntities.mysqlTable.host in: query description: Mysql hostname without port required: true schema: type: string title: host description: Mysql hostname without port - name: affectedEntities.mysqlTable.schema in: query description: Mysql database required: true schema: type: string title: schema description: Mysql database - name: affectedEntities.mysqlTable.table in: query description: Mysql table required: true schema: type: string title: table description: Mysql table - name: affectedEntities.clickhouseTable.host in: query description: Clickhouse hostname without port required: true schema: type: string title: host description: Clickhouse hostname without port - name: affectedEntities.clickhouseTable.schema in: query description: Clickhouse database required: true schema: type: string title: schema description: Clickhouse database - name: affectedEntities.clickhouseTable.table in: query description: Clickhouse table required: true schema: type: string title: table description: Clickhouse table - name: affectedEntities.airflowDag.integrationId in: query description: Coalesce Quality integration_id that identifies the Airflow instance required: true schema: type: string title: integration_id description: >- Coalesce Quality integration_id that identifies the Airflow instance - name: affectedEntities.airflowDag.dagId in: query description: Airflow dag_id that identifies the DAG required: true schema: type: string title: dag_id description: Airflow dag_id that identifies the DAG - name: affectedEntities.airflowTask.integrationId in: query description: Coalesce Quality integration_id that identifies the Airflow instance required: true schema: type: string title: integration_id description: >- Coalesce Quality integration_id that identifies the Airflow instance - name: affectedEntities.airflowTask.dagId in: query description: Airflow dag_id that identifies the DAG required: true schema: type: string title: dag_id description: Airflow dag_id that identifies the DAG - name: affectedEntities.airflowTask.taskId in: query description: Airflow task_id that identifies the task within the DAG required: true schema: type: string title: task_id description: Airflow task_id that identifies the task within the DAG - name: affectedEntities.custom.id in: query description: |- Id that identifies the custom entity The Id should be unique within the custom entity Identifier. required: true schema: type: string title: id description: |- Id that identifies the custom entity The Id should be unique within the custom entity Identifier. - name: affectedEntities.dataproduct.id in: query description: Dataproduct id that identifies the Dataproduct required: true schema: type: string title: id format: uuid description: Dataproduct id that identifies the Dataproduct - name: affectedEntities.synqPath.path in: query description: >- Coalesce Quality path that identifies the Coalesce Quality entity, needs to be one of supported paths required: true schema: type: string title: path description: >- Coalesce Quality path that identifies the Coalesce Quality entity, needs to be one of supported paths - name: affectedEntities.databricksTable.workspace in: query description: URL of Databricks workspace required: true schema: type: string title: workspace description: URL of Databricks workspace - name: affectedEntities.databricksTable.catalog in: query description: Databricks catalog required: true schema: type: string title: catalog description: Databricks catalog - name: affectedEntities.databricksTable.schema in: query description: Databricks schema required: true schema: type: string title: schema description: Databricks schema - name: affectedEntities.databricksTable.table in: query description: Databricks table or view required: true schema: type: string title: table description: Databricks table or view - name: affectedEntities.trinoTable.host in: query description: Hostname of the Trino instance required: true schema: type: string title: host description: Hostname of the Trino instance - name: affectedEntities.trinoTable.catalog in: query description: Trino catalog required: true schema: type: string title: catalog description: Trino catalog - name: affectedEntities.trinoTable.schema in: query description: Trino schema required: true schema: type: string title: schema description: Trino schema - name: affectedEntities.trinoTable.table in: query description: Trino table or view required: true schema: type: string title: table description: Trino table or view - name: affectedEntities.sqlMeshModel.integrationId in: query description: Coalesce Quality integration_id that identifies the dbt Core project required: true schema: type: string title: integration_id format: uuid description: >- Coalesce Quality integration_id that identifies the dbt Core project - name: affectedEntities.sqlMeshModel.fqn in: query description: SQLMesh model fully qualified name required: true schema: type: string title: fqn description: SQLMesh model fully qualified name - name: affectedEntities.sqlMeshAudit.integrationId in: query description: Coalesce Quality integration_id that identifies the dbt Core project required: true schema: type: string title: integration_id format: uuid description: >- Coalesce Quality integration_id that identifies the dbt Core project - name: affectedEntities.sqlMeshAudit.fqn in: query description: SQLMesh model fully qualified name required: true schema: type: string title: fqn description: SQLMesh model fully qualified name - name: affectedEntities.sqlMeshAudit.auditId in: query description: Identifier of the audit required: true schema: type: string title: audit_id description: Identifier of the audit - name: affectedEntities.monitor.monitoredId.mssqlTable.host in: query description: Hostname of the SQL Server instance required: true schema: type: string title: host description: Hostname of the SQL Server instance - name: affectedEntities.monitor.monitoredId.mssqlTable.database in: query description: SQL Server database required: true schema: type: string title: database description: SQL Server database - name: affectedEntities.monitor.monitoredId.mssqlTable.schema in: query description: SQL Server schema (e.g. "dbo") required: true schema: type: string title: schema description: SQL Server schema (e.g. "dbo") - name: affectedEntities.monitor.monitoredId.mssqlTable.table in: query description: SQL Server table or view required: true schema: type: string title: table description: SQL Server table or view - name: affectedEntities.monitor.monitoredId.oracleTable.host in: query description: Hostname of the Oracle instance required: true schema: type: string title: host description: Hostname of the Oracle instance - name: affectedEntities.monitor.monitoredId.oracleTable.serviceName in: query description: Oracle service name (PDB) required: true schema: type: string title: service_name description: Oracle service name (PDB) - name: affectedEntities.monitor.monitoredId.oracleTable.schema in: query description: Oracle schema (= owning user) required: true schema: type: string title: schema description: Oracle schema (= owning user) - name: affectedEntities.monitor.monitoredId.oracleTable.table in: query description: Oracle table or view required: true schema: type: string title: table description: Oracle table or view - name: affectedEntities.monitor.monitoredId.athenaTable.instance in: query description: |- AWS account and region the Athena workgroup runs in, formatted as "." (e.g. "123456789012.eu-west-1"). Auto-derived from sts:GetCallerIdentity at integration setup time. required: true schema: type: string title: instance description: |- AWS account and region the Athena workgroup runs in, formatted as "." (e.g. "123456789012.eu-west-1"). Auto-derived from sts:GetCallerIdentity at integration setup time. - name: affectedEntities.monitor.monitoredId.athenaTable.catalog in: query description: |- Glue Data Catalog name. Almost always "AwsDataCatalog" — the default catalog for Athena unless the customer registered a federated catalog. required: true schema: type: string title: catalog description: >- Glue Data Catalog name. Almost always "AwsDataCatalog" — the default catalog for Athena unless the customer registered a federated catalog. - name: affectedEntities.monitor.monitoredId.athenaTable.database in: query description: Glue database (the namespace users typically filter on). required: true schema: type: string title: database description: Glue database (the namespace users typically filter on). - name: affectedEntities.monitor.monitoredId.athenaTable.table in: query description: Glue table or view name. required: true schema: type: string title: table description: Glue table or view name. - name: affectedEntities.monitor.monitoredId.savedView.id in: query description: Saved view id (client-supplied UUID) that identifies the saved view required: true schema: type: string title: id format: uuid description: >- Saved view id (client-supplied UUID) that identifies the saved view - name: affectedEntities.monitor.monitorId in: query description: Identifier of the monitor required: true schema: type: string title: monitor_id description: Identifier of the monitor - name: affectedEntities.monitor.segment in: query description: Optional monitor segmentation identifier schema: type: string title: segment description: Optional monitor segmentation identifier - name: affectedEntities.monitor.integrationId in: query description: Coalesce Quality integration_id of the monitored identifier schema: type: string title: integration_id description: Coalesce Quality integration_id of the monitored identifier deprecated: true responses: '200': description: Success content: application/json: schema: $ref: '#/components/schemas/synq.incidents.v1.ListIncidentsResponse' components: schemas: synq.incidents.v1.ListIncidentsRequest.Field: type: string title: Field enum: - FIELD_UNSPECIFIED - FIELD_CREATED_AT - FIELD_UPDATED_AT synq.incidents.v1.ListIncidentsRequest.Sort.Order: type: string title: Order enum: - ORDER_UNSPECIFIED - ORDER_ASC - ORDER_DESC synq.incidents.v1.Incident.State: type: string title: State enum: - STATE_UNSPECIFIED - STATE_OPEN - STATE_CLOSED - STATE_CANCELLED synq.incidents.v1.ListIncidentsResponse: type: object properties: incidents: type: array items: $ref: '#/components/schemas/synq.incidents.v1.Incident' title: ListIncidentsResponse additionalProperties: false synq.incidents.v1.Incident: type: object properties: id: type: string description: ID of the incident. index: type: integer format: int32 description: Index of the incident (for human-readable references). name: type: string description: Name of the incident. issueIds: type: array items: type: string description: IDs of issues associated with this incident. createdBy: $ref: '#/components/schemas/synq.issues.actor.v1.Actor' description: Actor who created the incident. owner: $ref: '#/components/schemas/synq.users.v1.User' description: Owner of the incident. createdAt: $ref: '#/components/schemas/google.protobuf.Timestamp' description: Time at which the incident was created. updatedBy: $ref: '#/components/schemas/synq.issues.actor.v1.Actor' description: Actor who last updated the incident. updatedAt: $ref: '#/components/schemas/google.protobuf.Timestamp' description: Time at which the incident was last updated. state: $ref: '#/components/schemas/synq.incidents.v1.Incident.State' description: State of the incident. comments: type: array items: $ref: '#/components/schemas/synq.incidents.v1.IncidentComment' description: List of comments posted on the incident. title: Incident additionalProperties: false synq.issues.actor.v1.Actor: type: object allOf: - properties: name: type: string title: name minLength: 1 via: $ref: '#/components/schemas/synq.issues.actor.v1.Actor.Via' title: via - oneOf: - properties: email: $ref: '#/components/schemas/synq.issues.actor.v1.EmailUser' title: email title: email required: - email - properties: pagerduty: $ref: '#/components/schemas/synq.issues.actor.v1.PagerdutyUser' title: pagerduty title: pagerduty required: - pagerduty - properties: slack: $ref: '#/components/schemas/synq.issues.actor.v1.SlackUser' title: slack title: slack required: - slack title: Actor required: - name additionalProperties: false description: |- Actor identifies who performed a write — set by the calling client and carried end-to-end through the public API into stored audit trails (issue status changes, comments, incident assignments) and rendered downstream (e.g. Slack/MSTeams/email alerts). Producers should populate: 1. `name` — human-readable display label, derived from `synq.auth.iam.v1.IamResponse.user_name` when available, falling back to `user_email`. Avoid generic placeholders ("MCP", "API"); readers treat those as "no identity resolved" and fall back to impersonal copy. 2. `user` — the strongest identifier the caller can prove. For human callers, set `email` from `IamResponse.user_email` so the server can resolve the caller back to a workspace user. 3. `via` — entry-point label for the channel through which the request arrived (e.g. VIA_MCP for the MCP server), regardless of who the caller is. synq.users.v1.User: type: object properties: id: type: string firstName: type: string lastName: type: string email: type: string identities: type: array items: type: string description: |- Canonical identity strings for this user. Includes "synq:" and all linked aliases (email, slack, msteams). Can be passed to ListIssues(interacted_by_identities) to filter issues this user interacted with. title: User additionalProperties: false google.protobuf.Timestamp: type: string examples: - '2023-01-15T01:30:15.01Z' - '2024-12-25T12:00:00Z' format: date-time description: >- A Timestamp represents a point in time independent of any time zone or local calendar, encoded as a count of seconds and fractions of seconds at nanosecond resolution. The count is relative to an epoch at UTC midnight on January 1, 1970, in the proleptic Gregorian calendar which extends the Gregorian calendar backwards to year one. All minutes are 60 seconds long. Leap seconds are "smeared" so that no leap second table is needed for interpretation, using a [24-hour linear smear](https://developers.google.com/time/smear). The range is from 0001-01-01T00:00:00Z to 9999-12-31T23:59:59.999999999Z. By restricting to that range, we ensure that we can convert to and from [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) date strings. # Examples Example 1: Compute Timestamp from POSIX `time()`. Timestamp timestamp; timestamp.set_seconds(time(NULL)); timestamp.set_nanos(0); Example 2: Compute Timestamp from POSIX `gettimeofday()`. struct timeval tv; gettimeofday(&tv, NULL); Timestamp timestamp; timestamp.set_seconds(tv.tv_sec); timestamp.set_nanos(tv.tv_usec * 1000); Example 3: Compute Timestamp from Win32 `GetSystemTimeAsFileTime()`. FILETIME ft; GetSystemTimeAsFileTime(&ft); UINT64 ticks = (((UINT64)ft.dwHighDateTime) << 32) | ft.dwLowDateTime; // A Windows tick is 100 nanoseconds. Windows epoch 1601-01-01T00:00:00Z // is 11644473600 seconds before Unix epoch 1970-01-01T00:00:00Z. Timestamp timestamp; timestamp.set_seconds((INT64) ((ticks / 10000000) - 11644473600LL)); timestamp.set_nanos((INT32) ((ticks % 10000000) * 100)); Example 4: Compute Timestamp from Java `System.currentTimeMillis()`. long millis = System.currentTimeMillis(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(millis / 1000) .setNanos((int) ((millis % 1000) * 1000000)).build(); Example 5: Compute Timestamp from Java `Instant.now()`. Instant now = Instant.now(); Timestamp timestamp = Timestamp.newBuilder().setSeconds(now.getEpochSecond()) .setNanos(now.getNano()).build(); Example 6: Compute Timestamp from current time in Python. timestamp = Timestamp() timestamp.GetCurrentTime() # JSON Mapping In JSON format, the Timestamp type is encoded as a string in the [RFC 3339](https://www.ietf.org/rfc/rfc3339.txt) format. That is, the format is "{year}-{month}-{day}T{hour}:{min}:{sec}[.{frac_sec}]Z" where {year} is always expressed using four digits while {month}, {day}, {hour}, {min}, and {sec} are zero-padded to two digits each. The fractional seconds, which can go up to 9 digits (i.e. up to 1 nanosecond resolution), are optional. The "Z" suffix indicates the timezone ("UTC"); the timezone is required. A proto3 JSON serializer should always use UTC (as indicated by "Z") when printing the Timestamp type and a proto3 JSON parser should be able to accept both UTC and other timezones (as indicated by an offset). For example, "2017-01-15T01:30:15.01Z" encodes 15.01 seconds past 01:30 UTC on January 15, 2017. In JavaScript, one can convert a Date object to this format using the standard [toISOString()](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Date/toISOString) method. In Python, a standard `datetime.datetime` object can be converted to this format using [`strftime`](https://docs.python.org/2/library/time.html#time.strftime) with the time format spec '%Y-%m-%dT%H:%M:%S.%fZ'. Likewise, in Java, one can use the Joda Time's [`ISODateTimeFormat.dateTime()`]( http://www.joda.org/joda-time/apidocs/org/joda/time/format/ISODateTimeFormat.html#dateTime%2D%2D ) to obtain a formatter capable of generating timestamps in this format. synq.incidents.v1.IncidentComment: type: object properties: id: type: string message: type: string createdAt: $ref: '#/components/schemas/google.protobuf.Timestamp' actor: $ref: '#/components/schemas/synq.issues.actor.v1.Actor' title: IncidentComment additionalProperties: false synq.issues.actor.v1.Actor.Via: type: string title: Via enum: - VIA_UNSPECIFIED - VIA_API - VIA_MCP - VIA_SLACK - VIA_PAGERDUTY synq.issues.actor.v1.EmailUser: type: object properties: userEmail: type: string minLength: 1 format: email title: EmailUser required: - userEmail additionalProperties: false synq.issues.actor.v1.PagerdutyUser: type: object properties: userId: type: string minLength: 1 title: PagerdutyUser required: - userId additionalProperties: false synq.issues.actor.v1.SlackUser: type: object properties: userId: type: string minLength: 1 title: SlackUser required: - userId additionalProperties: false securitySchemes: bearerAuth: type: http scheme: bearer ````