Skip to main content

Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Stripe location.
stripe_api.png

Stripe

Create a Stripe Destination​

  1. Click the + icon on the Nexset that will be sent to the Stripe destination, and select the Send to Destination option from the menu.

  2. Select the Stripe connector from the list of available destination connectors. Then, select the credential that will be used to connect to your Stripe account, and click Next; or, create a new Stripe credential for use in this flow.

  3. In Nexla, Stripe destinations can be created using pre-built endpoint templates, which expedite destination setup for common Stripe endpoints. Each template is designed specifically for the corresponding Stripe endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Stripe destinations can also be configured manually, allowing you to send data to Stripe endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Stripe endpoints. Each template is designed specifically for the corresponding Stripe endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Add Records of Type

    This endpoint template allows you to create new records of a specific type in your Stripe account using records from a Nexset. Use this template when you need to automatically create charges, customers, products, subscriptions, invoices, or other Stripe resources based on data from your Nexla flows.

    • Enter the Resource Type in the Resource Type field. This should be the type of Stripe records you want to create (e.g., charges, customers, products, subscriptions, invoices, etc.). The Resource Type determines which type of records will be created. Check out the documentation URL for more details on record schema.
    • This endpoint sends data as JSON in the request body to create new records in your Stripe account. Each record from your Nexset will be sent as a separate API request to create a new record. The request body should contain the record data in the format required by the Stripe API for the specific resource type.

    This endpoint sends data as JSON in the request body to create new records in your Stripe account. Each record from your Nexset will be sent as a separate API request to create a new record. The request body should contain the record data in the format required by the Stripe API for the specific resource type, including all required fields and optional fields as needed.

    The Resource Type can be selected from available options (e.g., charges, customers, products, subscriptions, invoices, etc.). The record structure must match the Stripe API's expected format for the specific resource type. Check out the documentation URL for more details on record schema and required fields.

    For detailed information about record creation, request body formats, and available resource properties, see the Stripe API Documentation.

Configure Manually​

Stripe destinations can be manually configured to send data to any valid Stripe API endpoint. Manual configuration provides maximum flexibility for accessing endpoints not covered by pre-built templates or when you need custom API configurations.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Stripe API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Stripe API from the Method pulldown menu. Stripe API typically uses POST method for creating resources.

Data Format​

  1. Select the format in which the Nexset data will be sent to the Stripe API from the Content Format pulldown menu. Stripe API expects JSON format for all requests.

API Endpoint URL​

  1. Enter the URL of the Stripe API endpoint to which data will be sent in the URL field. This should be the complete URL to your Stripe endpoint (e.g., https://api.stripe.com/v1/charges, https://api.stripe.com/v1/customers). Include any required path parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The Stripe API endpoint URL should include the API base URL (https://api.stripe.com/v1/) and point to the endpoint where you want to create resources. The endpoint URL should include the appropriate resource path. You can test the endpoint using the Test button after configuring the URL.

Request Body​

  1. Configure the request body that will be sent to the Stripe API. The request body should contain the resource data formatted as JSON, with field names matching the Stripe API's expected structure. The request body format is typically {message.json} to send the entire Nexset data as JSON, or you can construct a custom JSON structure with specific field mappings.

The request body must be valid JSON and must match the Stripe API's expected format for the specific resource you're creating (charges, customers, products, etc.). Stripe API uses specific structures for different resources. Ensure your data includes all required fields for the resource type. For detailed information about request body formats, available endpoints, and resource structures, see the Stripe API Documentation.

Save the Destination​

  1. Once all of the relevant steps in the above sections have been completed, click the Next button to proceed with the rest of the data flow configuration, or click Save to save the destination configuration for later use.