page 1
Table of Contents
Introduction
Platform basics• Tradeshift as a multi-tenant platform• Network and identity• The Web application
Using Tradeshift to collaborate and exchange documents
• Collaborative extensibility• Message exchange modes• Messaging standards• Using machine learning to make
sense of images• Localization and customization• Extending beyond electronic invoicing
Getting data in and out of Tradeshift• REST API• Other integration options• Channels
• Point-to-point exchange• Broadcast
• Message formats and message conversion
• Document storage
Tradeshift integration scenarios• Small businesses on Tradeshift• Small business to large business,
using document forwarding• Small business to large business,
using API integration• SaaS integration with third-party
accounting solutions
Security and compliance• Auditing standards• General account security properties• Communication security
• Web security• Integration services security• API-level security
• Document level security
Tradeshift infrastructure• Scalability• Quality of service• Global reach
Tradeshift for developers and 3rd-party service providers
About Us
page 2
Tradeshift is a collaborative platform that supports any processes involving the exchange of structured, electronic business documents between businesses of any size, for internal employee collaboration and process support. As a platform it allows customers and 3rd parties to integrate or extend it in order to support new processes, collaborations and document exchanges. It supports the creation of new user interfaces or apps for these extensions in a way that may be distributed through the Tradeshift app store, and across desktop, tablet and mobile devices.
At the heart of the platform is the network which allows businesses to build networks of suppliers, customers, employees and other collaborators which they can use to speed up processes, reduce the noise, increase the quality of data, and use the combination of the network and real-time data to explore new business opportunities.
Any collaboration or exchange of data is based on industry-neutral open standards and open APIs ensuring that customers truly can access and have control over their data. The choice of an industry -neutral open standards format in combination with an open APIs is at the heart of extensibility strategy — allowingcustomers,integratorsand3rdpartiestobuildtrulycollaborativeE2Eprocessflows,regardlessifthesespanmultiplesystems(cloudoron-premise),involveemployeesorthecollaboration between suppliers, customers or 3rd parties.
Technically,Tradeshiftisrealizedasamassivelyscalablecloud-basedSaaS(Software-as-a-Service)platform, providing rich integration points both for customers and suppliers, for in-house and cloud-based ERP-systems, external SaaS solutions, as well as in-UI application extensions for desk-top, tablet or mobile.
The platform deals with the connectivity between business partners, the transport and storage of business documents such as invoices, purchase orders and other types of documents, as well as process states and informal communications between business partners. Tradeshift also supports a variety of outgoing channels including email with PDF, and connectivity with government and commercial procurement networks such as PEPPOL, INTTRA and other VAN networks.
The Tradeshift concept of “business network” is based on social network patterns and concepts. The network is the basis of communication, business message exchanges, and collaboration, both between companies, and within the company itself. The business network is where users of Tradeshift maintain and use their business relations to collaborate with business partners and their colleagues.
Introduction
page 3
A key goal of the Tradeshift platform is for it to be extended with new processes, collaborations and user interfaces. All functionality is exposed through the Tradeshift API to customers, 3rd party app developers and integration specialists. The Tradeshift API provides an integration point that is rich, lightweight, secure and reliable, and allows Tradeshift to be extended both for scenarios that include system-to-system integrations, supporting new company-internal processes between employees or supporting collaborations between buyers and suppliers.
In addition to enabling exchange of documents and communications between business partners, Tradeshift also supports the process of on-boarding suppliers, customers and other business partnerswithminimalmanualeffort.Theplatformofferstoolstomanagetheon-boardingprocessin large-sale segmented campaigns, while keeping track of the various stages of the process and the user engagement.
This technical whitepaper provides an overview of the Tradeshift platform, covering integration, security, quality, scalability, isolation, multi-tenancy and more. The goal is to provide readers with an understanding of how the Tradeshift platform may be utilized to support business transactions and collaboration between two businesses, and how the platform supports extending the current functionality set.
Tradeshift as a multi-tenant platform
Tradeshift is realized as a true multi-tenant platform. Each company on Tradeshift corresponds to a ‘tenant’ and is a separate administrative unit with its own users, data storage, localization, extensibility and API access controls. Nobody outside of the account, unless explicitly authorized by the account holder, can access data or functions within the account. Any form of collaboration or message exchange involves explicitly exchanging the relevant business document over the network to other Tradeshift tenants, or, if the party is outside of Tradeshift, through other channels such as email or externalValueAddedNetworks(VAN)serviceproviders.
The concept of a “strong tenant isolation” refers to the ability to see each account as a truly separate unit. This is what allows the platform to control the location of data storage, to manage security isolation of each account, to ensure strong access separation when the API is used for integrations or other extensions of the basic platform, for example in the form of apps. Access to a tenant data is based on the same paradigm of explicitly requesting and granting access permissions that you see when installing apps on a mobile phone.
Platform basics
page 4
Network and identity
The Tradeshift network deals with the identities of companies and users within the network. For companies a minimum set of information must be available for them to be visible and available in the network for other companies to request connections with them. Employees may also be visibleonthenetwork,forexampleforthepurposeofdirectinginvoicesatspecificemployees.
The concept of the network is based on the principle that each participant controls their part of the network — whichcompaniesandindividualstheywishtocollaboratewith.
The Web application
TheTradeshiftwebapplication(go.tradeshift.com)istargetedbusinessesthatwantaneasy-to-usetool to collaborate with companies and individuals within their business network. Out-of-the-box it supports their invoicing and ordering processes as well as basic collaboration, but may be extended with any feature or process that is available through the Tradeshift apps marketplace.
The web user interface is designed to work well with a variety of computing platforms, including desktops, tablets, and mobile phones. The web application utilizes a purpose-built document and message exchange platform. Figure 1 illustrates the technical architecture of the Tradeshift platform.
Figure 1: Tradeshift platform architecture
Com
plia
nce
Serv
ices
D
igita
l Sig
natu
re
Mgm
t Eng
ine
Dep
loy
Engi
neREST Interface (API)
DATA TIER
BUSINESS LOGIC TIER
PRESENTATION TIER
MAN
AGEM
ENT
TIER
PART
NER
SER
VICE
S TI
ER
Shared Datastore Per-Tenant Datastore
API proxyWeb User Interface
Core Services
SearchCluster
QueueCluster
IntergrationServices
PaymentServices
page 5
Collaborative extensibility
The goal of the Tradeshift platform is to support the concept of collaborative processes in the networkthatincludesbothcompanies,employeesandmayspancompany-specificsystemssuchasERPandworkflowsystems.
The foundation for this is the open API, the use of industry-neutral open message standards, the business network, and the direct support of collaboration actions and events. This allows customers, integrators and 3rd party app developers to extend Tradeshift with processes and business data thatincludealltypesofparticipantsinthenetwork — fromsmall,one-manbusinessesrelyingontheweb interface tor large, multi-national businesses dealing with large transaction volumes and have complexsetupsinvolvingin-houseERPandworkflowsolutions.
Collaboration is directly supported throughout the platform on any type of object such as business documents. Objects may be shared and assigned, both within a company and between companies. Collaborationmakesitpossibletoshareandtracktasksassignedtospecificindividuals,createoverviews such as TODO-lists that supports collaboration.
Thecollaborationfeaturesareatthecoreoftheworkflowcapabilities,thatbuildontopofthecoreTradeshift platform.
Message exchange modes
Tradeshiftoffersdifferentmodesofinteractiondependingonthetypeofbusinessandwhat services are required to support business processes:
• For businesses that exchange a low invoice volume and typically create invoices using word processing applications such as Microsoft Word, the Tradeshift web application can be leveraged to create, send and receive invoices and other business documents.
• For businesses that use accounting software, such as QuickBooks or Sage 50 to create invoices, these invoices and related business documents can be imported and sent from the Tradeshift platform using plug and play connectors.
Using Tradeshift to collaborate and exchange documents
page 6
• For businesses that exchange large volumes of business documents and use an ERP system, such as Oracle or SAP, Tradeshift can exchange messages between ERP systems using secure filetransfer,APIintegrations,orvendor-specificconnectivityadaptors.
• For application developers and makers of business software, Tradeshift’s REST API can be leveraged to exchange business documents and messages.
Figure 2 illustrates a sample exchange of invoices between two businesses, demonstrating how businessdocumentsandrelatedmessagesflowthroughtheplatform.
1. Asupplier(sender)createsandsendsaninvoicetoabuyer(receiver)throughTradeshift,either through the web application, one of the integration channels, CloudScan, or by using one of the connectors.
2. TheinvoiceisconvertedtoXMLandstoredonthesupplier’saccountonTradeshift(senderaccount).
3. Acopyoftheinvoiceistransmittedtothebuyer’saccount(receiveraccount),togetherwithanysupportingdocuments(suchasattachments,signaturesandsourcedocumentsincaseaconversionwasinvolved)
4. The invoice is either pushed to or pulled by the buyer’s ERP system for further processing.
5. Thestatusesoftheinvoice(e.g.sent,accepted,paid)iscommunicatedbetweenthetwopartiesthroughouttheexchange — alsointheformofXMLmessages.
SUPPLIER SENDERACCOUNT
RECEIVERACCOUNT
BUYER(ERP system)
1 4
5
2 3
XML
XML XML
Figure 2: Example message exchange
page 7
TheTradeshiftplatformacceptsotherformatsthanXML — bothincludingcomma-separatefilesandimages or PDFs of invoices which are then automatically transcribed using our CloudScan technology (basedonOCRandmachinelearning).Howeverintheend,Tradeshiftconvertsallofthese documentformatstoacanonicalXMLformatwhichisusedastheexchangebetweenthedifferentparties — beforepossiblybeingconvertedagaintosomeotherformatupondelivery.Bothformats(theoriginalformataswellastheXMLformatthatTradeshiftcreatesregardlessofthesourceformat)willbeavailabletotheparties.
Notethatallmessageexchanges — whetherit’sbusinessdocumentssuchasinvoicesandorders, orifit’seventsbeingfiredwhenaprocesschangesit’sstate(sayandeventindicatingtheaninvoicehasbeenacceptedbythereceivingparty) — willbeexchangedinthesamefashionasillustratedabove.
Messaging standards
TradeshiftusestheUBL(UniversalBusinessLanguage)XMLstandardasitscoremessageformat.UBL is an open, industry-neutral standard being developed internationally by the OASIS consortium. For example, it is the core message format for the pan-European PEPPOL procurement infrastructure.
Using machine learning to make sense of images
With CloudScan, Tradeshift is unique on the market to utilize a 100% machine learning based approachtoconvertunstructuredandsemi-structuredcontent(images,PDFs)intostructured data(XML)thatissuitedtobecommunicateddirectlytotheERPwithoutmanualprocessing.
The combination of machine learning techniques with the network based approach means that quality rate constantly improves as the network processes more messages, without the need for eachusertodotimeconsumingandper-supplierorper-customerconfigurationtocapturethedifferentvisualformatsofdocuments.
This strategy fundamentally changes the cost of converting unstructured data into structured by offeringtheeconomyofscaletoanyuserofCloudScan.TradeshiftissteadilyexpandingtheCloud-Scan technology to more business data domains.
Localization and customization
TheTradeshiftWebsiteislocalizedtokeymarkets;businessesresideindifferentcountriesmayusetheirspecificbusinessidentifiers,VATidentifiers,taxesandsoon.Tradeshiftuserscancustomizerelevant details such as:
page 8
• Businessandtaxidentifierschemes• Invoice taxes and rates, currencies• Address information and payment means• UIlanguageandcharacterset(suchase.g.forChinese)
Furthermore,throughthe“businessfirewall”Tradeshiftsupportsthevalidationoffieldswithinbusinessdocuments.Mandatoryfieldsandcustomvalueformatscanbespecifiedtoenforceaspecificformatforaninvoicefieldatthepointofinvoicecreationtoensurecorrectnessofinvoicesat the moment they are submitted.
Extending beyond electronic invoicing
TheTradeshiftplatformoffersmuchmorethanelectronicinvoicing.
• Business network management: Use the network to manage trusted business connections, communicate and collaborate
• Business Network Messaging: Shared messages with your network, or business-to-business messaging
• Growing feature set for small business users: The Web UI can be extended by 3rd-party developers of Web Applications
• Document storage: All messages communicated through Tradeshift are persisted and kept for long-term storage
• Channel management: Dispatchingofmessagestodifferentchannelssuchasemail,FTP,Tradeshift, Danish Nemhandel infrastructure and so on.
page 9
REST API
The Tradeshift API is based on a set of REST services that support both internal Tradeshift appli- cations and external integrations and apps. The RESTful architecture supports the platform goals of scalability, modularity, interoperability, reliability and security.
EachresourceoftheTradeshiftplatform,suchasbusinessdocuments,workflowevents,businessnetwork identities and connections, are exposed as REST resources for customers and app developers to use for integrations or extensions to the basic Tradeshift feature set.
The REST API is the foundation for the extensibility and integration options of Tradeshift. Other integration options such as FTPS and sftp are based on this basic interface.
TheRESTAPIallowsresourcestobehandledbothasXMLandJSON — withtheexceptionoftheUBL-basedresources(e.g.invoices,orders)whichdonothaveameaningfuljsonrepresentation.
Other integration options
The Tradeshift platform supports a growing set of other integration options towards buyers and suppliers including FTPS and sftp, both with push- and pull-based options. For example, the ability to forward documents supports a business integration scenario where the business initially receives invoices on their Tradeshift account, but need to have them forwarded to their on-premise ERP in real time e.g. via an FTP server.
ForFTPS/sftpanamingandsemaphoremechanismisemployedtoensurereliabledeliveryoffilesaswellassupportingfilessuchasattachments.
WhileTradeshiftnativelysupportsUBLwearesupportingagrowinglist(25+)ofindustrystandarddocument formats.
Channels
The channels that Tradeshift supports for message exchanges and other types of communication are growing. There are two types of channels in play: message exchange and broadcast channels.
Getting data in and out of Tradeshift
page 10
Point-to-point exchange
Message exchange channels are bilateral channels, and include account-to-account communi-cationifbothpartiesareontheTradeshiftplatform,Tradeshift-to-email+pdf,Tradeshift-to-FTPS/sftp,andTradeshift-to-VAN/EDI(suchase.g.PEPPOLorINTTRA).TheingoingchannelsincludeFTPS/sftp,API,receivingbusinessdocumentsviaemailorimage/PDFupload(usingCloudScanforOCR+machine-learningbaseddataextraction),receivingfromexternalEDI/VAN,flat-fileuploadsandconnectors.
All messages such as invoices or purchase orders are sent transactionally rather than being shared directly. Copies will exist both at the sender and the receiver side, thereby respecting the principles of tenant isolation and strong data protection.
Broadcast
‘Network shares’ are broadcast messages you can send to more receivers within your network. An example of such a message is the ‘network tell’ that you can send through the web UI as a text message you share with your entire business network.
Message formats and message conversion
TradeshiftusestheUBL(UniversalBusinessLanguage)industry-neutralXMLstandardasitscoremessage format. UBL is an open standard being developed internationally by the OASIS consortium, and is in operation in 30 countries worldwide. For example it is the core message format for the pan-European PEPPOL procurement infrastructure.
UBLdefinestheformatandsemanticsofmanybusinessmessagessuchasinvoices,creditnotesandorders,aswellasdefininganumberofstandardbusinessprocessesspanningmultipledocument exchanges, such as orders, order accepts, invoices and so on.
TheUBLspecificationisveryexpressiveandsupportsarichsetofelements,identifierschemesandextensions. Tradeshift uses a subset of UBL to accommodate the requirements of many industries. Amongotherthings,thissubsetofUBLencompassesthemostcommonbusinessidentifiertypes,paymentmeansdefinitionsandtaxtypesinthemajormarkets.
Documents retrieved, stored or dispatched via the API are also in the form of UBL documents. For example, to create and dispatch an invoice using the API, you would:
page 11
1. Create the UBL XML for the invoice2. PUT the complete XML invoice to Tradeshift as a REST resource3. PUT a dispatch resource with reference to the newly created invoice resource
In addition, the Tradeshift platform supports document transformations in various scenarios:
• Documentsreceivedfromexternalnetworksmaybetransformedfromanetwork-specificformat to the Tradeshift UBL subset upon receipt
• Documents uploaded via the web site may be converted from the most popular small business• Documentsforwardedtoexternalnetworksmaybetransformedtonetwork-specificformats
Tradeshiftsupportsagrowinglistofstandardindustrydocumentconversions(currently25+),includingEDI,comma-separatedfilesandothernon-XMLformats.
To lower the barriers of document exchange and collaboration even further, Tradeshift supports the receipt of unstructured message formats. When Tradeshift receives invoices in unstructured formsuchasimagesandPDFfiles,theCloudScanOCR-andmachinelearning-basedtechnologyisemployed to convert these to UBL XML before being forwarded to the receiver.
Document storage
Documents(e.g.invoices,orders)andmessages(e.g.comments,workflowstatechanges)aretreatedequallyasXMLmessagesandareallstoredwithintheconfinesofthetenantboundaries of each business. There is strong isolation between the message stores of individual tenants or businesses so that they may be stored in separate geographically located data centers.
Core business documents such as orders and invoices are signed when they are persisted and before being exchanged in order to achieve strong integrity. Business documents are stored indefinitely,oruntilabusinessexplicitlyrequestsdeletionofit.Alldataisbackedupregularlytoencrypted storage in redundant physical locations.
page 12
DifferenttypesofIntegrationswithTradeshiftaresupportedwhetheryouarealargeenterprise,small business, external service provider, or a developer of extensions and apps that are distributable through our apps marketplace. Below are a number of example integration scenarios in order to illustratehowdifferentplayersmayintegratewithTradeshift.
Small businesses on Tradeshift
If you are a small businesses and send a small volume of invoices, you may send invoices using Tradeshift’swebapplicationasshowninFigure3.IfbothpartieshaveaTradeshiftprofile,exchangeiskeptwithintheTradeshiftplatform.ApartywithoutaTradeshiftprofilemayreceiveinvoicesasPDF-invoices via email. If the buyer does not have an ERP the buyer might be using the Tradeshift web UI as well for handling the incoming invoices.
Small business to large business, using document forwarding
Small businesses can use the Tradeshift web site to create and send their invoices to large enterprises, shown in Figure 4. For large buyers that might have an ERP system, they may choose to receive invoicesusingreal-timefileforwardingfromTradeshifttothebuyerusingatransportsuchasFTPS
Tradeshift integration scenarios
Figure 3: Exchanging electronic invoices using the Tradeshift web application
SUPPLIER
SENDERACCOUNT
RECEIVERACCOUNT
BUYERXML XML
WEB APPLICATION
page 13
or SFTP, before moving the data to the internal ERP. The large enterprise can also send business documentstoanysmallbusinessorotherenterpriseonTradeshift,fromtheirERPorworkflowsystem,usingtheAPIoroneofthefiletransferoptions.
Small business to large business, using API integration
Inadditiontousingthefiledispatcher,documentscanbetransmittedusingtheTradeshiftAPI, asshowninFigure5.Thishasthesameeffectasusinganyofthefiletransferoptions.Thebuyermay choose to take advantage of the richer feature set of the API for example to manage their network of suppliers or customers.
Figure4:ExchangingelectronicinvoicesusingtheTradeshiftwebapplicationandtheTradeshiftfiledispatcher
SUPPLIER
SENDERACCOUNT
RECEIVERACCOUNT
BUYERERPXML
XMLWEB APPLICATION FILE DISPATCHER
SUPPLIER
SENDERACCOUNT
RECEIVERACCOUNT
BUYERERPXML
XMLWEB APPLICATION TRADESHIFT API
Figure 5: Exchanging electronic invoices using the Tradeshift web application and the Tradeshift API
page 14
SaaS integration with third-party accounting solutions
For external SaaS such as for example an online accounting system, Tradeshift exposes a basic user registrationwebflowinadditiontotheAPIintegrationpossibilities.OncetheSaaShasintegratedtowards the API, and a user has an account on Tradeshift and has authorized the SaaS to manage documents and dispatches on the users account through the API, the user can send and receive documents through the SaaS solution just as if it was through Tradeshift.
Auditing standards
TradeshiftisISAE3402certified(thesuccessortoSAS70).Thecontrolsofthisreportcoverthefollowing security-related aspects:
• Integrity of business messages• Authenticity of origin• Archiving• Access restrictions to data and functions
Security and compliance
SUPPLIER
SENDERACCOUNT
RECEIVERACCOUNT
BUYERACCUNTINGSOFTWARE
FILE DISPATCHER
TRADESHIFT API
XMLXML
ERP
Figure 6: Exchanging electronic invoices with third-party accounting application
page 15
Tradeshift builds on secure cloud platform with data centers that conform to the following security, infrastructure and related standards:
• SOC 1/SSAE 16/ISAE 3402• SOC2+SOC3• ISO27001certified• FedRAMPCompliantCloudServiceProvider(CSP)• PCI DSS level 1 compliant• DoD 5220.22-M / NIST 800-88 for decommissioning of hardware
General account security properties
The platform features strong tenant isolation, meaning that per-user storage is considered isolated units. For example, when sending an invoice from one account to another, a copy of that invoice is created and sent to the the receiving account, rather than this document being shared across the twoaccount.Thisallowsforscenarioswheredocumentsarephysicallystoredindifferentgeographicallocationswithdifferentprivacyorotherregulatoryrequirements.
Communication security
Web security
Forusersofthewebapplication,allcommunicationisprotectedwithSSLusingEVcertificates(‘extendedvalidation’certificates).Tradeshiftsupportsanumberofauthenticationoptionsrangingfromusername/passwordwithemailverificationtoSSOsolutionsincludingSAML2.0.The use of SSO allows users to take full control over authentication policies and rely of in-house identity providers and local administrator policies.
Integration services security
IntegrationservicesincludeAPI-basedintegrations(seebelowforsecuritypropertiesoftheAPI)aswellasSFTPandsftp,bothwithforwarding.
API-level security
At the API level, 2-legged OAuth together with SSL. OAuth signs messages to ensure integrity, and SSL provides privacy.
page 16
Multiple access keys may be issued to businesses or integrators on the platform, and each tenant may grant or revoke access to individual key holders. This allows the same scheme to be usedforbothenterpriseintegrations(wherealargebusinesswillneedtoaccessitsownaccount),andSaaSintegrationscenarios,whereasingleSaaSproviderneedslargenumberoftenants to grant access to tenant data.
Document level security
Business documents such as orders and invoices are signed when they are persisted to ensure the integrity of the documents. Tradeshift keeps redundant, encrypted backups of all data. Tradeshift maintainsadedicatedsecuritylayerintheplatformforensuringtenantdataisolation,asreflectedin our ISAE 3402 controls.
Inapplicablejurisdictionsorwheneverrequiredbycustomers,signaturesprovidedbycertified3rdparty signature services are available in addition to the basic integrity signature.
Scalability
Tradeshift has been developed as a massively scalable SaaS cloud platform. The underlying cloud platform gives us the elastic scalability required to keep operational costs to a minimum and ensures availability of resources at all times. The platform architecture gives us the ability to react to changesintrafficpatternswithjust-in-timeresourceprovisioning,andtosupportglobalscalabilitythrough a multi-datacenter stragey.
Scalability is ensured by three main properties of the platform:
• The Cloud Platform: The underlying cloud platform ensures that the platform is able to scale elastically both up and down with the demand, both regarding storage and service throughput
• The stateless, REST-based architecture is the enabler of on-demand driven up- and down- scaling, caching and failover
Tradeshift infrastructure
page 17
• A dynamic “continuous deployment” framework developed by Tradeshift that allows rapid deployment of new services across regions
• Real-timeandhistoricalmonitoringoftrafficpatterns
Quality of service
Tradeshift is committed to provide high quality service through its operations. Tradeshift’s ISAE 3402 certificationcertifiestheoperationalmaturityoftheTradeshiftplatformandinfrastructurewithrespect to monitoring, uptime, availability, failover, storage, integrity and general operational processes. Tradeshift is committed to give integration partners and customers real-time insight into the opera-tional status of our infrastructure and operations.
Global reach
The RESTful platform architecture with its stateless services and strong tenant isolation is the foundation for its scalability. Together with the deployment framework developed by Tradeshift, thearchitectureallowsTradeshifttoutilizeprocessingpowerandstorageindifferentregions,closeto the users of the service, ensuring excellent response times and low latency.
The design of the API has been driven by the desire to make it as simple as possible for developers to use and learn. The RESTful API presents a logical, resource-oriented view of the platform capabilities. The REST API has been designed to expose the full functionality of the Tradeshift platform. It is the sameAPIweexposeto3rdparties(integratorsandappdevelopers)thatTradeshiftusesinternallyto create our web UI.
The combination of REST, json/xml, SSL, UBL semantics and OAuth provides for a lean, simple and interoperable interface that allows developers to use existing client-side libraries, or, if they are working from legacy stacks that do not have out-of-the-box REST support, to still be able to create integrationswithminimaleffort.
ForintegratorsandappdevelopersTradeshiftoffersasandboxenvironmentthatmirrorstheproduction site with respect to API, platform functionality, and UI. A developer forum is also available, monitored and supported by the Tradeshift development team.
Tradeshift for developers and 3rd-party service providers
Web: tradeshift.comEmail: [email protected]: @tradeshift
Tradeshift Inc.612HowardStreet,Suite100San Francisco, CA 94105USA
Tradeshift DKNørregade36B,3rdfloor1165 Copenhagen KDenmark
LondonTradeshift Network Ltd.One Canada Square Level 42, Canary WharfLondon E14 5ABUnited Kingdom