Skip to main content

Leapfin 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 Leapfin location.
leapfin.png

Leapfin

Create a Leapfin Destination​

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

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

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

    Leapfin destinations can also be configured manually, allowing you to send data to Leapfin 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 Leapfin endpoints. Each template is designed specifically for the corresponding Leapfin 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 ObjectType

    Add Records of ObjectType

    • Select the object type you want to add records for from the Object Type pulldown menu. Available object types include: Payments, Invoice, Credit, and Tax. The default value is "payments". Check the API documentation URL for more details on object schema and required fields for each object type.
    • The endpoint uses POST requests to https://api.leapfin.com/v1/data/{object_type} where {object_type} is the object type you selected. The endpoint URL is automatically constructed based on your selection.
    • The endpoint sends data from your Nexset as the request body in JSON format. The request body is automatically formatted according to the schema fields and data mapping you configure. Each record in your Nexset will be sent as a JSON object containing the record data to add.
    • This endpoint does not automatically create a data source to track the responses received from the Leapfin API after each call.

    The request body must be properly formatted JSON that matches the Leapfin API specification for the selected object type. The endpoint requires API Key authentication, which is handled automatically by your credential configuration. The Content-Type: application/json header is automatically included in requests. The API Key is sent in the X-Api-Key header for all API requests. The request body must contain the required fields for the selected object type. For detailed information about adding records, including required fields, field names, and request formats for each object type, see the Leapfin API documentation.

Configure Manually​

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

With manual configuration, you can also create more complex Leapfin destinations, such as destinations that use custom request headers, different HTTP methods, or custom data formatting.

Content Format​

  1. Select the format in which the Nexset data will be sent to the Leapfin API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call. The Leapfin API typically uses JSON format for request bodies.

API Endpoint URL​

  1. Enter the URL of the Leapfin API endpoint to which you want to send the Nexset data in the URL field. This should be the complete URL including the protocol (https://) and any required path parameters. Leapfin API endpoints typically follow the pattern https://api.leapfin.com/v1/{endpoint_path}.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL. The endpoint requires API Key authentication, which is handled automatically by your credential configuration. The API Key is sent in the X-Api-Key header for all API requests. For detailed information about Leapfin API endpoints, authentication, and available APIs, see the Leapfin API documentation.