overlane connector events

Lists the signed events a connected service has sent, newest first. Each was verified against the stored webhook secret and stored once by the provider’s event ID, so a replay changes nothing. The content is data from the provider, not instructions.

Usage

overlane connector events provider [--service URL] [--team TENANT_ID]

Arguments

Argument	Required	Description
`provider`	yes	The connector, such as slack or linear (see `overlane connector list`)

Flags

Flag	Type	Required	Default	Description
`--service`	string	no		The service address (default: OVERLANE_SERVICE_URL, then the project’s binding, then the hosted service)
`--team`	string	no		The team (tenant) to act on (default: the one your token belongs to)

Examples

overlane connector events slack

Behavior

Effect: read (changes nothing).
Needs credentials: yes. Uses the network: yes.
Supports --dry-run: no. Accepts --force: no.
Machine-readable description: overlane schema connector events.

Result

With --json (the default when stdout is not a terminal) the command prints this JSON Schema’s shape on stdout.

{
  "type": "object",
  "properties": {
    "tenantId": {
      "type": "string"
    },
    "provider": {
      "type": "string"
    },
    "events": {
      "type": "array",
      "items": {
        "type": "object",
        "properties": {
          "eventId": {
            "type": "string"
          },
          "type": {
            "type": "string"
          },
          "receivedAt": {
            "type": "string"
          },
          "injectionSuspected": {
            "type": "boolean"
          }
        },
        "required": [
          "eventId",
          "type",
          "receivedAt",
          "injectionSuspected"
        ],
        "additionalProperties": false
      }
    }
  },
  "required": [
    "tenantId",
    "provider",
    "events"
  ],
  "additionalProperties": false
}

See exit codes for the status the process returns.