Skip to main content

2dehands 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 2dehands location.
two_2dehands_api.png

2dehands

Create a 2dehands Destination​

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

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

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

2dehands destinations can also be configured manually, allowing you to send data to 2dehands 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 2dehands endpoints. Each template is designed specifically for the corresponding 2dehands 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 creates resources of a selected type from records in a Nexset in your 2dehands account. Use this template when you need to automatically create resources such as advertisements, categories, or users based on data from your Nexla flows.

    • Enter the Resource Type in the Resource type field. This should be the type of resource you want to create (e.g., advertisements, categories, users). The Resource Type determines which type of resource will be created. You can select from the available options or type a custom resource type if needed.
    • This endpoint sends data as JSON in the request body to create new resources. Each record from your Nexset will be sent as a separate API request to create a resource. The request body should contain the resource data in the format required by the 2dehands API, including all required properties for the selected resource type.

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

    The resource structure must match the 2dehands API's expected format. Ensure your resource data includes all required fields for the selected resource type. For detailed information about resource creation, request body formats, and available resource properties, see the 2dehands API documentation.

    Create a transaction

    This endpoint template creates a transaction for an advertisement from records in a Nexset in your 2dehands account. Use this template when you need to automatically create transactions for advertisements based on data from your Nexla flows.

    • Enter the Item ID in the Item id field. This should be the unique identifier of the advertisement for which you want to create a transaction. The Item ID determines which advertisement's transaction will be created. You can find the Item ID by using the "Get resources" endpoint or from your 2dehands dashboard.
    • This endpoint sends data as JSON in the request body to create a new transaction. Each record from your Nexset will be sent as a separate API request to create a transaction. The request body should contain the transaction data in the format required by the 2dehands API, including all required properties for transaction creation.

    This endpoint sends data as JSON in the request body to create a new transaction for an advertisement in your 2dehands account. Each record from your Nexset will be sent as a separate API request to create a transaction. The request body should contain the transaction data in the format required by the 2dehands API, including all required properties for transaction creation.

    The transaction structure must match the 2dehands API's expected format. Ensure your transaction data includes all required fields. The Item ID can be found by using the "Get resources" endpoint or from your 2dehands dashboard. For detailed information about transaction creation, request body formats, and available transaction properties, see the 2dehands API documentation.

Configure Manually​

2dehands destinations can be manually configured to send data to any valid 2dehands API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the 2dehands 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 2dehands API from the Method pulldown menu. The most common methods for 2dehands destinations are:

    • POST: For creating new resources (most common for 2dehands destinations)
    • PUT: For updating existing resources
    • PATCH: For partial updates to existing resources

Data Format​

  1. Select the format in which the Nexset data will be sent to the 2dehands API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call.

The 2dehands APIs typically expect JSON format for most operations. Choose JSON unless you have specific requirements for other formats.

API Endpoint URL​

  1. Enter the URL of the 2dehands API endpoint to which you want to send the Nexset data in the URL field. For update/upsert operations, include the ID of the object to be updated at the end of the URL.

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.

Request Headers​

Optional

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include any headers already present in the credentials. Common headers like Authorization, Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration.

Exclude Attributes from the Call​

Optional

  • If any record attributes in the Nexset should be omitted when sending data to this 2dehands destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

Optional

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Record batching is particularly useful for 2dehands destinations when you need to process large numbers of records efficiently. Batching can help reduce API calls and improve performance.

Response Webhook​

Optional

Nexla can automatically send the response received from the 2dehands API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Response webhooks are particularly useful for 2dehands destinations to track resource creation status, update confirmations, and any error responses from the 2dehands API.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the 2dehands API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the 2dehands API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the 2dehands API using the current settings.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured 2dehands endpoint, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to the 2dehands endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.