Skip to content
Changelog

Report a bug

Amcards integration: operations for AI agents

Amcards connects to Type.com as an integration. This page lists the 49 operations documented for Claude and Codex in Type.com: 30 read, 12 write, 7 destructive.

About Amcards

AMCards enables users to create personalized greeting cards, automate mailing campaigns, strengthen customer relationships using a convenient online platform for individualized connections

Categories: Marketing & Social

How to connect Amcards to Type.com

Access
Organization connection: one shared account for the workspace.

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

Documented operations

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

49 operations listed.

  • Read

    Read API v1 schema

    Read API v1 resource discovery/schema metadata; this does not create records.

    GET /.api/v1/

  • Read

    Read campaign records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/campaign/

  • Read

    Read campaign schema

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/campaign/schema/

  • Read

    Read campaign details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/campaign/{campaignId}/

  • Read

    Read card records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/card/

  • Read

    Read card details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/card/{cardId}/

  • Read

    Read category records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/category/

  • Read

    Read category schema

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/category/schema/

  • Read

    Read contact records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/contact/

  • Read

    Read contact schema

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/contact/schema/

  • Read

    Search contacts

    Find owned contacts matching the supplied q search term.

    GET /.api/v1/contact/search/

  • Read

    Read contact details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/contact/{contactId}/

  • Read

    Read gift records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/gift/

  • Read

    Read group records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/group/

  • Read

    Read group schema

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/group/schema/

  • Read

    Read group details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/group/{groupId}/

  • Read

    Read mailing records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/mailing/

  • Read

    Read mailing details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/mailing/{mailingId}/

  • Read

    Read payment method records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/paymentmethod/

  • Read

    Read payment method schema

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/paymentmethod/schema/

  • Read

    Read payment method details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/paymentmethod/{paymentMethodToken}/

  • Read

    Read public template records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/publictemplate/

  • Read

    Read quicksend template records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/quicksendtemplate/

  • Read

    Read template records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/template/

  • Read

    Read user records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/user/

  • Read

    Read user schema

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/user/schema/

  • Read

    Read user details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/user/{userId}/

  • Read

    Read wallet records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/wallet/

  • Read

    Read wallet schema

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/wallet/schema/

  • Read

    Read wallet details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    GET /.api/v1/wallet/{walletId}/

  • Write

    Update contact details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    PATCH /.api/v1/contact/{contactId}/

  • Write

    Update group details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    PATCH /.api/v1/group/{groupId}/

  • Write

    Update user details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    PATCH /.api/v1/user/{userId}/

  • Write

    Create contact records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    POST /.api/v1/contact/

  • Write

    Create group records

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    POST /.api/v1/group/

  • Write

    Create encrypted payment method

    Create a payment method using Braintree client-side encrypted number/CVV; requires a vendor-provided CSE key and browser library. Raw card submission is not documented.

    POST /.api/v1/paymentmethod/

  • Write

    Fund an AMcards wallet

    Charge the supplied payment method for the requested amount and create a wallet and credit transaction.

    POST /.api/v1/wallet/

  • Write

    Clone campaign to user

    Copy an existing campaign into the authorized user account.

    POST /campaigns/clone/

  • Write

    Trigger drip campaign

    Start the specified campaign for the supplied recipient; downstream physical mail/gifts and billing may follow.

    POST /campaigns/open-campaign-form/

  • Write

    Send physical card using access token

    Submit a card for delivery using multipart form with access_token or Bearer header; printing/postage and optional gifts cost credit.

    POST /cards/open-card-form-oa/

  • Write

    Send physical card using username/password

    Submit a card for delivery using legacy multipart username/password authentication. This sends physical mail and consumes credit. Configure both username and password for multipart authentication.

    POST /cards/open-card-form/

  • Write

    Send template to multiple recipients

    Schedule a mailing to multiple recipients using a JSON body and Bearer token header; only owned templates and adequate credits are supported.

    POST /cards/open-mailing-form/

  • Destructive

    Delete contact details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    DELETE /.api/v1/contact/{contactId}/

  • Destructive

    Delete group details

    Use the named documented AMcards resource; query filters are parameters, not additional endpoints.

    DELETE /.api/v1/group/{groupId}/

  • Destructive

    Delete payment method details

    Remove the payment method and cancel associated memberships/subscriptions. This has billing and access consequences.

    DELETE /.api/v1/paymentmethod/{paymentMethodToken}/

  • Destructive

    Delete mailing and editable cards

    Delete a mailing; cards and gifts are automatically refunded if not already processed.

    POST /cards/delete-mailing/

  • Destructive

    Cancel editable card by ID

    Permanently cancel the specified editable card and return applicable account credit. JSON and Bearer header required.

    POST /cards/open-cancel-editable-card-by-id-form/

  • Destructive

    Cancel editable cards for contact

    Permanently cancel eligible editable cards associated with the specified contact and return applicable credit. JSON and Bearer header required.

    POST /cards/open-cancel-editable-cards-by-contact-form/

  • Destructive

    Downgrade user to free account

    Reduce the addressed customer account to the free plan through the documented inbound action endpoint.

    POST /user/downgrade-to-free-webhook/

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

Reference date: October 28, 2026. Amcards API docs.