Skip to main content

Beslist.nl Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a sync or streaming data flow that sends data to a Beslist.nl location.
beslist_nl.png

Beslist.nl

Create a Beslist.nl Destination​

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

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

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

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

    Update single product

    This endpoint updates a single product offer in your Beslist.nl shop by its external identifier. Use this endpoint when you need to update product information, pricing, availability, or other product details for individual products.

    • Enter the shop ID in the Shop id field. This is the identifier of the shop for which you want to update the product. You can retrieve your shop ID by accessing the /auth/v3/shops endpoint using a data source endpoint.

    • Enter the unique identifier of the product in the Identifier of the product field. This is the external ID that uniquely identifies the product you want to update. The external ID should match the identifier you use when creating or managing products in your system.

    • The endpoint uses POST requests to https://shopitem.api.beslist.nl/v3/offer/shops/{shopId}/offers/{externalId}. The endpoint URL is automatically constructed based on the shop ID and product identifier you provide.
    • The endpoint sends data from your Nexset as the request body in JSON format. Each record in your Nexset will be sent as a JSON object containing the product data to update. The request body should follow the Beslist.nl ShopItem API v3 specification for product updates, including required fields and field names.
    • Batch mode is disabled by default for this endpoint. Each record in your Nexset will be sent as a separate API request to update a product. If you need to update multiple products, you can send multiple records, but each will be processed as a separate request.

    Shop IDs can be obtained using the "Lists the shops" data source endpoint, which returns all shops linked with your API key. The product identifier (external ID) should match the identifier you use when creating products. The request body must be properly formatted JSON that matches the Beslist.nl ShopItem API v3 specification for product updates. 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. Batch mode is disabled by default (batch.mode: false), so each record will be sent as a separate request. For detailed information about updating products, including required fields, field names, and request formats, see the Beslist.nl ShopItem API V3 documentation.

    Update multiple products

    This endpoint updates multiple product offers in your Beslist.nl shop using batch processing. Use this endpoint when you need to update multiple products efficiently in a single batch operation.

    • Enter the shop ID in the Shop id field. This is the identifier of the shop for which you want to update products. You can retrieve your shop ID by accessing the /auth/v3/shops endpoint using a data source endpoint.

    • Enter the unique identifier of the batch in the Batch id field. This is the identifier that uniquely identifies the batch operation. The batch ID is used to track and manage the batch update process for multiple products.

    • The endpoint uses POST requests to https://shopitem.api.beslist.nl/v3/offer/shops/{shopId}/batch/{batchId}. The endpoint URL is automatically constructed based on the shop ID and batch identifier you provide.
    • The endpoint sends data from your Nexset as the request body in JSON format. The request body should contain the product data for all products to be updated in the batch. The request body should follow the Beslist.nl ShopItem API v3 specification for batch product updates, including required fields and field names.
    • Batch mode is disabled by default for this endpoint. The batch operation allows you to update multiple products in a single API request, which is more efficient than updating products individually.

    Shop IDs can be obtained using the "Lists the shops" data source endpoint, which returns all shops linked with your API key. The batch ID should be a unique identifier for the batch operation. The request body must be properly formatted JSON that matches the Beslist.nl ShopItem API v3 specification for batch product updates. 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. Batch mode is disabled by default (batch.mode: false), but the endpoint supports batch operations for updating multiple products efficiently. For detailed information about batch product updates, including required fields, field names, and request formats, see the Beslist.nl ShopItem API V3 documentation.

Configure Manually​

Beslist.nl destinations can be manually configured to send data to any valid Beslist.nl ShopItem API v3 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 Beslist.nl 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 Beslist.nl API from the Method pulldown menu. The Beslist.nl ShopItem API v3 primarily uses POST requests for data writing operations. The most common methods are:

    • POST: For creating or updating resources (e.g., updating products)
    • PUT: For updating existing data
    • PATCH: For partial updates to existing data
    • DELETE: For removing data

Data Format​

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

API Endpoint URL​

  1. Enter the URL of the Beslist.nl 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. For update operations, include the shop ID and product identifier or batch ID at the appropriate positions in the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. Beslist.nl ShopItem API v3 endpoints typically follow the pattern https://shopitem.api.beslist.nl/v3/offer/shops/{shopId}/offers/{externalId} for single product updates or https://shopitem.api.beslist.nl/v3/offer/shops/{shopId}/batch/{batchId} for batch operations. 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. For detailed information about Beslist.nl API endpoints and available APIs, see the Beslist.nl ShopItem API V3 documentation.

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). Additional headers are often required for API versioning, content type specifications, or custom authentication requirements.

    You do not need to include any headers already present in the credentials. Common headers like Authorization (API key), Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration. The Beslist.nl ShopItem API v3 requires API key authentication in the apiKey header, which is handled automatically by your credential configuration. The Content-Type: application/json header is typically set automatically for JSON request bodies.

Request Body​

Optional

  • If the API endpoint requires a specific request body format, configure how Nexla should format the request body from your Nexset data. The request body can be sent as JSON, XML, or form data, depending on the API endpoint requirements.

    • For JSON format, select JSON from the Request Body Format dropdown, and the Nexset data will be sent as a JSON object in the request body. Beslist.nl ShopItem API v3 endpoints typically use JSON format for request bodies.

    • For XML format, select XML from the Request Body Format dropdown, and the Nexset data will be converted to XML format in the request body.

    • For Form data format, select Form Data from the Request Body Format dropdown, and the Nexset data will be sent as form-encoded data in the request body.

Save the Destination​

  1. Once all configuration steps have been completed, click the Save button to save your destination configuration.

  2. The destination will now be available in your data flow and will begin sending data to the Beslist.nl endpoint according to the configured settings.