Payhere for AI agents

Agents read Payhere at once. Changes and sends are held for a person's approval by default.

About Payhere

Easy payment links for accepting online payments

What an agent can do in Payhere

Every Payhere action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.

Runs at once (reads)

Looks things up in Payhere without asking first. 8 actions.

  • Get Current CompanyTool to fetch company information for the currently authenticated user. Use when you need to retrieve comprehensive company details including identity, configuration, integration status, and associate
  • Get Current Company StatsTool to fetch payment statistics for the last 30 days with comparison data from the preceding 30-day period (30-60 days ago). Use when you need to analyze recent payment trends, subscriber growth, or
  • Get UserTool to fetch information on the currently authenticated user. Use when you need to retrieve details about the logged-in user.
  • List CustomersTool to list all customers from Payhere, ordered chronologically with most recent first. Use when you need to retrieve customer records, browse customers, or access customer information. Supports pagi
  • List REST HooksTool to list all active REST hooks subscriptions for the authenticated company. Use when you need to view all currently registered webhook listeners for your PayHere account.
  • List PaymentsTool to list all payments ordered chronologically, most recent first. Use when you need to retrieve payment history or check payment statuses. Supports pagination with page and per_page parameters.
  • List PlansTool to list all plans in your PayHere account. Use when you need to retrieve and paginate through available plans.
  • List subscriptionsTool to list all subscriptions ordered chronologically by most recent payment first. Use when you need to retrieve subscription data with customer and plan details.

Held for approval by default (changes and sends)

Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 5 actions.

  • Create HookTool to subscribe to a REST hook for receiving webhook events. Use when you need to register a webhook endpoint to receive real-time notifications for payment_received, subscription_cancelled, or subs
  • Create PlanTool to create a new payment plan in PayHere. Use when you need to set up either a recurring subscription or one-off payment plan for accepting payments.
  • Delete HookTool to remove a REST hook listener subscription. Use when you need to stop receiving webhook events for a specific hook.
  • Update Current CompanyTool to update the company information for the currently authenticated user. Use when modifying company details such as name, legal name, address, logo, support email, website, or branding preferences
  • Update PlanTool to update an existing plan's configuration and settings. Use when you need to modify plan properties like name, description, pricing, or other settings for both one-off and subscription plans.

Changes wait in Needs you

Changes and sends in Payhere are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

How approvals work

Payhere questions

Can an agent change data in Payhere on its own?

Not by default. Changes and sends in Payhere are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.

What can an agent read in Payhere?

This connector lists 8 read actions. Reads run at once, without waiting for approval.

How does Payhere connect?

It connects with API key. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.

Bring Payhere to your agents.