> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/uof/support-and-history/archived/deprecated-uof-endpoints/elements/period-scores.md).
# Period scores
The period scores element and its sub-element period score are present in the summary end point and in the timeline end point and they are extremely significant as they report the resulting for the match.
This is a useful information for those matches which are not covered live.
Here follows an example of period scores.
\\
\\
\\
\\
\\
\
Each period score element provides info about the outcome of a part of the match which can be different according to the sport. The example provides the resulting of a soccer match with 2 regular half times and over time and penalties with related scores.
Table below provides info related to the attributes in the period\_score element.
| Attribute | meaning | possible values | type | Note |
| ------------------- | ------------------------------------------------------- | ----------------------------------------------------------- | ------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| home\_score | score of the home team at a certain period of the match | number | numeric |
|
| away\_score | score of the away team at a certain period of the match | number | numeric |
|
| match\_status\_code | code of the match status | 6,7,40,50 | numeric | In the period\_score the match\_status\_code can assume just values of "overtime", "penalties" and in all other cases it will be "regualar\_period" |
| type | description of the period | "regular\_period"
"overtime"
"penalties"
| string |
|
| number | number of the period | number | numeric |
|
---
# 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://docs.sportradar.com/uof/support-and-history/archived/deprecated-uof-endpoints/elements/period-scores.md?ask=&goal=
```
`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.