Home / Product Line Carrier Connect API Our connect API landing page is below, here you can download the swagger, see example json requests and code examples. API documentation Once you are ready to get started please send an email over to servicedesk@3t-europe.com . We will send you back an API key that you can use for testing purposes. An API for Carriers to plug into Event This API allows carriers to pull data from Event, update Event with tracking, shipping labels and much more. Retrieve a route from Event In Event each of your routes will have a unique id number, this id can be found in connect. This unique identifier can be used to communicate with Event through our API and pull back route data for a specific route id. Example below. https://event3tdev.azure-api.net/carrierconnect/route/1e11Em49 This will return all the route detail for this route and all the detail for each of the stops on the route. Get all routes by collection date You can also pull all your routes for a given collection date. https://event3tdev.azure-api.net/carrierconnect/routes/2022-09-07 This will return a collection of routes, it will still included all the stop level detail. Get all customers you are connected to in Event If at any time you want to see all of the customers you are connected to in Event, you can call the operation below. https://event3tdev.azure-api.net/carrierconnect/accounts/ No parameter needs to be passed, we will identify who you are by the key you have passed in the request. Update routes and stops in Event The connect API also gives you the ability to send us information and update your routes/stops in Event. For example the below operation can be used to send us back shipping labels, documents and costs. https://event3tdev.azure-api.net/carrierconnect/stops/ Send us tracking updates You can send us back tracking information using the operation below, there is also the option to send us back GPS information so we can track the shipment on route. https://event3tdev.azure-api.net/carrierconnect/trackingevents/ Need us to push updates to you? If you need us to push information to you we have got you covered, using the operation below you can register a url for us to send webhook notifications to. https://event3tdev.azure-api.net/carrierconnect/trackingevents/ Currently, our recommended best practice for securing Webhooks involves using basic authentication and HTTPS on your endpoint. This will help prevent any altering of any information communicated to you by 3T, prevent any third parties from seeing your webhooks in transit, and will prevent any third parties from masquerading as 3T and sending fraudulent data. 3T performs certificate validation and requires any TLS-enabled (HTTPS) webhook recipients to have a certificate signed by a public trusted certification authority. We do not support sending webhooks to over SSLv2, SSLv3, or any connection using so-called export-grade ciphers. The example response shows the webhooks event you will receive to your endpoint once it is enabled.

3T is a leader in network solutions and logistics / transportation software, 3T's Event software redefines how you optimise the position of your business on a global scale in todays digital world. Event. Start building your next integration with Event Connect Register interest View documentation Technology that improves your business Our Event Connect API solutions are designed to be innovative and easy-to-use, allowing you to build new experiences with our TMS. Speed up your development with our specialised integrations: EVENT Order – order message solutions EVENT G0 – delivered receipt solutions View documentation Order Message solutions EVENT Order is our point-of-order integration pushing incoming orders directly into the planning and optimised plan information back Learn more Order Tracking solutions EVENT Go are a suite of API's that directly connect you to your logistics network through Event. It provides visibility, delivery and invoice detail so you can stay in control of keeping your customers happy. Learn more POD / Invoice solutions EVENT Go includes tracking, proof-of-delivery, additional cost requests and invoice detail from your chosen logistics providers Learn more

Home - Documentation - Delivery simulation (Event Go) Event Order API (POS) About our Partnership How does it work? Integration flow Additional information Delivery simulation The Delivery Simulation Endpoint facilitates external partners in emulating the complete delivery process for testing objectives. Engineered to replicate real-world delivery workflows, it initiates from assigning the delivery to a courier and advances through sequential stages until the delivery fulfillment. At each juncture, a webhook is activated, enabling external partners to validate the integration with their system. It's crucial to note that this endpoint is exclusively accessible within staging environments. Following the creation of an /estimate and /delivery, you gain access to utilize the generated requestId for accessing the simulate endpoint. This endpoint enables you to simulate the entire delivery process, providing a realistic emulation of the workflow from start to finish, thereby allowing comprehensive testing and validation of your integration This funtion is tbc Event Go Documention Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification next... Validation and certification

Top of Page Privacy Policy 'Header' Privacy Policy Title a b

Top of Page Privacy Policy 'Header' Title a b Privacy Policy

Top of Page Privacy Policy 'Header' Privacy Policy Title a b

