Pipe17

Pipe17 is a multi-channel e-commerce operations platform that orchestrates orders, inventory, products, and fulfillment across storefronts, marketplaces, 3PLs, and ERPs. Its REST API exposes these operational objects for read and write access, letting Nexla sync order, inventory, shipment, and financial data between Pipe17 and the rest of your data stack.

Power end-to-end data operations for your Pipe17 API with Nexla. Our bi-directional Pipe17 connector is purpose-built for Pipe17, 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 Pipe17 or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Pipe17 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 Pipe17 credential, you need an API key for your Pipe17 organization. Pipe17 authenticates every API request with an organization API key sent in the X-Pipe17-Key request header.

To obtain your Pipe17 API key, follow these steps:

1. Sign in to the Pipe17 console with an account that has administrator access to your organization.

2. Navigate to Settings > API Key.

3. Create a new API key. The key is owned by and associated with the user who creates it, so use an account that will remain active.

4. Set the resource-type grants for the key so that it has access to the objects you plan to read or write through Nexla (for example, orders, inventory, fulfillments). Administrators can adjust these grants or terminate the key at any time.

5. Copy the generated API key and store it securely — you will provide it when creating your Nexla credential.

For security, Pipe17 recommends creating separate keys for separate purposes rather than reusing a single broad key. For complete details on authentication and available objects, see the Pipe17 API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
API Key	Yes	Yes	Pipe17 organization API key (X-Pipe17-Key header value).

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 Pipe17 API key in the API Key field. This value is sent in the X-Pipe17-Key header on every request to the Pipe17 API and must be kept confidential.

   If your API key is compromised, terminate it in the Pipe17 console under Settings > API Key and generate a new one. API keys grant access to your Pipe17 organization data based on the resource-type grants assigned to the key.

   For detailed information about authentication and available objects, see the Pipe17 API documentation.

4. 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 Pipe17 connector tile, then select the credential that will be used to connect to Pipe17, and click Next; or, create a new Pipe17 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 Pipe17 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 Orders

List orders across all connected sales channels.

[Rest API] List Products

List products in the product catalog.

[Rest API] List Inventory

List inventory ledger items (on-hand/available quantities by SKU and location).

[Rest API] List Fulfillments

List order fulfillments (packed/shipped line items).

[Rest API] List Shipping Requests

List warehouse shipment/pick requests generated from orders.

[Rest API] List Trackings

List shipment tracking records and carrier status updates.

[Rest API] List Stores

List connected sales channels / storefronts (Shopify, Amazon, etc.).

[Rest API] List Integrations

List configured channel/marketplace/3PL integrations.

[Rest API] List Locations

List warehouse and fulfillment locations.

[Rest API] List Customers

List customer records associated with orders.

[Rest API] List Purchase Orders

List supplier purchase orders.

[Rest API] List Returns

List customer returns (RMAs).

[Rest API] List Refunds

List order refunds.

[Rest API] List Inventory Transfers

List inter-location inventory transfers.

[Rest API] List Receipts

List inbound receiving records against purchase orders/transfers.

[Rest API] List Invoices

List order/channel invoices.

[Rest API] List Shipment Boxes

List packed shipment box/carton records.

[Rest API] List Shipping Methods

List configured shipping methods/carrier services.

[Rest API] List Catalogs

List product catalogs.

[Rest API] List Catalog Products

List products within catalogs (channel-specific listings).

[Rest API] List Suppliers

List vendor/supplier records used on purchase orders.

[Rest API] List Payments

List order payment transactions.

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

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

Create one or more orders (e.g. from an external channel).

[Rest API] Update Order

Update an existing order (status, line items, shipping info).

[Rest API] Create Inventory Log Items

Post inventory adjustments/log items to update stock levels.

[Rest API] Create Fulfillments

Create a fulfillment record for shipped order line items.

[Rest API] Create Shipping Requests

Create a warehouse shipment/pick request for an order.

[Rest API] Create Tracking

Attach a carrier tracking record to a shipment.

[Rest API] Create Purchase Orders

Create a supplier purchase order.

[Rest API] Create Return

Create a customer return (RMA).

Manual configuration

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

Pipe17 APIs expect JSON payloads. For update operations, include the ID of the object to be updated as required by the target endpoint.

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 Pipe17 endpoint, open the destination resource menu, and select Activate.

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