Before You Begin
Before you begin installing the Jasper PIM subscription, you need to obtain an API key from Jasper PIM.
Log in to your Jasper PIM account.
On the side menu, select Settings > API Key.
Click Create Token.
Jasper PIM displays the My API Key dialog box.Copy the token and store it in a safe place. If you lose it, you must recreate a new token.
With the API token saved, you can begin installing the integration.
Installation Instructions for Integration Setup
Go to Subscriptions Management > Subscriptions and click Search Certified Integration Marketplace and Subscribe.
Click the Jasper PIM Integration title.
On the Subscription Detail page, click the Subscribe button.
Enter the Name of the subscription and select a Version. It can be set to any relevant and unique subscription name within the company where this subscription is created.
Format: [Product Name] - [Environment/Purpose]
Example: Jasper PIM– Release
Select Create Default Mappings (recommended).
If you don’t want to create default mappings and want to create all mappings from scratch by yourself, then uncheck this box.
Provide the API URL endpoint for your Jasper PIM instance. Your Jasper PIM API URL can be found in the Jasper dashboard URL prefix. For example, take the prefix from the dashboard URL
https://cabot39nda.oci-1.jasperpim.com/dashboardand add/api/v1to generate the API URL needed for the Jasper integration for iPaaS results inhttps://cabot39nda.oci-1.jasperpim.com/api/v1Environment URLs
Test/Sandbox:
https://cabot39nda.oci-1.jasperpim.com/api/v1Production: N/A
Enter the API Key you generated in Jasper PIM.
Enter the API Throttle Limit. This setting prevents any single integration or user from overwhelming the system with too many requests. It protects system performance by controlling the number of API requests that can run simultaneously, ensuring fair usage.
Recommended Values
Initial Setup: 5
Ongoing Operations: 500
High Volume: 500
Enter the API Throttle Seconds. This defines the time window during which the API Throttle Limit is measured. If an integration makes too many requests within this time window, additional requests are rejected until the window resets.
Default Value: 60 seconds
Range: 60 seconds
Enter the number of Concurrent Connections. This specifies the maximum number of simultaneous API connections that (Undefined variable: Integrations.placeholder) can process for a user or integration. If this limit is exceeded, new requests are queued or rejected until a currently active connection finishes.
Default Value: 2
Set Value to 10.
Range: 10
Enter the number of Concurrent Batch Executions. This specifies the maximum number of simultaneous batch executions that can process for an integration at one time. . If this limit is exceeded, new requests are queued or rejected until a currently active connection finishes.
Default Value: 10
Set Value to 10.
Range: 10
Click Apply to save the settings.
Common Issues and Solutions
Insufficient Permissions
Issue: Users cannot access products, attributes, or catalogs.er lacks required roles.
Solution: Verify the user has the correct role assignment (e.g., Administrator, Catalog Manager, Product Editor) in the Jasper Admin Console.
Unsupported Environment
Issue: Jasper integration fails with certain platforms or middleware.
Solution: Confirm that the target system is officially supported (e.g., Shopify, Magento, BigCommerce, Dynamics 365, custom API integrations). Ensure all API endpoints are enabled in Jasper.
Missing License
Issue: Users cannot log in or see restricted modules.
Solution: Assign an available Jasper PIM license to the user or purchase additional licenses through your Jasper account manager.
Installation or Setup Errors
Issue: Errors occur when installing or configuring Jasper connectors or APIs.
Solution:
Retry setup in a supported browser (Chrome, Edge).
Clear the cache and restart.
If it is still failing, check Jasper logs and re-attempt configuration.
Data Conflicts
Issue: Duplicate SKUs, overlapping attribute codes, or mismatched product schemas cause sync failures.
Solution: Clean data before import. Use Jasper’s data validation tools to enforce SKU uniqueness and schema compliance.
Storage and Performance Limits
Issue: Product or media uploads fail, or the system slows down. Product schemas cause sync failures.
Solution:
Archive unused catalogs, products, or media.
Request additional storage or performance scaling from Jasper Support.
Sync or API Failures
Issue: Data doesn’t flow between Jasper and integrated platforms.
Solution:
Re-check API credentials and access tokens.
Confirm the external system allows Jasper API calls.
Re-authenticate integrations from the Admin Console.
Regional Restrictions
Issue: Certain Jasper features or connectors are not available in your region.
Solution: Confirm with Jasper Sales which data centers and regions are supported for your subscription.
Product/Option Import Issue
Issue: Options or attributes fail to import into Jasper.
Solution:
Ensure attribute sets and option sets exist before import.
Map external attributes to Jasper Option IDs during setup.
Missing Dependencies
Issue: Some modules (e.g., Pricing, Multi-language, Media) don’t function correctly.
Solution: Verify that all required Jasper modules are installed and licensed in your environment.
Post-Installation Verification
After completing the installation, perform these tests to verify the installation.
Data Sync Test
Initiate a sample data pull. (To iPaaS.com)
Initiate a sample data push. (From iPaaS.com)
Functionality Test
Run an end-to-end business process.
Validate key features like field mappings, workflow triggers, and logging.
Review integration logs in iPaaS.com.
Support and Troubleshooting
Click the Help button on any iPaaS.com page to contact Support or to search our documentation.
Documentation: Search our documentation at the top of this article
Support Portal: Click the Help and Support button at the lower-right of this window.
Contact Information: Contact iPaaS.com.