2dehands

2dehands is an online marketplace that facilitates the buying and selling of a wide range of items including second-hand goods, new products, and services, serving as a popular classified ads platform in Belgium and the Netherlands.

Power end-to-end data operations for your 2dehands API with Nexla. Our bi-directional 2dehands connector is purpose-built for 2dehands, making it simple to ingest data, sync it across systems, and deliver it anywhere — all with no coding required. Nexla turns API-sourced data into ready-to-use, reusable data products and makes it easy to send data to 2dehands or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your 2dehands workflows fast, secure, and fully governed.

Features

Type: API

SourceDestination

• Seamless API Integration: Connect to any endpoint as source or destination without coding, with automatic data product creation
• Visual Composition & Chaining: Build complex integrations using visual templates, chain API calls, and compose workflows with data validation and filtering
• API Proxy: Expose curated slices of your data securely with a secure and customizable API proxy that validates and transforms data on the fly
• Request optimization with intelligent batching, retry, and caching to minimize API calls and costs

Prerequisites

Before creating a 2dehands credential, you need to obtain your Client ID and Client Secret from your 2dehands (Marktplaats) Developer account. 2dehands uses OAuth2 client credentials (2-legged) authentication for all API requests.

To obtain your 2dehands OAuth credentials, follow these steps:

1. Sign in to your 2dehands account using your administrator credentials.

2. Navigate to the 2dehands API documentation or visit the Marktplaats Developer Portal to access API key management.

3. In the 2dehands Developer Portal or API settings, navigate to API Keys, OAuth Applications, or Developer Settings to access your OAuth application management.

4. If you don't have an OAuth application yet, click Create Application or Register Application to create a new OAuth application.

5. Configure your OAuth application settings:

   • Enter a name for the application (e.g., "Nexla Integration")
   • Review and accept the 2dehands API Terms of Service
   • Set the application type to Client Credentials or 2-legged OAuth
   • Click Create or Register to create the application

6. After the application is created, you will see your Client ID and Client Secret. Copy both values immediately, as the Client Secret may not be accessible again after you navigate away from the page.

7. Store both credentials securely, as you will need them to configure your Nexla credential. The Client Secret is sensitive information and should be kept confidential.

The Client ID and Client Secret are used in the OAuth2 client credentials flow to obtain access tokens. These tokens are then used to authenticate your requests to the 2dehands API. If your credentials are compromised, you should immediately revoke them in your 2dehands Developer Portal and generate new ones. For detailed information about obtaining OAuth credentials, API authentication, and available endpoints, refer to the 2dehands API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Client ID	Yes	No	2dehands Client ID
Client Secret	Yes	Yes	2dehands Client Secret

Create a credential in Nexla

1. After selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – 2dehands

2. Enter a name for the credential in the Credential Name field and a short, meaningful description in the Credential Description field.

3. Enter your Client ID in the Client ID field. This is the OAuth2 client identifier you obtained from your 2dehands Developer Portal (API Keys or OAuth Applications). The Client ID is used to identify your application when requesting access tokens.

4. Enter your Client Secret in the Client Secret field. This is the OAuth2 client secret you obtained from your 2dehands Developer Portal. The Client Secret is used together with the Client ID to authenticate your application and obtain access tokens. The Client Secret is sensitive information and must be kept confidential.

   Your 2dehands OAuth credentials (Client ID, Client Secret) can be found in the 2dehands API documentation or your 2dehands Developer Portal under API Keys or OAuth Applications. The Client Secret is sensitive information and must be kept confidential.

   If your credentials are compromised, you should immediately revoke them in your 2dehands Developer Portal and generate new ones. The OAuth credentials provide access to your 2dehands account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

   For detailed information about obtaining OAuth credentials, API authentication, and available endpoints, see the 2dehands API documentation and 2dehands API overview.

5. Click the Save button at the bottom of the overlay. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Then, select the desired flow type from the list, and click the Create button. Select the 2dehands connector tile from the list of available 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.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure data sources to ingest data from common 2dehands endpoints. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable box below.

Get resources

This endpoint template fetches resources of a given type from your 2dehands account. Use this template when you need to retrieve advertisements, categories, users, or other resource types for analysis, reporting, or integration purposes.

• Enter the Resource Type in the Resource type field. This should be the type of resource you want to retrieve (e.g., advertisements, categories, users). The Resource Type determines which type of resource will be retrieved. You can select from the available options: Advertisements, Categories, or Users.

This endpoint returns resources of the specified type from your 2dehands account, including resource IDs, names, descriptions, and other resource metadata. The Resource Type determines which API endpoint path will be used to fetch the resources.

For detailed information about resources, API response structures, and available resource types, see the 2dehands API documentation.

Once the selected endpoint template has been configured, click the Test button to the right of the endpoint selection menu to retrieve a sample of the data that will be fetched. Sample data will be displayed in the Endpoint Test Result panel on the right, allowing you to verify that the source is configured correctly before saving.

Manual configuration

2dehands data sources can also be manually configured to ingest data from any valid 2dehands API endpoint, including endpoints not covered by the pre-built templates, chained API calls, or custom request parameters. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, endpoint URL, date/time and lookup macros, path to data, metadata, and request headers.

Once all of the relevant settings have been configured, click the Create button in the upper right corner of the screen to save and create the new 2dehands data source. Nexla will now begin ingesting data from the configured endpoint and will organize any data that it finds into one or more Nexsets.

Use as a destination

Click the + icon on the Nexset that will be sent to the 2dehands destination, and select the Send to Destination option from the menu. 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.

Endpoint templates

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common 2dehands endpoints. 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.

Manual configuration

2dehands destinations can also be manually configured to send data to any valid 2dehands API endpoint. Select the Advanced tab at the top of the configuration screen, and follow the instructions in Connect to Any API to configure the API method, data format, endpoint URL, request headers, attribute exclusions, record batching, and response webhooks. Manual configuration also allows Nexla to automatically send the response received from the 2dehands API after each call to a new Nexla webhook data source.

The 2dehands APIs typically expect JSON format for most operations. For update/upsert operations, include the ID of the object to be updated at the end of the URL.

Save & activate

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.