> ## Documentation Index > Fetch the complete documentation index at: https://docs.engini.ai/llms.txt > Use this file to discover all available pages before exploring further. # List trigger events > The firings this trigger has captured, newest first - one event PER RECORD, not per run: the engine's contract is one run per tick carrying the whole array, and this API's is one event per record, which is what __trigger_dispatch exists to reconcile. Duplicate records are absent by construction, not filtered on read: dispatch suppresses a repeated (trigger, payload) pair inside the instance's dedupe_window_hours, because the platform's poll watermark advances to a run's START and would otherwise re-deliver records created mid-run. Events are retained 30 days. Delivery state and replay are not part of this response - they arrive with the delivery pipeline. ## OpenAPI ````yaml /api-reference/openapi.json get /v1/triggers/{triggerId}/events openapi: 3.0.0 info: title: Engini DeveloperAPI version: v1 description: 'Merged public developer API spec: Identity + WorkflowApi.' servers: - url: https://api.engini.io security: - Bearer: [] - ApiKey: [] tags: - name: Auth description: Identify the caller a Developer API request is authenticated as. - name: Applications description: >- Discover the applications (toolkits) available in Engini and their connection requirements. - name: Tools description: Browse and execute the tools exposed by Engini applications. - name: Toolsets description: Manage toolsets - named groupings of connections and tools. - name: McpServers description: >- Inspect and maintain MCP servers - the account-wide endpoints that expose Engini tools and workflows over the Model Context Protocol. Distinct from the MCPClient connection kind, which is Engini consuming a third-party MCP server. - name: Connections description: >- Manage connections to applications, including OAuth sign-in and default-connection selection. - name: Triggers description: >- Create triggers that fire when something changes in a connected app, and manage the destinations their events are delivered to. paths: /v1/triggers/{triggerId}/events: get: tags: - Triggers summary: List trigger events description: >- The firings this trigger has captured, newest first - one event PER RECORD, not per run: the engine's contract is one run per tick carrying the whole array, and this API's is one event per record, which is what __trigger_dispatch exists to reconcile. Duplicate records are absent by construction, not filtered on read: dispatch suppresses a repeated (trigger, payload) pair inside the instance's dedupe_window_hours, because the platform's poll watermark advances to a run's START and would otherwise re-deliver records created mid-run. Events are retained 30 days. Delivery state and replay are not part of this response - they arrive with the delivery pipeline. operationId: Triggers_ListTriggerEvents parameters: - name: triggerId in: path required: true description: The ti_ public id of the trigger instance. schema: type: string x-position: 1 - name: offset in: query description: Zero-based index of the first item to return. schema: type: integer format: int32 default: 0 x-position: 2 - name: top in: query description: Maximum number of items to return. schema: type: integer format: int32 default: 100 x-position: 3 responses: '200': description: A paginated list of captured events. content: application/json: schema: $ref: '#/components/schemas/PaginatedResponseOfTriggerEventView' '400': description: Bad request - malformed body or invalid parameters. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '401': description: Unauthorized - missing or invalid bearer token. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '403': description: Forbidden - the caller lacks access to the resource. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '404': description: >- No such trigger in this account. A trigger belonging to another account answers the same way, deliberately. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '429': description: Too many requests - rate limit exceeded. headers: Retry-After: description: Number of seconds to wait before retrying. schema: type: integer content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' '500': description: Internal server error - an unexpected error occurred. content: application/json: schema: $ref: '#/components/schemas/ErrorResponse' security: - Bearer: [] - ApiKey: [] components: schemas: PaginatedResponseOfTriggerEventView: type: object description: Offset-based paginated wrapper for a list of items. additionalProperties: false required: - items - totalCount - offset - top properties: items: type: array description: The items in the current page. items: $ref: '#/components/schemas/TriggerEventView' totalCount: type: integer description: Total number of items available across all pages. format: int32 offset: type: integer description: Number of items skipped before this page (the requested offset). format: int32 top: type: integer description: Maximum number of items requested for this page. format: int32 ErrorResponse: type: object description: >- Unified error envelope for every non-200 response from /api/DeveloperAPI/v1/*. See applications-tools-spec.md ยง"Error envelope". additionalProperties: false required: - errorCode - message - requestId - timestamp - path properties: errorCode: type: string description: Machine-readable error code identifying the failure. message: type: string description: Human-readable error message. requestId: type: string description: Identifier of the request, for support/correlation. timestamp: type: string description: Timestamp when the error occurred (ISO 8601). path: type: string description: Request path that produced the error. details: type: array description: Per-field validation details, when applicable. nullable: true items: $ref: '#/components/schemas/ErrorDetail' TriggerEventView: type: object description: >- One captured trigger firing, as GET /v1/triggers/{triggerId}/events returns it - the payload Engini captured plus where its delivery got to. additionalProperties: false required: - delivery properties: id: type: string description: te_ + base62 - the only event id the API exposes. trigger_id: type: string description: The ti_ instance this firing belongs to. Survives a re-point. occurred_at: type: string description: When the firing happened, not when the row was written. format: date-time payload: description: >- The record, exactly as a delivery would carry it - or the truncation envelope, when PayloadTruncated is true. nullable: true payload_truncated: type: boolean description: >- True when the record exceeded the payload cap and Payload is the truncation envelope rather than the record. Surfaced rather than hidden: a caller reconciling against their own system needs to know they are looking at a stand-in. payload_hash: type: string description: >- SHA-256 of the canonicalised ORIGINAL payload - the same value the dedupe guard keys on, so a caller can reconcile "did I already see this record" without re-deriving our canonical form. delivery: description: >- Where this event's delivery got to. On the live subscribe stream this is always pending; read GET /v1/triggers/events/{eventId} for the settled state. oneOf: - $ref: '#/components/schemas/TriggerEventDeliveryStateDTO' ErrorDetail: type: object description: A single field-level error detail within an ErrorResponse. additionalProperties: false required: - field - issue properties: field: type: string description: Name of the field the issue relates to. issue: type: string description: Description of the issue with the field. TriggerEventDeliveryStateDTO: type: string description: >- Where this event's delivery got to. On the live subscribe stream this is always pending; read GET /v1/triggers/events/{eventId} for the settled state. x-enumNames: - Pending - Delivered - Failed - DeadLettered enum: - pending - delivered - failed - dead_lettered securitySchemes: Bearer: type: http description: Enter your JWT token scheme: bearer bearerFormat: JWT ApiKey: type: apiKey description: >- Opaque Developer API key (prefix `eng_`). Authenticates as the key's owner and resolves the account automatically. name: x-api-key in: header ````