When interacting with techTRACK via REST Application Programming Interface (API) there are tools, documentation and good practices that will help you do it in the easiest way possible.
These are the sections detailed in this article:
- How to get the required API credentials to be able to use the API.
- How to use Swagger documentation to learn and test the available API methods.
- How to use Postman for testing the API calls
HOW TO GET THE REQUIRED API CREDENTIALS
To use the API, you need two API keys: one for the user and one for the organization.
For detailed instructions on obtaining the necessary API keys, refer to the following articles:
- How to Get an API Key for Your Organization [Step-by-Step Guide]
- How to Get Your User API Key [Step-by-Step Guide]
WARNING: API credentials are sensitive and should be handled securely. Avoid sharing or exposing them. All API requests must be authenticated; unauthenticated requests will not be processed. While you might have the option to copy an account API key, using it instead of the organization's API key is strongly discouraged.
HOW TO USE SWAGGER DOCUMENTATION
You can review the Swagger documentation at https://v2.techtrack.cloud/swagger.

techTRACK's API methods are categorized in Swagger as follows:
Event: Details how to create and get events.
List: Details how to get list data that can be used in another categories.
- Pod: Details how to get Proof of Delivery (PoD) data.
- Tracking: Details how to create, get and update tracking numbers.
- TrackingIntegration: Details how to create an event in Intelcom format.
You can refer to How to Use Swagger Documentation [Information] to learn more about using Swagger for reference and testing Techdinamics' APIs.
HOW TO USE POSTMAN FOR TESTING
Once you have familiarized yourself with the API, the next step is to test it.
You can refer to How to Use Postman to Test API Calls [Step-by-Step guide] to learn more about using Postman for testing Techdinamics' APIs.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article