Plytix

Plytix is a Product Information Management (PIM) platform that helps businesses centralize, manage, and distribute product data across multiple channels, enabling teams to create consistent and compelling product experiences.

Power end-to-end data operations for your Plytix API with Nexla. Our bi-directional Plytix connector is purpose-built for Plytix, 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 Plytix or any other destination. With comprehensive monitoring, lineage tracking, and access controls, Nexla keeps your Plytix 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 Plytix credential, you need to obtain your API key and API password from your Plytix account. Plytix uses token-based authentication, where your API key and API password are used to obtain an access token that is then used for all subsequent API requests.

To obtain your Plytix API credentials, follow these steps:

1. Sign in to your Plytix account using your administrator credentials.

2. Navigate to your account settings or API management section in the Plytix interface.

3. Look for the API or API Credentials section in your account settings, or navigate to Settings > API or Integrations > API.

4. If you don't have API credentials yet, look for the option to create or view your API Key and API Password.

5. Click Create API Credentials or Generate API Key to create new API credentials.

6. Configure your API credentials:

   • Enter a name for the API credentials (e.g., "Nexla Integration")
   • Review and select the permissions or scopes for the credentials (if applicable)

7. Click Create or Generate to create the API credentials.

8. Your API Key will be displayed immediately after creation. Copy the API key.

9. Your API Password will be displayed immediately after creation. Copy the API password immediately, as it may not be accessible again after you navigate away from the page.

10. Store both credentials securely, as you will need them to configure your Nexla credential. The API key and API password are sensitive information and should be kept confidential.

The API key and API password are used to authenticate with the Plytix API authentication endpoint (/auth/api/get-token) to obtain an access token. The access token is then sent in the Authorization header with the Bearer prefix for all subsequent API requests to the Plytix API. The access token is automatically obtained and refreshed by Nexla as needed. If your credentials are compromised, you should immediately revoke them in your Plytix account settings and generate new ones. For detailed information about Plytix authentication, API access, and available endpoints, refer to the Plytix API documentation.

Authenticate

Credentials required

Field	Required	Secret	Description
Access Token	Yes	Yes	Access Token
API Password	Yes	Yes	API Password

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.

New Credential Overlay – Plytix

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 Plytix API key in the Access Token field. This is the API key you obtained from your Plytix account settings (Settings > API or API Credentials section). The API key is used along with the API password to authenticate with the Plytix API authentication endpoint and obtain an access token.

4. Enter your Plytix API password in the API Password field. This is the API password you obtained from your Plytix account settings. The API password is used along with the API key to authenticate with the Plytix API authentication endpoint and obtain an access token. The API password is sensitive information and must be kept confidential.

   Your Plytix API credentials can be found in your Plytix account settings under Settings > API or API Credentials section. The API key and API password are used to authenticate with the Plytix API authentication endpoint (/auth/api/get-token) to obtain an access token. The access token is then automatically sent in the Authorization: Bearer {token} header for all subsequent API requests to the Plytix API.

   The access token is automatically obtained and refreshed by Nexla as needed. If your credentials are compromised, you should immediately revoke them in your Plytix account settings and generate new ones. The API key and API password provide access to your Plytix account data and should be treated as sensitive information. Keep your credentials secure and do not share them publicly.

   For detailed information about Plytix authentication, API access, and available endpoints, see the Plytix API documentation.

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

Get available asset filters

This endpoint template retrieves available asset filters from your Plytix account. Use this template when you need to retrieve information about available filters for assets, including filter names, types, and other filter metadata.

• This endpoint automatically retrieves all available asset filters from your Plytix account. No additional configuration is required beyond selecting this endpoint template.

This endpoint returns a list of available asset filters from your Plytix account, including filter names, types, and other filter metadata. Use this endpoint to discover which filters are available in your Plytix account before using them with other Plytix endpoints.

For detailed information about asset filters, API response structures, and available filter data, see the Plytix 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

Plytix data sources can also be manually configured to ingest data from any valid Plytix 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.

Plytix API typically uses the GET method for retrieving data. Endpoint URLs follow the pattern https://pim.plytix.com/api/v1/{resource_path} (e.g., https://pim.plytix.com/api/v1/filters/asset). For the Response Data Path, use $.data[*] to extract all items from the data array, or $ to extract the entire response for single-record endpoints, depending on your endpoint.

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 Plytix 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 Plytix destination, and select the Send to Destination option from the menu. Select the Plytix connector from the list of available destination connectors, then select the credential that will be used to connect to the Plytix organization, and click Next; or, create a new Plytix 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 Plytix 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.

Add Records of ObjectType

This endpoint template adds records of a specific ObjectType to your Plytix account using records from a Nexset. Use this template when you need to create new products, relationships, or other object types in your Plytix account. Check out the documentation URL for more details on object schema.

• Select the object type from the Object Type pulldown menu. Available options include Products (products) and Relationships (relationships). The object type determines which Plytix resource will be created. Select the object type that matches the data you want to create.

This endpoint sends data as JSON in the request body to add records of a specific ObjectType in your Plytix account. Each record from your Nexset will be sent as a separate API request to create a new record in Plytix. The request body should contain the record data in the format required by the Plytix API.

The record structure must match the Plytix API's expected format for the selected object type. Check out the documentation URL for more details on object schema. For detailed information about record creation, request body formats, available object types, and resource management, see the Plytix API documentation.

Manual configuration

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

Plytix API typically uses the POST method and expects JSON format for request bodies. Endpoint URLs follow the pattern https://pim.plytix.com/api/v1/{object_type} (e.g., https://pim.plytix.com/api/v1/products, https://pim.plytix.com/api/v1/relationships). The request body is typically {message.json} to send the entire Nexset data as JSON, or a custom JSON structure with specific field mappings matching the expected schema for the selected object type.

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

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