More and more customers and technology partners use the Plunet API to integrate external software solutions with Plunet. What is the best method here? What is possible and what should be kept in mind? These are just some of the exciting questions that will be answered in the API Track. The highlight will be a showcase session, presenting the current API connections to tools such as WordPress, Drupal, SmartQuery and to a CRM/CEO Dashboard app. That will definitely give you an appetite for more!

1. Connecting the Dots – The Plunet API Track
Part 1: WordPress & Drupal
Rachel Ferris
Michael Harris
Acclaro

2. Acclaro Background
4500+
Translators
60+
Languages
250+
Clients
85
Staff
Founded in
2002
7 Global
Offices
Partner Since
2010

3. Our Customers

4. Industry Context
 Shift to continuous localization
 Orders counts up
 Word counts down
 More content in 3rd party systems
 Not all support easy import/export

5. Customer Context
 Want efficient tech-enabled solution
 Easily move content from internal systems to LSP
 Limit/remove manual processing
 Multiple tech solutions available
 Newer client-facing platforms solve some client challenges
 Not always optimal for LSP
• Increased admin effort for PMs: orders, jobs
• Non-standard TM features for linguists

6. API Integration
 Create Quotes
 Create Orders
 Attach files
 Select languages
 Due dates
 Comments
 Developer-friendly
 RESTful web service
 3rd party content
integrations
 Managed through
dashboard

7. API Connectors
Prep
Translate
ReviewTransfer
Receive
Content
Repositories
A
P
I
Dashboard & Console

8. Demo

9. Dashboard

10. Request API Token

11. WordPress: Apply Token

12. WordPress: Select Content

13. WordPress: Submit to Acclaro
for Translation
 s

14. Automated Order Creation

15. Status in Dashboard &
WordPress

16. Delivered Status Triggers
Automated Delivery

17. WordPress: Files Delivered
from Plunet

18. Drupal: Another CMS -
Same Connectivity

19. File Connectors

20. Benefits of API & Connectors
 Key Benefits
 Connects Plunet to customer systems & content platforms
 Easy for clients to integrate translation into their process
 Operational efficiencies
 Compete with leading tech-enabled service providers

21. What’s Next?
 New file connectors: One Drive, Google Drive
 Upcoming CMS integrations: Craft, AEM
 Gauging interest from Plunet LSPs for independent SAAS offering

22. Thank you
Any Questions? Let’s talk.
Rachel Ferris ∙ rferris@acclaro.com
Michael Harris ∙ mharris@acclaro.com