Skip to content
Changelog

Report a bug

Pushbullet integration: operations for AI agents

Pushbullet connects to Type.com as an integration. This page lists the 30 operations documented for Claude and Codex in Type.com: 6 read, 16 write, 8 destructive.

About Pushbullet

Pushbullet enables seamless sharing of notifications and files across devices.

Categories: Email & Messaging

How to connect Pushbullet to Type.com

Access
Organization connection: one shared account for the workspace.

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

Documented operations

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

30 operations listed.

Chat

  • Read

    List chats

    List chats. Full request/response fields and object definitions are in the contract.

    GET /v2/chats

  • Write

    Create chat

    Create chat. Full request/response fields and object definitions are in the contract.

    POST /v2/chats

  • Write

    Update chat

    Update chat. Full request/response fields and object definitions are in the contract.

    POST /v2/chats/{iden}

  • Destructive

    Delete chat

    Delete chat. Full request/response fields and object definitions are in the contract.

    DELETE /v2/chats/{iden}

Device

  • Read

    List devices

    List devices. Full request/response fields and object definitions are in the contract.

    GET /v2/devices

  • Write

    Create device

    Create device. Full request/response fields and object definitions are in the contract.

    POST /v2/devices

  • Write

    Update device

    Update device. Full request/response fields and object definitions are in the contract.

    POST /v2/devices/{iden}

  • Destructive

    Delete device

    Delete device. Full request/response fields and object definitions are in the contract.

    DELETE /v2/devices/{iden}

Push

  • Read

    List pushes

    List pushes. Full request/response fields and object definitions are in the contract.

    GET /v2/pushes

  • Write

    Create push

    Create push. Full request/response fields and object definitions are in the contract.

    POST /v2/pushes

  • Write

    Update push

    Update push. Full request/response fields and object definitions are in the contract.

    POST /v2/pushes/{iden}

  • Destructive

    Delete push

    Delete push. Full request/response fields and object definitions are in the contract.

    DELETE /v2/pushes/{iden}

  • Destructive

    Delete all pushes

    Delete all pushes. Full request/response fields and object definitions are in the contract.

    DELETE /v2/pushes

Channel

  • Write

    Create channel

    Create channel. Full request/response fields and object definitions are in the contract.

    POST /v2/channels

Subscription

  • Read

    List subscriptions

    List subscriptions. Full request/response fields and object definitions are in the contract.

    GET /v2/subscriptions

  • Read

    Channel info

    Channel info. Full request/response fields and object definitions are in the contract.

    GET /v2/channel-info

  • Write

    Create subscription

    Create subscription. Full request/response fields and object definitions are in the contract.

    POST /v2/subscriptions

  • Write

    Update subscription

    Update subscription. Full request/response fields and object definitions are in the contract.

    POST /v2/subscriptions/{iden}

  • Destructive

    Delete subscription

    Delete subscription. Full request/response fields and object definitions are in the contract.

    DELETE /v2/subscriptions/{iden}

Text

  • Destructive

    Create text

    Create text. Full request/response fields and object definitions are in the contract.

    POST /v2/texts

  • Destructive

    Update text

    Update text. Full request/response fields and object definitions are in the contract.

    POST /v2/texts/{iden}

  • Destructive

    Delete text

    Delete text. Full request/response fields and object definitions are in the contract.

    POST /v2/texts/{iden}

User

  • Read

    Get user

    Get user. Full request/response fields and object definitions are in the contract.

    GET /v2/users/me

Upload

  • Write

    Upload request

    Upload request. Full request/response fields and object definitions are in the contract.

    POST /v2/upload-request

Ephemeral payloads

  • Write

    Send arbitrary ephemeral

    JSON-only payload delivered directly to paired clients; not stored reliably and no tickle notification. Requires active client stream, not a Type WebSocket subscription.

    POST /v2/ephemerals

  • Write

    Legacy ephemeral SMS (deprecated)

    Explicitly deprecated; prefer Create Text. Requires Android device SMS permission and source user/device identity; token alone is not a universal SMS gateway.

    POST /v2/ephemerals

  • Write

    Mirror device notification

    Named payload push.type=mirror, distinct from generic ephemeral. Requires client/device metadata; Android notification mirror event shape does not prove Type has device permissions.

    POST /v2/ephemerals

  • Write

    Dismiss mirrored notification

    Named payload push.type=dismissal targets package/notification/user identifiers. Dismissal is not deletion of every push or device data.

    POST /v2/ephemerals

  • Write

    Send clipboard content to clients

    Named payload push.type=clip can change paired client clipboard. No client permissions, background stream or E2E encryption granted automatically.

    POST /v2/ephemerals

OAuth application flow

  • Write

    Exchange OAuth authorization code

    Different application-credential contract using client_id/client_secret/code/grant_type, not an ordinary Access-Token resource call. User consent/redirect roundtrip needed; current Type provider has no configured OAuth flow.

    POST /oauth2/token

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