Skip to content
Changelog

Report a bug

Ably integration: operations for AI agents

Ably connects to Type.com as an integration. This page lists the 44 operations documented for Claude and Codex in Type.com: 19 read, 17 write, 8 destructive.

About Ably

Ably is a real-time messaging platform helping developers build live features, including chat and data synchronization, with global scalability and robust reliability for modern applications

Categories: Developer Tools & IT

How to connect Ably to Type.com

Access
Organization connection: one shared account for the workspace.

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

Documented operations

44 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.

44 operations listed.

History

  • Read

    Get message history for a channel

    Get message history for a channel

  • Read

    Get presence history of a channel

    Get presence on a channel

Publishing

  • Write

    Publish a message to a channel

    Publish a message to the specified channel

Status

  • Read

    Get presence of a channel

    Get presence on a channel

  • Read

    Get metadata of a channel

    Get metadata of a channel

  • Read

    Enumerate all active channels of the application

    Enumerate all active channels of the application

Push

  • Read

    List devices registered for receiving push notifications

    List of device details of devices registed for push notifications.

  • Read

    Get a device registration

    Get the full details of a device.

  • Read

    Reset a registered device's update token

    Gets an updated device details object.

  • Read

    List channel subscriptions

    Get a list of push notification subscriptions to channels.

  • Read

    List all channels with at least one subscribed device

    Returns a paginated response of channel names.

  • Write

    Register a device for receiving push notifications

    Register a device’s details, including the information necessary to deliver push notifications to it. Requires "push-admin" capability.

  • Write

    Update a device registration

    Specific attributes of an existing registration can be updated. Only clientId, metadata and push.recipient are mutable.

  • Write

    Subscribe a device to a channel

    Subscribe either a single device or all devices associated with a client ID to receive push notifications from messages sent to a channel.

  • Write

    Publish a push notification to device(s)

    A convenience endpoint to deliver a push notification payload to a single device or set of devices identified by their client identifier.

  • Destructive

    Unregister matching devices for push notifications

    Unregisters devices. All their subscriptions for receiving push notifications through channels will also be deleted.

  • Destructive

    Update a device registration

    Device registrations can be upserted (the existing registration is replaced entirely) with a PUT operation. Only clientId, metadata and push.recipient are mutable.

  • Destructive

    Unregister a single device for push notifications

    Unregisters a single device by its device ID. All its subscriptions for receiving push notifications through channels will also be deleted.

  • Destructive

    Delete a registered device's update token

    Delete a device details object.

Authentication

  • Write

    Request an access token

    This is the means by which clients obtain access tokens to use the service.

Stats

  • Read

    Retrieve usage statistics for an application

    The Ably system can be queried to obtain usage statistics for a given application, and results are provided aggregated across all channels in use in the application in the specified period. Stats may be used to track usage against account quotas.

  • Read

    Get the service time

    This returns the service time in milliseconds since the epoch.

Accounts

  • Read

    Lists account apps

    GET /accounts/{account_id}/apps

  • Write

    Creates an app

    POST /accounts/{account_id}/apps

Apps

  • Read

    Lists app keys

    GET /apps/{app_id}/keys

  • Read

    Lists namespaces

    GET /apps/{app_id}/namespaces

  • Read

    Lists queues

    GET /apps/{app_id}/queues

  • Read

    Lists rules

    GET /apps/{app_id}/rules

  • Read

    Gets a rule using a rule ID

    GET /apps/{app_id}/rules/{rule_id}

  • Write

    Updates an app

    PATCH /apps/{id}

  • Write

    Updates app's APNs info from a .p12 file

    Updates app's APNs info from a .p12 file

  • Write

    Creates a key

    POST /apps/{app_id}/keys

  • Write

    Updates a key

    PATCH /apps/{app_id}/keys/{key_id}

  • Write

    Revokes a key

    POST /apps/{app_id}/keys/{key_id}/revoke

  • Write

    Creates a namespace

    POST /apps/{app_id}/namespaces

  • Write

    Updates a namespace

    PATCH /apps/{app_id}/namespaces/{namespace_id}

  • Write

    Creates a queue

    POST /apps/{app_id}/queues

  • Write

    Creates a rule

    POST /apps/{app_id}/rules

  • Write

    Updates a Rule

    PATCH /apps/{app_id}/rules/{rule_id}

  • Destructive

    Deletes an app

    DELETE /apps/{id}

  • Destructive

    Deletes a namespace

    DELETE /apps/{app_id}/namespaces/{namespace_id}

  • Destructive

    Deletes a queue

    DELETE /apps/{app_id}/queues/{queue_id}

  • Destructive

    Deletes a rule

    DELETE /apps/{app_id}/rules/{rule_id}

Me

  • Read

    Get token details

    GET /me

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