Myparcelasia icon

Myparcelasia

Custom operations

Actions6

Overview

This node integrates with the Myparcelasia API to perform various shipping-related actions. Specifically, the Checkout Order operation finalizes the checkout process for shipments by sending shipment keys along with authentication tokens to the API endpoint. This operation is useful in scenarios where you have created shipments and need to confirm or finalize their checkout status programmatically.

Practical examples include:

  • Automating the shipment checkout process after creating multiple shipments.
  • Integrating with e-commerce platforms to automatically confirm orders for shipping.
  • Batch processing shipment checkouts using stored shipment keys.

Properties

Name Meaning
CJ Token A secret token used to authenticate requests to the Myparcelasia API for checkout order.
API Key An API key credential required to authorize the checkout order request.
Shipment Keys The shipment keys identifying which shipments to checkout; typically a string of keys.

Output

The output JSON contains the response from the Myparcelasia API after attempting to checkout the specified shipments. It generally includes confirmation details such as success status, any errors, and possibly updated shipment information.

No binary data is output by this operation.

Example output structure (simplified):

{
  "success": true,
  "message": "Checkout completed",
  "data": {
    "checkedOutShipments": [
      {
        "shipmentKey": "abc123",
        "status": "checked_out"
      }
    ]
  }
}

Dependencies

  • Requires access to the Myparcelasia API endpoints.
  • Needs valid CJ Token and API Key credentials configured securely in n8n.
  • Network connectivity to https://api.customje.com/mpa-checkout.php must be available.

Troubleshooting

  • Common issues:

    • Invalid or expired CJ Token/API Key will cause authentication failures.
    • Incorrect or malformed shipment keys may result in errors or no shipments being checked out.
    • Network issues or API downtime can cause request failures.

  • Error messages:

    • "The operation is not implemented yet!" — indicates an unsupported operation was selected.
    • "The resource \"actions\" is not known!" — indicates an invalid resource parameter.
    • API error responses will be passed through; check the message field for details.

  • Resolutions:

    • Verify that CJ Token and API Key are correct and active.
    • Ensure shipment keys are correctly formatted and correspond to existing shipments.
    • Check network connectivity and API service status.
    • Use the node's "Continue On Fail" option to handle errors gracefully during batch processing.

Links and References

Discussion