Skip to main content

PrestaShop

PrestaShop is an open-source e-commerce platform for building and managing online stores. Its webservice API exposes store resources—orders, customers, addresses, pricing, and more—over REST, letting you extract catalog and transactional data for analytics, reporting, or synchronization with downstream systems.

PrestaShop icon

Power end-to-end data operations for your PrestaShop API with Nexla. Our bi-directional PrestaShop connector is purpose-built for PrestaShop, 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 PrestaShop or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your PrestaShop 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 PrestaShop credential, you need to enable the webservice on your store and generate a webservice authentication key. PrestaShop authenticates API requests using HTTP Basic authentication, where the webservice key is supplied as the username and the password is left empty.

To obtain your PrestaShop credentials, follow these steps:

  1. Sign in to your PrestaShop back office with an account that has administrator permissions.

  2. Navigate to Advanced Parameters > Webservice.

  3. Set Enable PrestaShop's webservice to Yes, and save the setting to activate the API.

  4. Click Add new webservice key (or the + button), then click Generate! to create a 32-character authentication key. You may also enter your own 32-character key.

  5. Under Permissions, grant the key access to the resources you plan to ingest (for example, orders, customers, and addresses). Grant GET access for read-only ingestion, and save the key.

  6. Note your store's API base URL, which is your storefront domain followed by /api (for example, https://your-store.com/api).

  7. Store the webservice key securely. The key alone grants access to the resources you authorized, so treat it as sensitive information and disclose it only to trusted integrations.

For more detail on enabling the webservice and managing access keys, see the PrestaShop Webservice Documentation.

Authenticate

Credentials required

FieldRequiredSecretDescription
UsernameYesNoYour PrestaShop webservice authentication key, generated under Advanced Parameters > Webservice. PrestaShop uses this key as the HTTP Basic auth username.
PasswordYesYesThe HTTP Basic auth password. PrestaShop does not use a password with the webservice key, so this may be left empty.
Base URLYesNoYour store's webservice base URL, in the form https://your-store.com/api.

Create a credential in Nexla

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

  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 PrestaShop webservice key in the Username field. This is the authentication key you generated in Prerequisites.

  4. Leave the Password field empty unless your setup requires a password. PrestaShop authenticates using only the webservice key.

  5. Enter your store's webservice base URL in the Base URL field, in the form https://your-store.com/api.

    Your webservice key grants access to every resource you authorized for it. If the key is compromised, disable it or generate a new one in your PrestaShop back office under Advanced Parameters > Webservice.

    For details on webservice access, permissions, and available resources, see the PrestaShop Webservice Documentation.

  6. 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 creation.

Use as a data source

To create a new data flow, navigate to the Integrate section, and click the New Data Flow button. Select the PrestaShop connector tile, then select the credential that will be used to connect to your PrestaShop store, and click Next; or, create a new PrestaShop 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 PrestaShop webservice resources. Select the endpoint from which this source will fetch data from the Endpoint pulldown menu. Available endpoint templates are listed in the expandable boxes below.

[Rest API] List Order Carriers

This endpoint template ingests records from the PrestaShop order_carriers resource. Retrieve order_carriers. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Order Details

This endpoint template ingests records from the PrestaShop order_details resource. Retrieve order_details. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Order Histories

This endpoint template ingests records from the PrestaShop order_histories resource. Retrieve order_histories. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Order Invoices

This endpoint template ingests records from the PrestaShop order_invoices resource. Retrieve order_invoices. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Order Payments

This endpoint template ingests records from the PrestaShop order_payments resource. Retrieve order_payments. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Orders

This endpoint template ingests records from the PrestaShop orders resource. Retrieve orders. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Order Slip

This endpoint template ingests records from the PrestaShop order_slip resource. Retrieve order_slip. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Order States

This endpoint template ingests records from the PrestaShop order_states resource. Retrieve order_states. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Price Ranges

This endpoint template ingests records from the PrestaShop price_ranges resource. Retrieve price_ranges. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Specific Price Rules

This endpoint template ingests records from the PrestaShop specific_price_rules resource. Retrieve specific_price_rules. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Specific Prices

This endpoint template ingests records from the PrestaShop specific_prices resource. Retrieve specific_prices. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Contacts

This endpoint template ingests records from the PrestaShop contacts resource. Retrieve contacts. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Customer Messages

This endpoint template ingests records from the PrestaShop customer_messages resource. Retrieve customer_messages. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Customers

This endpoint template ingests records from the PrestaShop customers resource. Retrieve customers. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Customer Threads

This endpoint template ingests records from the PrestaShop customer_threads resource. Retrieve customer_threads. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Employees

This endpoint template ingests records from the PrestaShop employees resource. Retrieve employees. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Groups

This endpoint template ingests records from the PrestaShop groups resource. Retrieve groups. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Shop Groups

This endpoint template ingests records from the PrestaShop shop_groups resource. Retrieve shop_groups. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Tax Rule Groups

This endpoint template ingests records from the PrestaShop tax_rule_groups resource. Retrieve tax_rule_groups. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice Documentation.

[Rest API] List Addresses

This endpoint template ingests records from the PrestaShop addresses resource. Retrieve addresses. Use this template when you need this data for analysis, reporting, or synchronization with other systems.

  • Nexla issues a paginated GET request to this resource and automatically iterates through all available pages, stopping when no further records are returned.

The PrestaShop webservice returns resource data in JSON when the Output-Format is set to JSON. For details on this resource, its fields, and available filters, see the PrestaShop Webservice 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

PrestaShop data sources can also be manually configured to ingest data from any valid PrestaShop webservice resource, including resources 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 PrestaShop 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.