Skip to content
Changelog

Report a bug

Emailable integration: operations for AI agents

Emailable connects to Type.com as an integration. This page lists the 11 operations documented for Claude and Codex in Type.com: 4 read, 6 write, 1 destructive.

About Emailable

Emailable vendor API references, subject to account permissions.

Categories: Email & Messaging

How to connect Emailable to Type.com

Access
Organization connection: one shared account for the workspace.

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

Documented operations

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

Email verification

  • Read

    Verify an email

    Verify an email. Verifies one email and consumes documented usage on live keys. Retry the same timed-out verification within five minutes; later requests count again. A metered read is not a deletion.

    GET /v1/verify

  • Read

    Verify an email via POST (rate-table reference)

    Verify an email via POST (rate-table reference). POST is explicitly listed in the shared rate-limit table. Detailed endpoint examples show GET; exact POST field binding is not separately established. Do not treat the GET JSON-body example as a demonstrated POST request.

    POST /v1/verify

  • Read

    Get a batch status and results

    Get a batch status and results. Retrieves status, completed/partial results or download_file output. Partial output is limited to batches of at most 1,000 emails; billing failures may return 402.

    GET /v1/batch

  • Read

    Get account information

    Get account information. Retrieves account email and remaining credits; public API keys cannot use this endpoint.

    GET /v1/account

  • Write

    Verify a batch of emails

    Verify a batch of emails. Creates a verification batch of up to 50,000 emails (larger enterprise batches by support). All parameters belong in the body, not query. Optional callback can be delivered repeatedly until acknowledged.

    POST /v1/batch

OAuth

  • Write

    Authorize an OAuth application

    Authorize an OAuth application. Browser consent flow can issue an authorization code and grant application access after user approval. It is not a JSON data lookup.

    GET /oauth/authorize

  • Write

    Create OAuth device authorization codes

    Create OAuth device authorization codes. Creates device_code/user_code and user consent URLs. Device grant must be enabled for the app; respect returned expiry and polling interval.

    POST /oauth/device/code

  • Write

    Exchange an authorization code

    Exchange an authorization code. Issues access/refresh tokens from a single-use code that expires in ten minutes; client secret and redirect URI required, code_verifier conditional on PKCE.

    POST /oauth/token

  • Write

    Poll OAuth device authorization

    Poll OAuth device authorization. Can issue tokens once consent is approved; device grant does not use client_secret. Handle authorization_pending, slow_down (+5 seconds), denied and expired states.

    POST /oauth/token

  • Write

    Refresh OAuth credentials

    Refresh OAuth credentials. Requests a new access token and a new refresh token using the prior refresh token and client credentials. No undocumented old-token invalidation is asserted.

    POST /oauth/token

  • Destructive

    Revoke an OAuth access token

    Revoke an OAuth access token. Revokes the specified access token so it can no longer authenticate requests; returns an empty JSON response.

    POST /oauth/revoke

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