> For the complete documentation index, see [llms.txt](https://docs.openreview.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openreview.net/~/changes/kVYMUwjISEF9x7H1lfSE/getting-started/using-the-api/notes/getting-all-metareviews.md).

# Getting all MetaReviews

To get all meta-reviews for a venue, you can do the following: 

1. Get all submissions for your venue. You can do this by passing your venue's submission invitation into get\_all\_notes*.* You should also pass in details = "directReplies" to obtain any notes that reply to each submission. 

```python
submissions = client.get_all_notes(
    invitation="Your/Venue/ID/-/Submission",
    details='directReplies'
)
```

2\. For each submission, add any replies with the Meta-Review invitation to a list of meta-reviews. 

```python
metareviews = [] 
for submission in submissions:
    metareviews = metareviews + [reply for reply in submission.details["directReplies"] if reply["invitation"].endswith("Meta_Review")]
```

3\. The  metareviews list now contains all of the meta-reviews for your venue.


---

# 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.openreview.net/~/changes/kVYMUwjISEF9x7H1lfSE/getting-started/using-the-api/notes/getting-all-metareviews.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.