Top of Page Requirements Direct-to-Print Labelling The no-hands, web based label solution for fully integrated customers... Are you looking to print parcel labels directly from packing the item? No manual searching or scanning for the HU in Event, just pack and print? The Direct-to-Print application uses the Label Station ID added to the Packing message to trigger the print of the label you have just packed. The application is a windows application It needs to be downloaded onto each Label Station PC Each PC must have a default printer setup Each Label Station must be given a unique name to differentiate it (Workstation01, Workstation02...) You will need to add this unique Label Station ID to the packing Order message you create On receipt of the packing Order message, Event will process the request automatically and output the correct label for exactly the packing Order sent. Expected performance is approx. 10 seconds per label* note : Direct-to-Print works only per packing Order message, it does not allow for consolidation as it creates per HU reference. Ready to activate? Make sure all the requirements have been met... Get Direct-to-Print Implementing Direct-to-Print How to start direct label printing This guide will step through getting started with hands free label generation What is Direct-to-Print? To find information for your users, you can search for it in 3t-event.com... 'How to' guide ...or access it from the activation page in Event itself. Save ...save the status. Direct-to-Print is now LIVE and ready to receive. What is Direct-to-Print? To find information for your users, you can search for it in 3t-event.com... 1/19 Now it's active, how do i use it? Once downloaded, the application will need to be opened each time the PC is switched on by the user. PIN the application fro the Start menu to the Task Bar to make it easier to access. Click on it to start it and minimise it again Start packing and labels will print on the PC default printer There is no need to open Event as the application works without it physically open. Application Open and minimise each shift. ROUTE configuration In ROUTE configuration, you can see if Print-to-Label is active. Application Open and minimise each shift. 1/2 Requirements Requirements to use Direct-to-Print A valid Event account with ROUTE, integrated parcel carriers with valid accounts. A valid interface from your ERP to Event [including the Label Station tag] Ability to download the windows application to each PC on each Label Station .net framework on each PC (https://dotnet.microsoft.com/en-us/download/dotnet-framework/thank-you/net48-web-installer ) A default label print for each Label Station PC A package to put the label on... Support process At any point, when the application cannot connect and 'stops listening for labels' we will automatically generate a support ticket to the 3T Service Desk and your Admin account email address. This will be considered a Priority support ticket and acted on with immediate effect. Where a label cannot be returned, an error label will be produced to advise you of the issue If a label has a hazardous code associated we will generate an additional label to advise of this. * Label generation speed is approximate and based on the quality of your internet connection. Tested as below: http://www.speedtest.net Download speed 73.92 Mbps Upload speed 86.70 Mbps Response time 10 ms

Home - Documentation - Validation and certification (Event Go) Validation and certification Event Go Documention Event Order API (POS) About our Partnership How does it work? Integration flow Additional information Event Go API (POD) Overview Our test scenarios are meticulously crafted to ensure partners have accurately configured their systems to seamlessly interact with our Delivery as a Service APIs. Prior to going live, partners must successfully pass certification tests to validate integration against our specified requirements, ensuring a reliable interaction with our delivery services. Key verification points include: Estimate Payload Verification: Validate parameters such as weight, preparation duration, alcohol availability, target delivery time, and address accuracy. Delivery Payload Verification: Assess parameters including target collection time, vendor order ID, and special instructions. Request Identifier Mapping: Ensure proper mapping of requestId as a unique identifier for each SaaS delivery. Delivery Creation Verification: Confirm partners create the NEW, UPDATE, CANCEL, COMPLETE delivery API call to verify creation. De How does it work? Onboarding Getting started Delivery simulation Validation and Certification

Top of Page Privacy Policy Hello A.I How does A.I work? Artificial intelligence (AI) works by ingesting massive amounts of data, finding statistical patterns within it using complex math and algorithms, and then applying those learned patterns to make predictions, solve problems, or create new content on its own The Three Core Steps of AI Data:The system reads millions or billions of examples like photos, text, or sounds. Training: Algorithms search for recurring connections and rules, adjusting internal math settings to minimize mistakes. Inference: The trained model uses what it learned to respond to new inputs, acting like a super-powered prediction engine Privacy Policy

Home - Documentation - Getting started (Event Go) Event Order API (POS) About our Partnership How does it work? Integration flow Getting started Environment-Specific Endpoint: In this section, you’ll find a comprehensive list of endpoint URLs tailored to different environments. Whether you’re testing on staging, developing locally, or production, ensures seamless integration by selecting the appropriate URL corresponding to your environment. Here is the Environment Specific Endpoints: UAT - POST https://event3tuat.azure-api.net /Oasis/omf PROD - POST https://event3t.azure-api.net /Oasis/omf General API Management Gateway - https://event3tuat.azure-api.net Event Go Documention Additional information Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification next... Delivery simulation

