Trimble Reactions API

The Reactions API from Trimble — 2 operation(s) for reactions.

GitHub OpenAPI

Operations 3

GET /context/{contextId}/issues/{issueId}/reactions List reactions for an issue #
POST /context/{contextId}/issues/{issueId}/reactions Add a reaction to an issue #
DELETE /context/{contextId}/issues/{issueId}/reactions/{reactionId} Delete a reaction #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/trimble:trimble-reactions-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

trimble-reactions-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Issue Management Service Reactions API
  description: '# Issue Management Service (IMS)


    REST API for creating, reading, updating, and deleting issues attached to a Trimble Connect context (project or file). Issues support rich access-control, capability discovery via `_actions`, and sync primitives (snapshot / changes feed).


    ## Context Types


    Every request targets a **context** identified by a TRN string passed as `{contextId}`. Two context types are supported and they have different ACL behaviours:


    | Context type | TRN pattern | ACL model |

    |---|---|---|

    | **Project** | `trn:2:tc:{region}:projects:{projectId}` | Full viewer model — ADMIN, creator, assignee, and explicit ACL holders. Plain project members without an explicit ACL grant have no automatic access. |

    | **File** | `trn:2:tc:{region}:projects:{projectId}:files:{fileId}` | Open access — any user who can access the file receives all issue actions **except** `issue:UpdatePermissions`. The `/permissions` endpoints return `404` for file contexts. |


    ## Capability Discovery — `_actions`


    All issue endpoints accept an optional `?fields=_actions` query parameter. When requested, the response includes a `_actions` array listing the wire-format action strings the authenticated caller is **currently authorised** to perform on that issue. Clients **must** check `_actions` before showing mutation controls rather than hard-coding role assumptions.


    Available action values:


    | Wire value | Meaning |

    |---|---|

    | `issue:Read` | View issue details |

    | `issue:Update` | Edit issue fields |

    | `issue:Delete` | Delete the issue |

    | `issue:AddLinks` | Create links on this issue |

    | `issue:DeleteLinks` | Remove links from this issue |

    | `issue:ReadLinks` | List links attached to this issue |

    | `issue:UpdatePermissions` | Call `PATCH /permissions` on this issue (project context only) |


    ## ACL Buckets


    Issue permissions are stored as ACL buckets. The API surface exposes **two** buckets only (`"full"` is internal and rejected on PATCH):


    | Bucket key | Actions granted | Notes |

    |---|---|---|

    | `"edit"` | `issue:Read`, `issue:Update`, `issue:AddLinks`, `issue:DeleteLinks`, `issue:ReadLinks`, `issue:UpdatePermissions` | Does **not** include `issue:Delete` |

    | `"view"` | `issue:Read`, `issue:ReadLinks` | Read-only access |


    The inherited ACL floor is: **creator → edit**, **assignees → edit**. Effective access = `max(inherited floor, explicit grant)` — explicit ACL can only **elevate**, never reduce, an actor''s access.


    ## ACL Permission Model (Project Context)


    - Project ADMIN → all 7 actions

    - Issue creator → all 7 actions

    - Issue assignee → `edit` bucket (no `issue:Delete`)

    - `tc-groups:*` in `acl.view` → VIEW bucket for all project members

    - Actors with explicit `"edit"` ACL entry → `edit` bucket

    - Actors with explicit `"view"` ACL entry → `view` bucket

    - No match → **empty actions** (denied; endpoints return 403)

    - Effective = `max(inherited floor, explicit grant)` — cannot downgrade


    When a new project is created, `shareNewIssuesWithAllProjectMembers` defaults to `true`, causing `tc-groups:*` to be auto-added to the `view` bucket of every newly created issue. Disabling this flag makes issues **private by default** (visible only to ADMIN, creator, and assignees).


    ## Identity Formats


    ACL identity strings must match `^(users:|tc-groups:).+$`:


    | Format | Example | Meaning |

    |---|---|---|

    | `users:{tiduuid}` | `users:abc123` | Specific Trimble Identity user |

    | `tc-groups:{groupId}` | `tc-groups:grp456` | Specific Connect project group |

    | `tc-groups:*` | `tc-groups:*` | All project members (wildcard) |


    A maximum of **100 identities** across all buckets combined is enforced on PATCH.'
  contact:
    name: Trimble Connect Platform Team
  version: v1
servers:
- url: https://app.connect.trimble.com/v1/issues
  description: Prod US1 (primary)
