• State Suggested Answer
  • Replies 1 reply
  • Answers 1 answer
  • Subscribers 2 subscribers
  • Views 122 views
  • Users 0 members are here
Options
Related

SDK/API to Language Weaver Cloud?

Roger Shu

Hi Dev team

Our client’s plan is to establish the connection between their internal content platform with Language Weaver (Cloud) for synchronized translation, and would like to confirm some technical details.

They are evaluating which method - SDK or  API - would more proper for their platform and business demands.

I searched but had very limited inforamation from Documentation and WIKI.

Could you please help share your commments or suggest any? Appreciate for your help.

 

Methods

Support synchronized translation?

Any links to detailed webpage?

Support asynchronous translation?

Any links to detailed webpage?

Support HTTP?
Any links to detailed webpage?

Support HTTPS?
Any links to detailed webpage?
SDK method

Yes？

？

？

?

API method

Yes

Synchronous translation - Wiki - Language Weaver - RWS Community

？

Yes

Technical Requirements And Best Practices

Yes

Technical Requirements And Best Practices

 Best regards,

Roger
emoji
Rate translation
×
Suggest better translation
×
Parents
  • 0

    Hi  , 
    The LW SDK is the preferred method for developing integrations to Language Weaver simply because it makes the development easier. Fundamentally, the SDK is using the same API to communicate with Language Weaver. In any case, I'd like to point you towards the Language Weaver Developer documentation: https://developers.languageweaver.com/api/lw/index.html, where you will also find the SDKs for various languages as well as a Postman collection that can serve as a developer playground to help understand the API endpoints.

    All of the methods above support synchronous translation, asynchronous translation and https (recommended). Please share those details with the customer developers. 

    We also recommend that LW integrations use https headers to identify themselves, making it easier to distinguish integration usage from other types of usage when reporting. 

    The following headers should be sent with each HTTP request made to Language Weaver.

    • Trace-App - [REQUIRED] Defines the Application Name for the integration - up to 128 chars

    • Trace-App-Version - [REQUIRED] Defines the version of the integration. String - up to 128 chars

    • Trace-App-Meta-Info - [OPTIONAL] Meta information that can be sent from the integration. String - up to 256 chars
Reply
  • 0

    Hi  , 
    The LW SDK is the preferred method for developing integrations to Language Weaver simply because it makes the development easier. Fundamentally, the SDK is using the same API to communicate with Language Weaver. In any case, I'd like to point you towards the Language Weaver Developer documentation: https://developers.languageweaver.com/api/lw/index.html, where you will also find the SDKs for various languages as well as a Postman collection that can serve as a developer playground to help understand the API endpoints.

    All of the methods above support synchronous translation, asynchronous translation and https (recommended). Please share those details with the customer developers. 

    We also recommend that LW integrations use https headers to identify themselves, making it easier to distinguish integration usage from other types of usage when reporting. 

    The following headers should be sent with each HTTP request made to Language Weaver.

    • Trace-App - [REQUIRED] Defines the Application Name for the integration - up to 128 chars

    • Trace-App-Version - [REQUIRED] Defines the version of the integration. String - up to 128 chars

    • Trace-App-Meta-Info - [OPTIONAL] Meta information that can be sent from the integration. String - up to 256 chars
Children
No Data