Confirming Correct API Endpoints for GetTGP to Prevent XML Errors

Introduction

This article explains how to confirm GetTGP API endpoints and relation values so XML payloads are accepted consistently. It is intended for Reindeer users and integration teams troubleshooting GetTGP calls in automated workflows.

Correct API Endpoints for GetTGP

Use the GetTGP endpoint and API version configured for your Reindeer integration environment. Check the API documentation or implementation notes for the exact URL, version, authentication method, and required request format.

Relation Values for Groupage Scenarios

When submitting relational data in GetTGP calls, use the expected relation codes for the shipment scenario.

• For Groupage National, use XXZ when the Consignee Zip Code is the same as the Customer Zip Code.
• For Groupage National, use XXX when the Consignee Zip Code is different from the Customer Zip Code.
• For Groupage International imports into Germany, follow the relations documentation provided for that workflow and lane.

Verifying Your Implementation

If XML errors persist after applying the correct API endpoints and relations:

• Double-check endpoint URLs, API version, authentication, and payload formatting in your integration layer.
• Confirm relation codes such as XXZ and XXX match the shipment scenario.
• Validate the XML structure against the schema definitions provided in your API documentation.
• Confirm that relevant connector, runtime, or integration updates have been applied in your environment.

Support

For issues with GetTGP endpoint behavior or XML parsing, contact support@reindeer.ai.