- url: https://app21.connect.trimble.com/v1/issues
  description: Prod EU1
- url: https://app22.connect.trimble.com/v1/issues
  description: Prod UK1
- url: https://app31.connect.trimble.com/v1/issues
  description: Prod AP1
- url: https://app32.connect.trimble.com/v1/issues
  description: Prod AP2
security:
- bearerAuth: []
tags:
- name: Reactions
paths:
  /context/{contextId}/issues/{issueId}/reactions:
    get:
      tags:
      - Reactions
      summary: List reactions for an issue
      description: Retrieve paginated list of reactions for a specified issue
      operationId: listReactions
      parameters:
      - name: contextId
        in: path
        description: The unique identifier of the context in TRN format (trn:2:tc:{us|eu|eu-gb|ap|ap-au}:projects:{projectId} for project context or trn:2:tc:{us|eu|eu-gb|ap|ap-au}:projects:{projectId}:files:{fileId} for file context).
        required: true
        schema:
          type: string
      - name: issueId
        in: path
        description: The unique identifier of the issue
        required: true
        schema:
          type: string
      - name: pageSize
        in: query
        description: Number of reactions to return per page (1-100)
        required: false
        schema:
          type: integer
          format: int32
          default: 100
        example: 100
      - name: skipToken
        in: query
        description: Token for retrieving the next page of results. A cursor pointing to the last known change of the objects. `skipToken` format is implementation detail of the service and must not be used or modified by client. The client should only pass the skipToken as it is received in Response.
        required: false
        schema:
          type: string
      responses:
        '200':
          description: Reactions retrieved successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PagedResponse'
    post:
      tags:
      - Reactions
      summary: Add a reaction to an issue
      description: Add a reaction (emoji) to a specified issue
      operationId: addReaction
      parameters:
      - name: contextId
        in: path
        description: The unique identifier of the context in TRN format (trn:2:tc:{us|eu|eu-gb|ap|ap-au}:projects:{projectId} for project context or trn:2:tc:{us|eu|eu-gb|ap|ap-au}:projects:{projectId}:files:{fileId} for file context).
        required: true
        schema:
          type: string
      - name: issueId
        in: path
        description: The unique identifier of the issue
        required: true
        schema:
          type: string
      requestBody:
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/ReactionRequest'
        required: true
      responses:
        '201':
          description: Reaction added successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ReactionResponse'
  /context/{contextId}/issues/{issueId}/reactions/{reactionId}:
    delete:
      tags:
      - Reactions
      summary: Delete a reaction
      description: Delete a specific reaction by its ID
      operationId: deleteReaction
      parameters:
      - name: contextId
        in: path
        description: The unique identifier of the context in TRN format (trn:2:tc:{us|eu|eu-gb|ap|ap-au}:projects:{projectId} for project context or trn:2:tc:{us|eu|eu-gb|ap|ap-au}:projects:{projectId}:files:{fileId} for file context).
        required: true
        schema:
          type: string
      - name: issueId
        in: path
        description: The unique identifier of the issue
        required: true
        schema:
          type: string
      - name: reactionId
        in: path
        description: The unique identifier of the reaction
        required: true
        schema:
          type: string
      responses:
        '204':
          description: Reaction deleted successfully
components:
  schemas:
    PageReference:
      type: object
      properties:
        href:
          type: string
    ReactionRequest:
      type: object
      properties:
        emoji:
          type: string
          description: The emoji reaction
      required:
      - emoji
    PageLink:
      type: object
      properties:
        first:
          $ref: '#/components/schemas/PageReference'
        self:
          $ref: '#/components/schemas/PageReference'
        next:
          $ref: '#/components/schemas/PageReference'
    PagedResponse:
      type: object
      properties:
        items:
          type: array
          items: {}
        links:
          $ref: '#/components/schemas/PageLink'
    ReactionResponse:
      type: object
      properties:
        id:
          type: string
          description: The unique ID of the reaction
        emoji:
          type: string
          description: The emoji reaction
        createdBy:
          type: string
          description: The user who created the reaction
        createdAt:
          type: string
          format: date-time
          description: When the reaction was created
      required:
      - createdAt
      - createdBy
      - emoji
      - id
  securitySchemes:
    bearerAuth:
      type: http
      description: 'Trimble Identity JWT bearer token. Pass as ''Authorization: Bearer {token}''.'
      scheme: bearer
      bearerFormat: JWT