This is the multi-page printable view of this section. Click here to print.

Return to the regular view of this page.

Developer Center

Welcome to the Wordly Developer Center!

Here you will find pointers and documentation for integrating Wordly with your platform or application.

If you still have questions, please contact us at

1 - Developer API

Manage your account using Wordly’s REST APIs

You can now manage your account using Wordly’s REST APIs. You can view the OpenAPI documentation and try out the APIs yourself over at the API Reference page provided that you have a developer API key.

Please note that the API Reference page acts on live data, so be cautious when using it.

New features will be added regularly, so stay tuned for more updates!


Click here to view the changelog.

Getting a Developer API Key

A developer API key must be included as a header for all requests. You must have a Wordly account, and your account must be added to an allow list before you can create and use an API key. You can request to have your account added by contacting Wordly Support.

Once your account has been added to the allow list, you can create a non-expiring API key in the Portal by following these steps:

  1. Go to your user profile page in the Wordly Portal.
  2. Click on the ‘+’ icon button in the API Key row to create a new API key. Creating an API Key

If you do not see the API Key row in your profile, then your account has not been added to the allow list.

Getting Started

The following section will help get you started in using Wordly’s REST APIs. You can view the Open API documentation and try out the API yourself over at

Authorization Header

In order to use the API, you must include the x-wordly-api-key header with every request. The value of this header is your developer API key.

Example: x-wordly-api-key: f716690b-4e9a-4656-9523-7003637eb6cc

Failure to provide the API key in the header will result in a 401 (i.e., unauthorized) response from the server.


As new versions of the API are released, the request and response body schemas may change.

Wordly will include the x-wordly-api-version header in every response which tells you which version of the API the response body is conforming to.

Example: x-wordly-api-version: 1.0

Conversely, you can provide the x-wordly-api-version header in your requests to pin the request and response body schema to a specific API version. This ensures that your requests will continue to work when new versions of the API are released.

If you do not provide the x-wordly-api-version header in your requests, then Wordly will assume the latest API version. Therefore, we strongly recommend that you include this header with every request.


