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 2ememain location.
t2ememain_api.png

2ememain

Create a 2ememain Destination​

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

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

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

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

    Create Resource

    This endpoint template allows you to create a new resource of a specific type in your 2ememain account using records from a Nexset. Use this template when you need to automatically create resources such as advertisements, listings, or other 2ememain resources based on data from your Nexla flows.

    • Enter the Resource Type in the Resource Type field. This should be the type of 2ememain resources you want to create (e.g., advertisements, listings, etc.). The Resource Type determines which type of resources will be created.
    • This endpoint sends data as JSON in the request body to create new resources in your 2ememain account. Each record from your Nexset will be sent as a separate API request to create a new resource. The request body should contain the resource data in the format required by the 2ememain API for the specific resource type.

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

    The Resource Type determines which type of resources will be created. The resource structure must match the 2ememain API's expected format for the specific resource type. For detailed information about resource creation, request body formats, and available resource properties, see the 2ememain API documentation.

Configure Manually​

2ememain destinations can be manually configured to send data to any valid 2ememain 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 2ememain 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 2ememain API from the Method pulldown menu. 2ememain API typically uses POST method for creating resources.

Data Format​

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

API Endpoint URL​

  1. Enter the URL of the 2ememain API endpoint to which data will be sent in the URL field. This should be the complete URL to your 2ememain endpoint (e.g., https://api.marktplaats.nl/v1/advertisements, https://api.marktplaats.nl/v1/listings). Include any required path parameters in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. The 2ememain API endpoint URL should include the API base URL (https://api.marktplaats.nl/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 2ememain API. The request body should contain the resource data formatted as JSON, with field names matching the 2ememain 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 2ememain API's expected format for the specific resource you're creating (advertisements, listings, etc.). 2ememain API uses specific structures for different resources. For detailed information about request body formats, available endpoints, and resource structures, see the 2ememain 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.