What’s supported
Supported actions
The Stripe connector supports:- Read Actions, including full historic backfill.
- Write Actions.
- Proxy Actions, using the base URL
https://api.stripe.com.
Supported Objects
Note: In theory, nested fields can be used with all Stripe objects. However, the objects marked as supporting nested fields in the tables also enable automatic expansion of related data via Stripe’s expand feature. For those objects, the connector can fetch extra fields that are not returned by default, and surface them. Field example for objectThe Stripe connector supports reading and writing to and from the following objects:balance_transactions:"$['source']['payment_intent']['currency']".
| Object | Read | Write | Nested Field |
|---|
Treasury API
The Stripe connector supports reading and writing to and from the following Treasury API objects:| Object | Read | Write | Nested Field |
|---|
Example integration
For an example manifest file of a Stripe integration, visit our samples repo on Github.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 Stripe:- Create a manifest file like the example.
- Deploy it using the amp CLI.
- Embed the InstallIntegration UI component. The UI component will prompt the customer for an API key.
- 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.