---
title: "GET /posts/{ids}"
method: GET
path: "/posts/{ids}"
---

# GET /posts/{ids}

`GET /posts/{ids}`

Fetches a set of posts by ids.
 
This method is meant for grabbing an object when unsure whether an id identifies a question or an answer. This is most common with user entered data.
 
{ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for post_id, answer_id, or question_id on post, answer, and question objects respectively.
 
The sorts accepted by this method operate on the follow fields of the post object:
 - activity - last_activity_date
 - creation - creation_date
 - votes - score
  activity is the default sort.
 
 It is possible to create moderately complex queries using sort, min, max, fromdate, and todate.

 
This method returns a list of posts.

## Path parameters

- `ids` string, required

## Query parameters

- `order` 'desc' | 'asc'
- `max` string
- `min` string
- `sort` 'activity' | 'creation' | 'votes'
- `fromdate` integer
- `todate` integer
- `pagesize` integer
- `page` integer
- `filter` string
- `callback` string
- `site` string, required

## Response `200`

OK

## Other responses

- `400` — bad_parameter – 400 An invalid parameter was passed, this includes even "high level" parameters like key or site.
- `401` — access_token_required – 401 A method that requires an access token (obtained via authentication) was called without one.
- `402` — invalid_access_token – 402 An invalid access token was passed to a method.
- `403` — access_denied – 403 A method which requires certain permissions was called with an access token that lacks those permissions.
- `404` — no_method – 404 An attempt was made to call a method that does not exist. Note, calling methods that expect numeric ids (like /users/{ids}) with non-numeric ids can also result in this error.
- `405` — key_required – 405 A method was called in a manner that requires an application key (generally, with an access token), but no key was passed.
- `406` — access_token_compromised – 406 An access token is no longer believed to be secure, normally because it was used on a non-HTTPS call. The access token will be invalidated if this error is returned.
- `500` — internal_error – 500 An unexpected error occurred in the API. It has been logged, and Stack Exchange developers have been notified. You should report these errors on Stack Apps if you want to be notified when they're fixed.
- `502` — throttle_violation – 502 An application has violated part of the rate limiting contract, so the request was terminated.
- `503` — temporarily_unavailable – 503 Some or all of the API is unavailable. Applications should backoff on requests to the method invoked.

---

[API](https://skmtc.net/apis-guru/apis/stackexchange.md) · [All operations](https://skmtc.net/apis-guru/apis/stackexchange/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/apis-guru/stackexchange/versions/c8370badded7/schema)