Skip to content
Changelog

Report a bug

Pushover integration: operations for AI agents

Pushover connects to Type.com as an integration. This page lists the 31 operations documented for Claude and Codex in Type.com: 11 read, 12 write, 8 destructive.

About Pushover

Pushover is a service that enables real-time notifications to your devices through simple API integration.

Categories: Email & Messaging

How to connect Pushover to Type.com

Access
Organization connection: one shared account for the workspace.

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

Documented operations

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

31 operations listed.

Message API

  • Read

    List notification sounds

    Application-token sound lookup, not a general file/audio upload capability.

    GET /1/sounds.json

  • Read

    Get application message limits

    Reads application quota/billing-cycle metadata using application token; no purchase or quota mutation.

    GET /1/apps/limits.json

  • Read

    Validate user or group destination

    Semantic validation read over POST requires full Type raw method access. Validation does not send a notification or establish target-user consent.

    POST /1/users/validate.json

  • Write

    Send push notification

    Application token plus target user/group key; can send to device/group, HTML, URL, timestamp, sounds and optional attachments. Attachment multipart/binary transport is not implemented by raw JSON/form.

    POST /1/messages.json

  • Write

    Send emergency-priority notification

    Named payload capability: priority=2 with retry and expire produces repeated notifications until acknowledgment/expiry. Shares message route, not another endpoint; callbacks/receipt polling are separate.

    POST /1/messages.json

Receipt API

  • Read

    Get emergency receipt status

    Application token plus receipt; poll no faster than every 5 seconds and only within documented receipt retention. Reading status does not cancel/acknowledge retries.

    GET /1/receipts/{receipt}.json

  • Destructive

    Cancel emergency notification retries

    Stops retries for the specified emergency receipt; application token required.

    POST /1/receipts/{receipt}/cancel.json

  • Destructive

    Cancel emergency retries by tag

    Cancels all active emergency messages matching tag; not merely a receipt search. Application token required.

    POST /1/receipts/cancel_by_tag/{tag}.json

Groups API

  • Read

    List delivery groups

    Application token reads account/team-owned groups; group keys are separate identifiers.

    GET /1/groups.json

  • Read

    Get group and members

    Requires group key and owning account/team application token. Returns members and device/disabled metadata.

    GET /1/groups/{group}.json

  • Write

    Create delivery group

    Application token for owning account/team plus name. Creates routing group, not target-user credentials.

    POST /1/groups.json

  • Write

    Add user to group

    Requires known user key; optional device restricts routing. Account/team ownership required.

    POST /1/groups/{group}/add_user.json

  • Write

    Enable group delivery to user

    Resumes notifications to an existing member/device; does not create a new user license.

    POST /1/groups/{group}/enable_user.json

  • Write

    Rename group

    Application token on owning account/team; group name uniqueness restrictions apply.

    POST /1/groups/{group}/rename.json

  • Destructive

    Remove user from group

    Removes matching user/device membership and future group delivery, not their Pushover account.

    POST /1/groups/{group}/remove_user.json

  • Destructive

    Disable group delivery to user

    Temporarily stops notifications to matching group member/device; routing-access removal maximum effect.

    POST /1/groups/{group}/disable_user.json

Glances API

  • Write

    Update a device widget

    Application token plus user key; updates widgets, distinct from message delivery. Device targeting and string/count/percentage/progress fields follow source.

    POST /1/glances.json

Subscriptions API

  • Write

    Migrate user to subscription

    Application token plus subscription code/user key; migration changes destination subscription. Does not create a generic OAuth grant.

    POST /1/subscriptions/migrate.json

Teams API

  • Read

    Get Team information

    Requires Team API token, not application API token; accesses team users/admin metadata.

    GET /1/teams.json

  • Write

    Add Team user

    Requires Team API token; invitation/account/password/license flags have documented user-management effects. No team administrator authority inferred.

    POST /1/teams/add_user.json

  • Destructive

    Revoke Team invitation

    Revokes pending invitation for an email; Team token, not application token.

    POST /1/teams/revoke_invitation.json

  • Destructive

    Remove Team user

    Removes Team membership and team delivery-group membership, not user account; at least one administrator must remain.

    POST /1/teams/remove_user.json

Licensing API

  • Read

    Get remaining license credits

    Reads application license credit balance without assigning a license; no purchase or credit mutation.

    GET /1/licenses.json

  • Destructive

    Permanently assign a paid license

    Consumes pre-paid license credit; assignment cannot be revoked/reassigned and purchased credits are nonrefundable. Email assignment deducts credit even while pending signup. One platform/license per request. No automatic retries before human error review.

    POST /1/licenses/assign.json

Open Client

  • Read

    Download pending Open Client messages

    Requires user session secret and device_id; distinct from application-token POSTsend on samepath. Download alone does not acknowledge/delete messages.

    GET /1/messages.json

  • Write

    Open Client user login

    Separate user email/password login can return session secret and require two-factor challenge. Not an application-token API or configured Type login adapter; no login performed.

    POST /1/users/login.json

  • Write

    Register Open Client device

    Requires user session secret, device name and os=O; creates licensed Desktop/Open Client device, not a message destination from app token alone.

    POST /1/devices.json

  • Write

    Acknowledge emergency message as client

    Requires user session secret, not application token. Acknowledges receipt and stops repeated notification behavior; no implicit recipient identity.

    POST /1/receipts/{receipt}/acknowledge.json

  • Destructive

    Delete downloaded Open Client messages

    Session secret plus highest downloaded message ID removes queued messages through that ID; string IDs avoid loss of integer precision. Not a read-only checkpoint.

    POST /1/devices/{device_id}/update_highest_message.json

Open Client assets

  • Read

    Download application icon for client

    Documented dynamic icon name; binary asset caching required. Not a JSON API response or Type attachment proof.

    GET /icons/{icon}.png

  • Read

    Download notification sound for client

    Documented sound identifier; binary audio caching required. Not general device storage/audio access.

    GET /sounds/{sound}.mp3

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