> For the complete documentation index, see [llms.txt](https://speaking-test-docs.speechace.com/speechace-speaking-test/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://speaking-test-docs.speechace.com/speechace-speaking-test/speechace-workspaces-create-manage-and-share-speaking-assessments/embedding-assessments-in-other-apps-and-websites/oembed-integration-for-speechace-speaking-test/receiving-test-results-on-specified-callback/results-callback-to-3rd-party-application-backend.md).

# Results callback to 3rd party application backend

Test completion callbacks to 3rd party app backends are useful in storing the user's speaking test results in the 3rd party app's database. Recall that in the last section, we discussed passing app\_score\_submission\_url parameter as a means to get results for the test as shown below:\
\
app\_score\_submission\_url=**<https://e-learning-website.com/submit\\_speechace\\_scores?courseid=91\\&testid=25\\&userid=1234a>**

Once the test is complete, the app\_score\_submission\_url will receive a post call with the following parameters:\
{\
&#x20;   "version": "1.0", \
&#x20;   "key": 'IlYq1zwpMrCaUAW3', \
&#x20;   "courseId": 1234, \
&#x20;   "quizId": 456,\
&#x20;   "userId": 1234a, \
&#x20;   "score": { \
&#x20;        "overall" : 4.0, \
&#x20;        "pronunciation": 7.6, \
&#x20;        "fluency": 6.5, \
&#x20;        "vocab": 6.6, \
&#x20;        "grammar": 5.5 }, \
&#x20;        "reportUrl": <https://speak.speechace.co/placement/report/a698bd97924e08e68ef1db96a8\\>
}

Note that we pass back the key as obtained in the URL from the shared assessment panel so you may verify that the caller is indeed us. You must check for this key otherwise anyone can call your callback URL to submit grades.

{% hint style="info" %}
Note that the reportURL can be used to obtained the full detailed report for the test attempt in JSON format as presented in the next section.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://speaking-test-docs.speechace.com/speechace-speaking-test/speechace-workspaces-create-manage-and-share-speaking-assessments/embedding-assessments-in-other-apps-and-websites/oembed-integration-for-speechace-speaking-test/receiving-test-results-on-specified-callback/results-callback-to-3rd-party-application-backend.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.