Self-serve rate card import Uploading rate cards for carriers you connect with To use a non parcel carrier, you will need to upload a rate card A rate card simply shows where a carrier will deliver to and how much that delivery will cost... If you are using ROUTE in Event you will need to connect to carriers. To allocate routes to your connected carrier you need a rate card. Carriers in Event have a standard universal rate card or you can arrange and negotiate your own rates. This guide assumes you have created an account with a carrier, connected to them through Event and now need to upload your negotiated rate card so you can start allocating routes. Connect and allocate Decide on a carrier and create an account [contract] with the carrier (outside of Event) Connect to your chosen carrier through Event* Receive a 'carrier now connected' notification Create a rate card, upload. Start allocating routes to your carrier * A carrier will add themselves to EVENT through being invited. They only need to be invited once and in doing so will create access, login details and a 'connected' presence in the Event ecosystem overall for all current and future Accounts to connect to. You just need to upload a rate card.. * There is not set requirement for naming a rate card upload file. We will add a date time stamp to make sure it is unique Do not change the format of these rate cards! Download, change the date but not the headers or the tab names Which rate card do i use? The rate card templates are simply based on the a tariff in WEIGHT or PALLET based. Are you adding a groupage pallet tariff or one based on weight? hint: FTL is always added as weight. See the examples below to help you quickly create a rate card. If creating an FTL tariff, use the Template 1. This includes EXW. If creating an Groupage PALLET based tariff, use the Template 1 If creating an Groupage WEIGHT based tariff, use the Template 2 Standard plt / weight tariff click to download Template 1 FTL all postcode Rate card template PLT - Day / night / weekend / holiday 19-04-2023 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc This tariff includes where a carrier provides different costs based on the time of day or day of week It is only for the FTL sheet, not for Groupage Column J cannot be used if any of columns O-T are being used. Leave J as = blank Column U can be used with either column J or columns O-T. It can also be used on its own. The daytime setting can be configured in AccountVITALS / Setup Basics / Rate Card Bank holidays can be configured in AccountVITALS / Setup Basics / Holidays The headers for columns O-U will be used to show as the servie in Change Carrier Template 2 Groupage all UK postcode rate card template PLT. Upto 10 plts 12-02-2019 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc Template 3 Rate card template weight - Groupage 12-02-2019 - AP Hint: Its important to define if the Groupage tariff is per weight band or pallet. The excel spreed sheet tab defines this Template 4 Rate card template weight bands- Groupage 17-09-2021 - AP This function includes 2 new columns. 'PER' column and 'ROUNDING' column. PER = rate per kg. This can be 1 as std or 100kg ROUNDING = set to round by, e.g. 10 (to mearest 10) The PER calculation example is: 99-250kg line in tariff rate = 39.98 Set PER rate as 100kg Shipped 145kg Set rounding to 10kg (nearest 10kg) so 150kg calculated rate = 39.98 x 1.5 Template 4a Rate card template weight bands with minimum charge 14-09-2022 - AP Template 5 Rate card template pallet per lifts - Groupage 17-09-2021 - AP This function is the standard Groupage rate card by pallet. The difference is a configuration to set between per plt or per lift. This Lift configuration will use the stackability from the Stop. If 7 plts and stackable, lifts = 3 lifts The default is per pallet. Groupage rate card by m3 Template 6 GRP rate card by m3 08-05-2021 - AP Hint: Any postcodes not used can be added as '0' rate to be used as adhoc Use column F & G for calculating Stop volume (10-15 m3 band = 4.50 x total m3) Use column H & I for calculating Stop volume as a fixed total cost (10-15 m3 band = 180.00 fixed rate) To set the calcuation at PLANNED or DESPATCHED status, use the configuration in Carrier VITALS To speed up creating multi equipment type FTL rate cards... Template 7 FTL x3 equipment types UK postcodes template 12-02-2019 - AP Template 8 FTL x2 equipment types UK postcodes template 12-02-2019 - AP Distance tariff by metric Template 9 Distance tariff from a source point 12-02-2019 - AP This distance tariff allows for a cost to be calculated from a source postcode and by a metric, i.e. per tonne Distance tariff from point A-B Template 10 Distance tariff from a source point 12-02-2019 - AP This distance tariff allows for a cost to be calculated based on the actual distance banding from any location to any location. It is not dependant on any metric, simply a cost per distance by an equipment type Parcel tariff by service Template 12 Parcel tariff by weight and service 11-10-2021 - AP Tariff for calculating parcel wieght and service through SLM rules What if i want to use a carrier but i have no rate card? You do not need to add a rate card for a carrier to be able to use the carrier in Event. Using Event's 'Spot Rate' function lets you allocate to any carrier at any time Rate Card Validation So once you have uploaded a rate card, AMI will validate the contents and notify you of the result. The validation will include format and contents, providing information, where a failure occurs on what the failure is. Initial validation that must be passed to proceed; 1. Correct column headers Validation will fail if the headers are named differently to the template. Validation error message ' Column headers are not named correctly' 2. Correct order of the columns Validation will fail if the columns are not in the correct position. Validation error message ' Columns are not in the required positions' 3. Carrier ID Validation will pass if the carrier ID exists on the Account being uploaded to and will fail if the carrier does not exist in Account receiving upload. Validation error message for notification and storing ' Carrier ID must match the carrier's code in Carrier VITALS' Specific validation 1. Origin country Is required. Format is ISO code. Validation error message ' Add a valid ISO 2 digit country code, i.e. US, GB ' 2. Origin code Is required. Format can be numbers or letters. CV, 01, 850. Validation error message 'Valid post or area code required in the format of at least the 1st 2 digits of the code, i.e. CV, 11, 98' 3. Destination country Is required. Format ISO code. Validation error message ' Add a valid ISO 2 digit country code, i.e. US, GB ' 4. Destination code Is required. Format c an be numbers or letters . CV 22 6HL , CV 22, CV , 01, 01000, 10000. Validation error message 'Valid post or area code required in the format of at least the 1st 2 digits of the code, i.e. CV22, 11, 98' 5. FromBand Is required. A number of at least 0. Can be format 1.000000001. Validation error message 'Must add a number in the format 1 ' Example: for FTL this would be 1 6. ToBand Is required. A number of at least 0. Can be format 1.000000001 if Groupage. Validation error message 'Must add a number in the format 2.000000001 ' Example: for FTL this would be 99999 7. Stop rate Is required if Delivery type = FTL. Format must be 0.00. Validation error message ''Rate must be included for FTL and cannot be left empty. It can be 0.00' 8. Equipment Is required. Validate the equipment type against the Account Equipment database and if a match can be found allow, if no match fail validation. Validation error message '[failed equipment name] is not a valid equipment type for this Account. Please use a valid type or update your equipment' 9. SLM rule Not required. Default is blank. This is a specialist rule for RULE ASSIST only. Max characters = 10 Validation error message where not matching rule is found in SLM 'No matching rule found in Route Assist rules' To use this rule, ROUTE ASSIST rules for the carrier must match those in the rate card. To use this function, add the SLM rules to the ROUTE ASSIST column called 'Groupage type' *this rule will lookup ROUTE ASSIST rule, take the associated Groupage Type and when looking up the rate card, will look to match a SLM rule to the Groupage type added. 10. Mode Is required. Must be LAND, AIR or SEA. AMI will default to LAND if not added. If added but not one of the 3... Validation error message 'Mode must equal LAND, SEA or AIR in this format ' 11. Service Is required. Default is Economy. AMI will default to Economy if not added. If added but not Economy, check for match in Account's Service and update. No validation message. 12. Delivery type Is required. Must be '2' for FTL or '4' for Groupage. Validation error message 'Delivery type must be '4' for GROUPAGE or '2' for FTL' 13. Cost Is required. validation just a number. Must be a number in format 0.00, 200.00. Can be 0.00 if no rate is known. Validation error message 'A rate must be included and cannot be left empty. Format is 0.00. It can even be 0.00 '

