Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Paddle Events (BYOK) — connector documentation

  • MCP endpoint: https://byok-paddle-events.connectorbay.com/mcp
  • REST API: POST https://byok-paddle-events.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-paddle-events.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Paddle Events Paddle Billing API key (live environment; sandbox keys use a different host and do not work here), sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-paddle-events.connectorbay.com/health · Tool schemas: https://byok-paddle-events.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-paddle-events · agent@connectorbay.com

What Paddle Events (BYOK) is for

Paddle Events (BYOK) lets an AI assistant read your own Paddle Events data through the Paddle Events API with a key you supply (Paddle Billing API key (live environment; sandbox keys use a different host and do not work here)). Read-only: 6 tools (list_event_types, list_events, list_notification_settings, list_notifications, list_notification_logs, get_paddle_ip_addresses). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.paddle.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Paddle Events. Paddle Events and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which event types can a Paddle notification destination subscribe to?"
  • "What events did my Paddle account generate lately?"
  • "Which Paddle notification destinations are active?"
  • "Which Paddle webhook notifications failed to deliver?"
  • "Why did Paddle notification ntf_01abc fail to deliver?"
  • "Which IP addresses does Paddle send webhooks from?"

What it does

  • list_event_types: List the Paddle event types you can subscribe to (such as subscription.created), with group and available API versions.
  • list_events: List events that happened in your Paddle account, newest first, with event id, type and time. The event payload (customer data) is not returned.
  • list_notification_settings: List notification destinations (webhooks and email) with type, destination, active flag, subscribed events and API version. Signing secrets are not returned.
  • list_notifications: List notifications Paddle sent to your destinations with type, delivery status, attempts and times. Timestamps are RFC 3339. The payload is not returned.
  • list_notification_logs: List the delivery attempts of one Paddle notification with response code and time. Response bodies are not returned.
  • get_paddle_ip_addresses: Get the IP address ranges Paddle sends webhooks from, to allow-list on your server.

BYOK key

You bring your own Paddle Events Paddle Billing API key (live environment; sandbox keys use a different host and do not work here) (https://vendors.paddle.com/authentication-v2). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.paddle.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Paddle Events API (api.paddle.com) with a BYOK key; documentation: https://developer.paddle.com/api-reference/events/list-events. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Paddle Events. Paddle Events and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Paddle Events account.

Built for: Worldwide. Languages: English.