Application configuration is an integral activity prior to the process of integration. If your chosen application is
credentials need to be provided for validating the agent. Here you will find the detailed description on how to
configure the agents
for the application of Shipstation, Troubleshooting issues and the attributes and action.
Shipstation is a REST Application which supports both the BASIC authentication. The Adapter of the application Shipstation provides the leverage to communicate and adapt with the AEC Portal. This section provides you the detailed process of validating the credential of the application Shipstation.
Pre-requisites of Shipstation Configuration
- Valid APPSeCONNECT Portal credentials.
- Select the Application Shipstation in the APP section.
- Create connection for Shipstation.
- Publish Touchpoint, Update Adapters and Update Configuration in the agent.
Configure the Agent
To Know about Agent Configuration, Click here
Configuring the Shipstation Adapter
- In the App Configuration panel of the agent, click on the + button, beside the app Shipstation.
- On clicking the + button, the credential panel opens for the application Shipstation.
- For generating the API Key and the API Secret,
navigate to Settings (the wrench icon) > Account > API Settings> Generate API Keysin the Shipstation Portal. The API settings window opens.
- Provide the generated credentials in the agent and then click on
Following this process, the Shipstation application can be configured in the agent.
ISSUE 1:Source Application Data Not Found
Source Application Data Not Found even if Data is present is the Source Application.
Some of the basic troubleshooting issue happens due to improper validations or even if it is accurately validated, and if touchpoints do not sync,
this basic issue resolves after removing the
Temp and Cache files from the
portal and from your
system. Therefore, after clearing all this publish the
touchpoints again along with Update Configuration on the agent.
For E.g. If the
Source Application Not Found in the log file appears, the probable cause is due to the presence of the Temp and Cache Files.
ISSUE 2:Syncing Issues
While working with SAP B1 Integrations, SAP Business One DI Server ON/OFF is needed to be done for proper syncing else data will not sync to SAP Business One
ProTip: For the integration between Shipstation and SAP Business One, no Addons needed to be installed in SAP.
However, for the integration between these application, UDFs needed to be created for the touchpoint
Business Partner Download
as per the business requirements.
Attributes and Actions
While defining a connect to a particular API endpoint in Shipstation, you require clear understanding about the data requirements and endpoint configurations. You can refer to this document to find all the endpoint details of your shipstation installation. To define the endpoint in APPSeCONNECT, you need Actions and Entities. Actions are specifically targetted for a particular endpoint while schema is the data needed to execute the API. Here are the list of some of the prepackaged API actions defined for you which you can easily plug and play while doing your integrations.
|Endpoint||Action||Action Type||Schema||UI Help||API Help|
|customers||customers||Get||Customers||Create customer for Shipstation and POST it to the destination application||API for fetching Customers|
|orders||orders||GET||order||Creating Orders in Shipstation||API Path for fetching Orders from Shipstation|
|orders/createorder||orders/createorder||POST||order||Posting orders from Source Application to Shipstation||API for Posting Orders to Shipstation|