Korely Events API

The Events API from Korely — 1 operation(s) for events.

GitHub OpenAPI

Operations 1

GET /v1/events List Events #

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/korely-ai:korely-ai-events-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. By signing up you are subscribing to the APIs.io and API Evangelist newsletters — you can unsubscribe from any issue. See our Privacy Policy and Terms.

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

OpenAPI Specification

korely-ai-events-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Korely Ai Events API
  version: 1.0.21
  description: 'Operations tagged Events across 2 of this provider''s published API definitions: korely-ai-agent-openapi.json, korely-ai-openapi.json. Each path carries the servers of the definition it was published in.'
servers:
- url: https://api.korely.ai
  description: EU (Helsinki)
tags:
- name: Events
paths:
  /v1/events:
    get:
      tags:
      - Events
      summary: List Events
      description: 'Which writes have finished being processed.


        A write returns as soon as the memory is stored, then fact extraction runs

        behind it. Without this endpoint a developer polls blind: they cannot tell

        "extraction has not finished" from "there was nothing to extract", which is

        the first confusing thing anyone hits when building on us.


        `events` are the newest writes, newest first; `status` filters them before

        `limit` is applied, so `?status=error` returns the most recent errors

        however many ready writes came after them.


        `processing` in the response is how many writes of this key''s project (of

        `user_id`, when given) are still in flight, counted over all of them, so a

        batch import can wait on one number instead of walking every id. It ignores

        `status` and `limit`.


        No webhook announces that a write''s extraction finished: `memory.created`

        is sent when the memory is stored, before its facts, and

        `GET /admin/webhooks/events` lists the events there are. Waiting for the

        facts is polling this, or reading the memory again.'
      operationId: list_events_v1_events_get
      security:
      - HTTPBearer: []
      parameters:
      - name: user_id
        in: query
        required: false
        schema:
          anyOf:
          - type: string
            maxLength: 255
          - type: 'null'
          description: Filter to one end user.
          title: User Id
        description: Filter to one end user.
      - name: status
        in: query
        required: false
        schema:
          anyOf:
          - type: string
            pattern: ^(processing|ready|error)$
          - type: 'null'
          description: Filter to one processing state.
          title: Status
        description: Filter to one processing state.
      - name: limit
        in: query
        required: false
        schema:
          type: integer
          maximum: 200
          minimum: 1
          default: 50
          title: Limit
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EventsResponse'
        '401':
          description: '`invalid_key`: the `Authorization: Bearer` key is missing, unknown, revoked or expired.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '403':
          description: '`forbidden`: the key lacks the scope this operation needs; `message` names it.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '422':
          description: '`invalid_request`: the body, a query parameter or a path parameter is malformed (`detail` lists the first 20 fields that failed, `message` names the first and counts them all), or the endpoint refuses a value (an empty content, an unreadable timestamp, a NUL byte or a lone UTF-16 surrogate anywhere in the request, a moment that cannot be stored, which is any but from 0001-01-02 to 9999-12-30, in UTC; `detail` is a sentence or `{code, message}`).'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '429':
          description: '`rate_limit_exceeded`: past the request ceiling, the per-minute one set on this install (`RATE_LIMIT_PER_MINUTE`) or, on the hosted service, the plan''s minute, hour or day; `message` names the window and `Retry-After` the seconds until it resets. On this service also `quota_exceeded`: the plan''s queries of the month are spent (`limit`, `used`, `resets_at`, and no `Retry-After`: a retry fails until `resets_at` or a bigger plan).'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '500':
          description: '`internal_error`: the server failed on this request; `message` holds no detail of it.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
        '503':
          description: 'A dependency did not answer: the database while the key was checked (`unavailable`, see `Retry-After`), or the one `code` names. Nothing was written; retry. Also `unavailable` when the request waited more than 5 s for another change to the same records (an erasure under way, for example) or its statement ran past 60 s; see `Retry-After`.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ApiError'
