Skip to main content

Authorization

Follow this guide to create a new 2dehands credential that will allow Nexla to authenticate to and exchange data with your 2dehands account.
two_2dehands_api_auth.png

2dehands

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.

Create a 2dehands Credential​

  • To create a new 2dehands credential, after selecting the data source/destination type, click the Add Credential tile to open the Add New Credential overlay.

New Credential Overlay – 2dehands

2dehandsCred.png

Credential Name & Description​

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

    Resource descriptions are recommended but are not required. They should be used provide information about the resource purpose, data freshness, etc. that can help the owner and other users efficiently understand and utilize the resource.

OAuth2 Client Credentials Authentication​

2dehands uses OAuth2 client credentials (2-legged) authentication for all API requests. This method uses your Client ID and Client Secret to obtain access tokens automatically.

  1. 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.

  2. 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.

Save the Credential​

  1. Once all of the relevant steps in the above sections have been completed, click the Save button at the bottom of the overlay to save the configured credential.

  2. The newly added credential will now appear in a tile on the Authenticate screen during data source/destination creation and can be selected for use with a new data source or destination.