Skip to main content

​
What’s supported

​
Supported actions

This connector supports:
  • Read Actions, including full historic backfill. Please note that incremental reading is only supported for transactions. For all other objects, a full read of the Paddle instance will be done per scheduled read.
  • Write Actions.
  • Proxy Actions, using the base URL https://api.paddle.com.

​
Supported objects

The Paddle connector supports reading from the following objects: The Paddle connector supports writing to the following objects:

​
Example integration

For an example manifest file of an Paddle integration, visit our samples repo on Github.

​
Creating an API key

Click here for more information about generating an API key for Paddle.

​
Using the connector

This connector uses API Key auth, which means that you do not need to set up a Provider App before getting started. (Provider apps are only required for providers that use OAuth2 Authorization Code grant type.) To start integrating with Paddle:
  • Create a manifest file using the example.
  • Deploy it using the amp CLI.
  • If you are using Read Actions, create a destination.
  • Embed the InstallIntegration UI component.
  • Start using the connector!
    • If your integration has Read Actions, you’ll start getting webhook messages.
    • If your integration has Write Actions, you can start making API calls to our Write API.
    • If your integration has Proxy Actions, you can start making Proxy API calls.