Developer API

• 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!

Changelog

Click here to view the changelog.

Getting a Developer API Key

A developer API key must be included as a value in the header for all requests.

Prerequisites

• An Wordly account with available minutes.
• Your Wordly account must be added to an allow list by Wordly Support.

Once your account has been added to the allow list, you can create a non-expiring API key in the portal:

1. Go to your user profile page in the Wordly portal.
2. Click the + button in the API Key row to create a new API key. 

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

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 (Unauthorized) response from the server.

Versioning

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

Wordly includes 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

You can also 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 don't provide the x-wordly-api-version header in your requests, then Wordly will assume the latest API version. For this reason, we strongly recommend that you include this header with every request.

Errors

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.

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.

Voice Pack IDs

Sessions can be assigned a voice pack ID, which 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 text to speech 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.

If you don't specify a voice pack when creating a session using the API, then the created session uses the voice pack selected in your Wordly profile. By default, your profile will be set to use the default voice pack, which is currently the Feminine Voice.

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