Skip to content
Changelog

Report a bug

Payhere (UK) integration: operations for AI agents

Payhere (UK) connects to Type.com as an integration. This page lists the 15 operations documented for Claude and Codex in Type.com: 10 read, 3 write, 2 destructive.

About Payhere (UK)

Payhere is a UK payments tool for selling, invoicing and collecting recurring payments online through Stripe, with payment links, plans and customer records.

Categories: Commerce & Payments

How to connect Payhere (UK) to Type.com

Access
Organization connection: one shared account for the workspace.
MCP
This integration is not available through Type’s MCP server. It remains available in Type.

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

Documented operations

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

  • Read

    GET /api/v1/current_company

    Fetch the company information for currently authenticated user

    GET /api/v1/current_company

  • Read

    GET /api/v1/current_company/stats

    Fetch payment stats for last 30 days. Comparison fields are 30-60days to give a comparison value from last month.

    GET /api/v1/current_company/stats

  • Read

    GET /api/v1/customers/:id

    Fetch a customer by ID, this will also pull down their subscriptions and payment history.

    GET /api/v1/customers/:id

  • Read

    GET /api/v1/customers

    List all of your customers, ordered chronologically, most recent first.

    GET /api/v1/customers

  • Read

    GET /api/v1/payments/:id

    Fetch a payment by ID

    GET /api/v1/payments/:id

  • Read

    GET /api/v1/payments

    List all of your payments, ordered chronologically, most recent first.

    GET /api/v1/payments

  • Read

    GET /api/v1/plans

    List all of your plans.

    GET /api/v1/plans

  • Read

    GET /api/v1/subscriptions/:id

    Fetch a subscription by ID, this will also pull down the customer and payments.

    GET /api/v1/subscriptions/:id

  • Read

    GET /api/v1/subscriptions

    List all of your subscriptions, ordered chronologically, most recent payment first.

    GET /api/v1/subscriptions

  • Read

    GET /api/v1/user

    Fetch info on the currently authenticated user

    GET /api/v1/user

  • Write

    PUT /api/v1/current_company

    Update the company information for currently authenticated user

    PUT /api/v1/current_company

  • Write

    POST /api/v1/plans

    Create a new plan.

    POST /api/v1/plans

  • Write

    PUT /api/v1/plans/:id

    Update a plan.

    PUT /api/v1/plans/:id

  • Destructive

    POST /api/v1/refunds

    Refund all or part of a customer payment; this moves funds.

    POST /api/v1/refunds

  • Destructive

    DELETE /api/v1/subscriptions/:id

    Cancel future payments; the subscription remains active until the current period ends.

    DELETE /api/v1/subscriptions/:id

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

Reference date: October 28, 2026. Payhere (UK) API docs.