Discussions

Hello team! I'm encountering an issue with the "Update a Shipment" PATCH request via the Easyship API. I'm receiving a 200 OK message for a request, however the output returned shows that the required property "description" has, in fact, not been updated. Could you please assist in explaining why this may have occurred? The API has all required access scopes for the request. <https://help.plyco.com.au/hubfs/easyship.png> Thanks

Hello, We're building integration for Easyship in our system, we process large amount of shipments every month more than 10 thousands, now we need Mock shipments data in our EasyShip account as we need to test our integration in large scale. Looking forward for solution from Easyship team

I am writing to seek assistance as I am currently trying to integrate your “Return Shipment“ API and am facing some issues. Please provide a valuable solution for that. Also, attach the screen shot. <https://prnt.sc/N8X4iQ7Pku_F>

I am writing to seek assistance as I am currently trying to integrate your “Return Shipment“ API and am facing some issues. Please provide a valuable solution for that. Also, attach the screen shot.

We are in the initial face of integration easyship api but before we get too far, we did not see any information regarding FedEX ETD and DHL PLT on your API documentation. We plan on creating and printing all of our labels from our web interface through easyship API calls, we were hoping to set the options to send ETD or PLT from our application, is that possible to do so with Easyship?

We got a message that UPS is changing their APIs model so I wanted to ask if you do all the integration or if we have to do anything? Here is part of the message: On June 5, 2023, UPS began the sunset process for access key authentication in favor of the more secure OAuth 2.0 model for all APIs. This change impacts all API integrations and requires updates to your existing application interface. If your integration is managed by a 3rd party, please contact the provider. The migration guide linked below can help answer questions about the transition from access keys to OAuth 2.0 OAuth Migration Guide How will this impact my API integration? • Beginning June 3, 2024, access keys will no longer be supported for authentication • API integration owners must obtain new API credentials from the UPS Developer Portal and update their application interface to use the OAuth 2.0 security model • Any legacy UPS API integrations using XML, SOAP, or legacy JSON payloads will also be required to convert to the RESTful APIs

When I integrate the api at checkout on a website build by myself, are there any front end components that are ready to use or is that something I must build myself?

Please activate methods for creating shipping orders for the API, api name ship247 1. Shipping scope 2. Single Adres validation scope 3. ve other scopes for create orders

Hello, I have the following detail "error": { "code": "invalid_content", "details": [ "Shipments not ready to be shipped: ESUS10138972" ], "message": "The request body content is not valid.", "request_id": "0a3640eb36c9993bdba7c41e8c813718", "type": "invalid_request_error"