Home - Documentation - Point-of-Order (Event Order) Event Order API (POS) About our Partnership How does it work? Integration flow Additional information About the Partnership Our Point-Of-Sale (Event Connect) integrations put your customers and order management processes front and centre, pushing incoming sales orders directly from your Point-Of-Sale system automatically. This means: No more copying customer orders from your Point-Of-Sale manually No more excel spreadsheets, macros or convoluted formula's Staff can work to existing business workflows Reduced training overhead for your staff Fewer orders with wrong or missing items Simple, consolidated inventory management, reporting and accounting Order changes from customers (item names, dates, quantities) made in your system are immediately reflected in Event, Delivery apps and reporting Event Go Documention Event Go API (POD) Overview How does it work? Onboarding Getting started Delivery simulation Validation and Certification Event Connect Capabilities Event Order API Event Order is a set of API's for order messages and their optimised TMS routes. Sending us new orders, updating or cancels provides the TMS with the most upto date order book that instantly updates to follow the ebb and flow of your sales. It also includes the completed Plan message, how Event planned the orders into routes It includes: Order message (OMF) Plan return Event Go API Event Go is a set of API's for the execution of the delivery. It includes Tracking updates Proof of Delivery Additionally requested costs Invoice information Event. TMS Plan result NEW order Order accepted UPDATE order Order accepted COMPLETE order Tracking updates Proof of delivery Cost additions Invoice details Planning optimisation Carrier integration Event Order Event Go Event Connect How does it work?