If an error occurs while processing your request, you will receive an HTTP error response. In most cases, you will receive a JSON response body in the following format:

  "message": "An error message will be here.",
  "code": 2003,
  "errors": [
      "message": "Any additional error information..."
      "message": "...will be listed here."

The code field is a numeric error code that is specific to Wordly. The table below is a list of possible error codes that you may receive in an error response.

Error Code Description
2003 Not authorized to perform this action.
2026 A field is not valid.
2041 Operation cannot be completed because the session is in use.
5001 Required fields are missing from the request.
5002 A field is not valid.
5004 Requested resource could not be found.

Deleting a Developer API Key

If you wish to delete and revoke your API key, then you can do so through the Portal. You are free to generate a new API key after deleting your existing one.

Follow these steps to delete your API key:

  1. Go to your user profile page in the Wordly Portal.
  2. Click on the trashcan icon button in the API Key row to delete your API key. Deleting an API Key


Caption Webhook Request Body

The Captions API allows an ongoing Wordly session to send live captions to a designated webhook URL. Captions will continue to be generated and sent until the Wordly session ends or until captioning is explicily stopped using the API.

A webhook URL must be provided when making the request to start captioning a Wordly session. As Wordly generates caption segments, they will be sent to the webhook URL via a POST request.

The body of this POST request will be a single JSON object that contains the following fields.

JSON Field Type Description
sequence number

The sequence number for this caption segment which defines the order that captions should be shown starting with 1. This will always be set to the correct value by the service, and caption segments will be sent to the webhook URL in this order.

Generally, caption segments will also arrive in order; however, be aware that this is not a guarantee due to network conditions outside of Wordly’s control. Therefore, the sequence number can be used to verify the ordering of captions segments as they arrive.

language string A Wordly language code. The caption text will be in this language.
text string The actual caption text formatted as specified per the caption settings that were provided when captioning was requested.
duration number How long the caption should be displayed in milliseconds.

Voice Pack IDs

Sessions can be assigned a voice pack ID. A voice pack is a curated, one-to-one mapping of voices to available Wordly attendee languages. Attendees using the Wordly Web Attend app will hear transcriptions and translations using the voices in the specified pack if they elect to use the speak along feature.

Currently, there is no way to programmatically retrieve a list of available voice packs. However, the following curated voice packs can be used when specifying the voice pack ID for a session.

Voice Pack Name Voice Pack ID
Voice Pack 1 672def43-f760-451c-82f8-c01711ccaa84
Voice Pack 2 97cc30b9-a883-47d5-a2d1-0ad89fc69187

If you do not specify a voice pack when creating a session using the API, then the created session will use the voice pack selected in your Wordly profile. By default, your profile will be set to use the default voice pack, which is currently Voice Pack 1.

You can sample the voice packs for different languages when editing a session or updating your profile in the Wordly Portal.

1.1 - Changelog

Notable changes made to the Wordly API

Version: 1.5.2

Release date: June 23, 2023


  • Minor internal changes with no impact to users.

Version: 1.5.1

Release date: June 8, 2023


  • Added more robust error handling when API key authorization fails.

Version: 1.5.0

Release date: April 21, 2023

What’s New

  • Security and dependency updates.

Version: 1.4.0

Release date: March 17, 2023

What’s New

  • Added a Captions API that will generate live captions from an ongoing Wordly session that will be distributed to a provided webhook URL. See the REST API help page and API reference for more information on captioning.
  • API service version is now visible on the reference page.

Version: 1.3.1

Release date: March 7, 2023


  • Fixed an issue where certain internal server errors would generate the wrong API error response for consumers.

Version: 1.3.0

Release date: February 16, 2023

What’s New

  • Added a voicePackId field to the Sessions API that allows for a voice pack to be optionally specified when creating and updating sessions. See the REST API help page and API reference for more information on voice packs.

    Existing sessions created before this change will automatically use a default voice pack.

Version: 1.2.0

Release date: January 30, 2023

What’s New

  • Added a field to the glossary section object called substitutedPhrases. This field holds a map of replacement rules that can be seen in the Replace tab in the Portal.
  • Check out the API reference for more information.

Version: 1.1.2

Release date: September 23, 2022

What’s New

  • Added support for five new languages listed in the table below. These languages can now be used when creating/updating sessions, glossaries, or streams.
Language Language Code
Czech cs
Indonesian id
Romanian ro
Thai th
Vietnamese vi

Version: 1.1.1

Release date: September 16, 2022


  • (BREAKING) Updated the POST /sessions request so that the language code is now required.
  • Updated the documentation for the streaming API found on the API reference page. The documentation now includes more detailed information.
  • The default limit for both GET /sessions and GET /glossaries is now 10.
  • Updated the error message when a blank search term is provided when sending a GET /glossaries or GET /sessions request.


  • Fixed an issue with the POST /sessions API where an error was returned when a user submitted a scheduledStart value in the request body that included a timezone offset (e.g., 2022-09-22T10:00:00-0700). Now, start times that include a timezone offset should work and no longer return an error.
  • Added constraints to the GET /sessions request so that an error is returned if the page or limit query parameter is set to a value less than 1.

Version: 1.1.0

Release date: September 9, 2022

What’s New

  • Added a new API for streaming media content to Wordly. Check out the API reference for more information.

Version: 1.0.0

Release date: August 15, 2022

What’s New

  • 🎉 Initial release! CRUD operations for sessions and glossaries.

2 - Languages

Languages Supported by Wordly

Wordly supports a number of languages and the codes for each language are listed below.

Speaker Languages

These language codes can be used in all Wordly integrations and APIs:

Language Code Language Name
af Afrikaans
sq Albanian
ar Arabic
bn Bengali
bg Bulgarian
zh-HK Cantonese
zh-CN Chinese (Simplified)
zh-TW Chinese (Traditional)
hr Croatian
cs Czech
da Danish
nl Dutch
en English (US)
en-AU English (AU)
en-GB English (UK)
et Estonian
fi Finnish
fr French (FR)
fr-CA French (CA)
de German
el Greek
gu Gujarati
he Hebrew
hi Hindi
hu Hungarian
id Indonesian
it Italian
ja Japanese
ko Korean
lv Latvian
lt Lithuanian
ms Malay
mt Maltese
no Norwegian
pl Polish
pt Portuguese (PT)
pt-BR Portuguese (BR)
ro Romanian
ru Russian
sr Serbian
sk Slovak
sl Slovenian
es Spanish (ES)
es-MX Spanish (MX)
sv Swedish
tl Tagalog
th Thai
tr Turkish
uk Ukrainian
vi Vietnamese
cy Welsh

Attendee Languages

Along with the languages above, these languages are supported in the Attend iframe and endpoints:

Language Code Language Name
ga Irish
fa Persian
pa Punjabi
sw Swahili
ta Tamil
ur Urdu

3 - iFrame Integration

Receiving Translations in an iFrame

Often, the easiest way to integrate Wordly translations into a platform or web application is to embed the ‘attend’ client in an HTML iFrame.

iFrame Embed

The basic HTML code for embedding Wordly translations in an iframe uses the standard HTML iframe tag:

    <iframe src="url" />

You place this in your application wherever you would like Wordly translations to appear. Typically you want to set width and height so the iframe will fill the space you leave for it. This can be done directly in the iframe tag, or via a class attribute. For example:

    <iframe src="url" width="100%" height="300px" />

Source URL

The url to use as the source is crafted from the Wordly session that you want to show your users. The basic format is:<session id>

for example, something like:

where ‘ABCD-1234’ would be replaced with a Wordly session ID obtained from the Portal at

Source URL parameters

The url takes a number of optional arguments that can be used with sessions that require a passcode and to change the way the iframe content is displayed:

  • key: the session passcode if one is required to attend. Open sessions do not require a passcode.
  • lang: the initial language code of the translations for this user. This is not often used. The translation languge will default to English or whatever the user has chosen in the past. See languages for the list of language codes.
  • fgcolor: an HTML color for the text in the iframe. This value can be any valid HTML color name or a custom hex RGBA color. The default is white.
  • bgcolor: an HTML color for the background of the iframe. This value can be any valid HTML color name or a custom hex RGBA color. The default is black.
  • fgsize: an HTML size value for the text in the iframe. This value can be any valid HTML text size, including units. This defaults to the container text size and is not often used.
  • tags: a boolean value that can be set to “false” to prevent the display of speaker names in the iframe. This defaults to “true”.
  • speakerLanguage: a boolean value that can be set to “false” to hide the display of the language the speaker is using. This defaults to “true”.
  • enableTTS: a boolean value that can be set to “true” to enable text-to-speech support. When this value is ‘true,’ new buttons are added to the bottom bar allowing the user to select a voice for the text to be spoken out loud, and a mute/unmute button. This defaults to “false“.
  • finalOnly: a boolean value that can be set to “true” to change the default value for the “Show only complete phrases” user setting. When this value is “true,” only completed translations will be shown to the user and partial translations will be suppressed.
  • showScrollbar: a boolean value that can be set to “false” to prevent the scrollbar from appearing in the frame. When this value is set to “false,” users cannot scroll back to read earlier parts of a transcript.
  • hide: a list of Wordly language codes to hide from the user. This parameter is a string of codes separated by commas. The specified languages will be removed from the various menus presented to the user. For example: ?hide=en,es,fr will remove English, Spanish, and French from the language menus. See languages for the list of language codes.
  • show: a list of Wordly language codes to show to the user. This parameter is a string of codes separated by commas. The specified languages will be the only ones included in the various menus presented to the user. For example: ?show=en,es,fr will reduce all language menus to just English, Spanish, and French. See languages for the list of language codes.


A url to display session ‘DCBA-4321’ in Spanish with big, green text would be:

and this emebedded in an iframe in your HTML might look like:

    <iframe src="" width="100%" />

A url to display session “DCBA-4321” with TTS enabled:

and this emebedded in an iframe in your HTML might look like:

    <iframe src="" width="100%" />

4 - RTMP Streaming

Streaming Content to Wordly in Real Time

A common way for users and developers to send speech to Wordly for translation is via RTMP streaming, This can be useful when using Wordly to translate a conference session or webinar, or when embedding Wordly in an iframe.

RTMP Streaming

The streaming connection to wordly is via RTMP which requires two things:

  • A streaming URL
  • A stream key

Streaming URL

The Wordly streaming URL is:


This will open an encrypted stream to the Wordly RTMP server.

There is an optional, unencrypted RTMP streaming link. However, we strongly encourage RTMPS as it is more secure. If you cannot use the RTMPS link for some reason, the unencrypted streaming URL is:


Stream Key

The stream key tells Wordly the session you are streaming to. This will be the same session as using in the iframe embed (if you are using an iframe). The stream key must also include the passcode to enable access to that session. For example:


Where AABCD-1234 is the Wordly session ID and 987654 is the passcode for the session.

Stream keys are generated automatically when a session is scheduled in the Wordly Portal, and you can find them and the streaming URLs in the session Streaming Shortcuts at

Portal Streaming Shortcuts

Adding a delay

Sometimes you may need to delay the stream you are sending to Wordly in order to match the delay of the video player in your integration. You add a delay as a parameter attached to the stream key. The delay is in milliseconds to allow fine tuning if needed.

For example you can add a delay of 15 seconds to the stream key above like this:


or if you prefer obscurity you can attach it to the end of the stream key like this:


Adding a language

When you stream to a Wordly session, Wordly will expect speech in the stream to be in the language specified in the session. If the content is actually in a different language, you can override it in the stream key as an additional parameter. See languages for the list of language codes.

For example, to tell Wordly the content of the stream is in French, you can use a stream key like this:


or it can be appended to the stream key like this:


You can also combine the language and delay parameters:




The language parameter is not often used. The current streaming language can be changed while streaming is active using the streaming controls in the Portal.

Streaming controls

You can open the live streaming controls in the Portal by clicking on the gear icon next to the session that you are streaming to:

Portal Streaming Controls

With these controls you can change the language Wordly is expecting the stream speakers to be using. To change the language, pick the new language in the drop-down selector and click the red “Change” button:

Change Streaming Language

Each time a new language is used, a blue quick-change button appears. The streaming language can be changed back to a previous language by clicking one of these buttons.

Finally, when streaming is complete, the “End” button can be used to end the Wordly session.