components:
  schemas:
    ErrorCode:
      properties:
        code:
          type: string
          title: Code
          description: Stable, machine-readable reason, e.g. `not_found`, `stale_write`, `invalid_request`, `search_unavailable`. Branch on this, never on `message`.
          examples:
          - not_found
        message:
          type: string
          title: Message
          description: What went wrong, for a person to read. Wording may change.
      type: object
      required:
      - code
      - message
      title: ErrorCode
      description: A refusal with a stable reason.
    EventsResponse:
      properties:
        events:
          items:
            $ref: '#/components/schemas/MemoryEvent'
          type: array
          title: Events
        processing:
          type: integer
          title: Processing
          description: Writes of this key's project (of `user_id`, when given) still in flight, counted over all of them. Independent of `status` and `limit`.
      type: object
      required:
      - events
      - processing
      title: EventsResponse
    MemoryEvent:
      properties:
        memory_id:
          type: string
          title: Memory Id
        user_id:
          anyOf:
          - type: string
          - type: 'null'
          title: User Id
        agent_id:
          anyOf:
          - type: string
          - type: 'null'
          title: Agent Id
        status:
          type: string
          title: Status
        created_at:
          anyOf:
          - type: string
          - type: 'null'
          title: Created At
      type: object
      required:
      - memory_id
      - user_id
      - agent_id
      - status
      - created_at
      title: MemoryEvent
    ApiError:
      properties:
        detail:
          anyOf:
          - type: string
          - $ref: '#/components/schemas/ErrorCode'
          - items:
              $ref: '#/components/schemas/ValidationIssue'
            type: array
          title: Detail
          description: 'As this install has always sent it: a sentence; or `{code, message}` where the endpoint names the reason; or, on a 422 from validation, the list of fields that failed.'
        code:
          type: string
          title: Code
          description: 'Stable, machine-readable reason, the same names as the hosted API: `invalid_key`, `forbidden`, `not_found`, `stale_write`, `invalid_request`, `identity_required` (a write with neither user_id nor agent_id), `rate_limit_exceeded`, `search_unavailable`, `model_unavailable`, `service_paused`, `internal_error`... When `detail` is `{code, message}` it is that code. Branch on this, never on `message`.'
          examples:
          - not_found
        message:
          type: string
          title: Message
          description: 'What went wrong, for a person to read: the sentence, the message of `detail`, or the first field that failed validation. Wording may change.'
        current_fact_id:
          anyOf:
          - type: string
          - type: 'null'
          title: Current Fact Id
          description: '`fact_not_current`: the fact in force to correct instead, null when nothing took the fact''s place. Absent on every other refusal.'
      type: object
      required:
      - detail
      - code
      - message
      title: ApiError
      description: The body of every answer that is not a success, whatever the status.
    ValidationIssue:
      properties:
        type:
          type: string
          title: Type
          description: What kind of failure, e.g. `missing`, `extra_forbidden`, `string_too_long`, `invalid_namespace_id`.
        loc:
          items:
            anyOf:
            - type: string
            - type: integer
          type: array
          title: Loc
          description: 'Where: `body`, `query` or `path`, then the field, e.g. ["body", "memories", 0, "user_id"].'
        msg:
          type: string
          title: Msg
          description: What is wrong with it, for a person to read.
        ctx:
          anyOf:
          - additionalProperties: true
            type: object
          - type: 'null'
          title: Ctx
          description: The limit that was crossed, when there is one.
      type: object
      required:
      - type
      - loc
      - msg
      title: ValidationIssue
      description: One field that failed validation. The value sent is never echoed back.
  securitySchemes:
    HTTPBearer:
      type: http
      scheme: bearer
    bearerAuth:
      type: http
      scheme: bearer
      description: Your kor_live_ API key.
x-refined-from:
- korely-ai-agent-openapi.json
- korely-ai-openapi.json