Picqer

Picqer is a warehouse and order-fulfillment management platform for e-commerce, handling picking, packing, inventory, and shipment operations. Its REST API exposes orders, products, stock, purchase orders, returns, and warehouse data, letting you sync fulfillment information with the rest of your data stack and push new orders and products back into Picqer.

Power end-to-end data operations for your Picqer API with Nexla. Our bi-directional Picqer connector is purpose-built for Picqer, 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 Picqer or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Picqer 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 Picqer credential, you need an API key from your Picqer account and your Picqer API base URL. Picqer authenticates API requests using HTTP Basic authentication, where the API key is supplied as the username and the password field is ignored.

To obtain your Picqer API credentials, follow these steps:

1. Sign in to your Picqer account at your organization's subdomain (e.g., https://example.picqer.com).

2. Navigate to Settings > API Keys in the Picqer web application.

3. Create a new API key, or copy an existing one. API keys can be revoked at any time from this screen and cannot be used to sign in to the Picqer web app, so they are safe to use for integrations.

4. Determine your API base URL. Each Picqer client has its own subdomain, and the API base URL follows the pattern https://{subdomain}.picqer.com/api/v1. For example, if you access Picqer at https://example.picqer.com, your base URL is https://example.picqer.com/api/v1.

5. Store the API key securely, as you will use it when configuring your Nexla credential.

Picqer requires all API requests to include a User-Agent header that identifies your application. For detailed information about authentication and available endpoints, refer to the Picqer API Documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Username	Yes	No	Username used to authenticate requests to the Picqer API.
Password	Yes	Yes	Password used to authenticate requests to the Picqer API.
Base URL	Yes	No	API base URL.

Picqer uses your API key as the username for HTTP Basic authentication. Enter the API key in the Username field; the password field is not used by Picqer, so any placeholder value can be entered in the Password field.

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.

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 Picqer API key in the Username field.

4. Enter a value in the Password field. Picqer ignores the password when the API key is supplied as the username, so any placeholder value can be used here.

5. Enter your Picqer API base URL in the Base URL field (e.g., https://example.picqer.com/api/v1).

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/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. Select the Picqer connector tile, then select the credential that will be used to connect to Picqer, and click Next; or, create a new Picqer 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 Picqer endpoints. 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 Users

This endpoint template retrieves users from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Orders

This endpoint template retrieves orders from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Backorders

This endpoint template retrieves backorders from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Purchase Orders

This endpoint template retrieves purchase orders from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Customers

This endpoint template retrieves customers from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List VAT Groups

This endpoint template retrieves VAT groups from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Products

This endpoint template retrieves products from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Products Stock

This endpoint template retrieves the stock records for a specific Picqer product.

• Product ID (required) — ID of the Picqer product whose stock to retrieve.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Returns

This endpoint template retrieves returns from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Locations

This endpoint template retrieves locations from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Warehouses

This endpoint template retrieves warehouses from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Suppliers

This endpoint template retrieves suppliers from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Tags

This endpoint template retrieves tags from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Templates

This endpoint template retrieves templates from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer API Documentation.

[Rest API] List Stats

This endpoint template retrieves account statistics from your Picqer account.

For detailed information about this endpoint and its response fields, see the Picqer 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

Picqer data sources can also be manually configured to ingest data from any valid Picqer 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 Picqer 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 Picqer destination, and select the Send to Destination option from the menu. Select the Picqer connector from the list of available destination connectors, then select the credential that will be used to connect to Picqer, and click Next; or, create a new Picqer 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 Picqer 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.

[Rest API] Create Order

This endpoint template creates a new order in Picqer with status 'concept', using records from a Nexset.

Each record from your Nexset is sent as a JSON request body to create a new order. The record structure must match the format expected by the Picqer API. For detailed information about order creation and required fields, see the Picqer API Documentation.

[Rest API] Update Order

This endpoint template updates the delivery/invoice address and other select fields of an existing Picqer order.

• Order ID (required) — ID of the Picqer order to update.

Each record from your Nexset is sent as a JSON request body to update the specified order. The record structure must match the format expected by the Picqer API. For detailed information about updating orders, see the Picqer API Documentation.

[Rest API] Create Product

This endpoint template creates a new product in Picqer with the required fields idvatgroup, productcode, name, and price, using records from a Nexset.

Each record from your Nexset is sent as a JSON request body to create a new product. The record structure must match the format expected by the Picqer API. For detailed information about product creation and required fields, see the Picqer API Documentation.

[Rest API] Update Product

This endpoint template modifies an existing Picqer product's details, including name, price, and productfields.

• Product ID (required) — ID of the Picqer product to update.

Each record from your Nexset is sent as a JSON request body to update the specified product. The record structure must match the format expected by the Picqer API. For detailed information about updating products, see the Picqer API Documentation.

Manual configuration

Picqer destinations can also be manually configured to send data to any valid Picqer 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.

Picqer APIs expect JSON format for order and product operations. For update 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 Picqer endpoint, open the destination resource menu, and select Activate.

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