Skip to content
Changelog

Report a bug

Keen.io integration: operations for AI agents

Keen.io connects to Type.com as an integration. This page lists the 23 operations documented for Claude and Codex in Type.com: 11 read, 7 write, 5 destructive.

About Keen.io

Keen.io is an embedded analytics API that enables developers to collect, analyze, and visualize event data seamlessly.

Categories: Analytics & Data

How to connect Keen.io to Type.com

Access
Organization connection: one shared account for the workspace.

To add the connection, follow the steps in Space connections.

Documented operations

23 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.

23 operations listed.

Events, saved queries and access keys

  • Read

    Inspect collections

    Read schema information for project event collections.

    GET /3.0/projects/{project_id}/events

  • Read

    Inspect collection

    Read event collection schema when authenticated using a Read Key.

    GET /3.0/projects/{project_id}/events/{collection}

  • Read

    Inspect property

    Read schema information for one collection property.

    GET /3.0/projects/{project_id}/events/{collection}/properties/{property}

  • Read

    Get saved query results

    Run/read results for a saved query.

    GET /3.0/projects/{project_id}/queries/saved/{query_name}/result

  • Read

    List saved definitions

    Read all saved query definitions.

    GET /3.0/projects/{project_id}/queries/saved

  • Read

    Get saved definition

    Read a saved query definition.

    GET /3.0/projects/{project_id}/queries/saved/{query_name}

  • Read

    List access keys

    Read project access-key records using pagination/name filters.

    GET /3.0/projects/{project_id}/keys

  • Read

    Get access key

    Read a specific access-key record.

    GET /3.0/projects/{project_id}/keys/{custom_key}

  • Write

    Record multiple events

    Record batches of events across collections.

    POST /3.0/projects/{project_id}/events

  • Write

    Record event

    Record a JSON event in the collection.

    POST /3.0/projects/{project_id}/events/{collection}

  • Write

    Record event via GET beacon

    Record an event from URL/base64-encoded data with a Write Key. This GET mutates data and must not be treated as a read.

    GET /3.0/projects/{project_id}/events/{collection}?data={encoded_data}

  • Write

    Update events

    Apply property_updates to events matching the provided selection.

    PUT /3.0/projects/{project_id}/events/{collection}

  • Write

    Create or update saved query

    Save a query definition; refresh_rate controls caching.

    PUT /3.0/projects/{project_id}/queries/saved/{query_name}

  • Write

    Create access key

    Create a scoped Access Key for the project.

    POST /3.0/projects/{project_id}/keys

  • Write

    Restore access key

    Restore an access key that was revoked.

    POST /3.0/projects/{project_id}/keys/{custom_key}/unrevoke

  • Destructive

    Delete collection or matching events

    Delete the collection or events matching supplied filters/timeframe; destructive scope depends on supplied query parameters.

    DELETE /3.0/projects/{project_id}/events/{collection}

  • Destructive

    Delete property

    Remove a property from an event collection.

    DELETE /3.0/projects/{project_id}/events/{collection}/properties/{property}

  • Destructive

    Delete saved query

    Remove a saved query definition.

    DELETE /3.0/projects/{project_id}/queries/saved/{query_name}

  • Destructive

    Revoke access key

    Disable an access key.

    POST /3.0/projects/{project_id}/keys/{custom_key}/revoke

  • Destructive

    Delete access key

    Permanently remove an access key.

    DELETE /3.0/projects/{project_id}/keys/{custom_key}

Analytics queries

  • Read

    Count matching events

    Return the number of events matching event_collection and optional filters/timeframe; HEAD returns response headers.

    GET /3.0/projects/{project_id}/queries/count

  • Read

    Count matching events

    Return the number of events matching event_collection and optional filters/timeframe; HEAD returns response headers.

    HEAD /3.0/projects/{project_id}/queries/count

  • Read

    Count matching events

    Return the number of events matching event_collection and optional filters/timeframe; HEAD returns response headers.

    POST /3.0/projects/{project_id}/queries/count

See How connections work for access and permissions, or browse all integrations.