> 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/datacore/sports-apis/baseball/datacore-api-v1/introduction/bulk-post-and-put-requests.md).

# Bulk POST & PUT requests

When performing bulk POST or PUT requests, it is essential to consider the size of the payload to ensure optimal performance and avoid potential issues.

**Payload Size for Complex Structures** For complex structures, such as Matches, the recommended number of rows to include in the payload is 70. This guideline helps maintain efficiency and reliability during data processing.

**Payload Size for Other Endpoints** For other endpoints, it may be possible to handle larger payloads. However, it is crucial to analyze the performance and determine the appropriate size for your specific use case. Conduct thorough testing and monitoring to identify the optimal payload size that your system can handle without compromising performance.


---

# 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/datacore/sports-apis/baseball/datacore-api-v1/introduction/bulk-post-and-put-requests.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.