My Speaking Score's API

Modified on Wed, 4 Jun at 6:23 AM

? My Speaking Score API – Summary


Read more: https://www.myspeakingscore.com/my-speaking-score-api 


Purpose:
The API allows developers or platforms to integrate automated TOEFL Speaking scoring into their own tools using SpeechRater™ and e-rater® technologies. It provides score predictions for spoken responses and written essays.


? Core Capabilities

1. Speaking Score (SpeechRater)

  • Accepts an audio file + TOEFL Speaking prompt.

  • Returns a 4-point score and sub-scores across key dimensions:

    • Pronunciation & fluency

    • Grammar

    • Vocabulary

    • Coherence

    • Speaking rate

    • Sustained speech

  • Score is typically available within seconds.

2. Writing Score (e-rater)

  • Accepts a written TOEFL essay.

  • Returns a 30-point scaled score with sub-scores:

    • Grammar

    • Usage

    • Mechanics

    • Style

    • Organization

3. VoX AI (Proprietary Prediction)

  • For platforms that don’t want to use ETS APIs directly.

  • Predicts TOEFL Speaking score using My Speaking Score’s proprietary AI.

  • Returns a predicted SpeechRater score with a confidence interval.


? Features

  • Real-time feedback or batch processing.

  • Confidence intervals (e.g., [3.2, 3.8]) on AI-predicted scores.

  • CEFR & IELTS mappings available (optional).

  • Available as REST API with secure endpoints.

  • JSON request/response format.


? Authentication & Access

  • Requires API key (managed by My Speaking Score team).

  • Tiered access based on plan (Basic, Elite, Infinite, etc.).

  • Custom integrations available for partners and institutions.


? Use Cases

  • EdTech platforms

  • Online tutoring companies

  • TOEFL prep apps

  • Institutional assessment tools

  • Voice-enabled language learning experiences


Please contact us for more information.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article