Skip to content
Changelog

Report a bug

Stack Exchange integration: operations for AI agents

Stack Exchange connects to Type.com as an integration. This page lists the 124 operations documented for Claude and Codex in Type.com: 121 read, 3 write.

About Stack Exchange

Stack Exchange is a network of Q&A communities where users ask questions, share knowledge, and collaborate on topics like coding, math, and more

Categories: Developer Tools & IT

How to connect Stack Exchange to Type.com

Access
Organization connection: one shared account for the workspace.

To add the connection, follow the steps in Space connections.

Documented operations

124 operations. Your connection's permissions determine which operations are available. API references describe the vendor surface; they do not expand your connection's credentials or access.

124 operations listed.

Access tokens

  • Read

    GET /access-tokens/{accessTokens}

    Reads the properties for a set of access tokens. {accessTokens} can contain up to 20 access tokens. These are obtained by authenticating a user using OAuth 2.0. This method returns a list of accesstokens.

  • Read

    GET /access-tokens/{accessTokens}/invalidate

    Immediately expires the access tokens passed. This method is meant to allow an application to discard any active access tokens it no longer needs. {accessTokens} can contain up to 20 access tokens. These are obtained by authenticating a user using OAuth 2.0.

Answers

  • Read

    GET /answers

    Returns all the undeleted answers in the system. The sorts accepted by this method operate on the follow fields of the answer object: - activity - lastactivitydate - creation - creationdate - votes - score activity is the default sort.

  • Read

    GET /answers/{ids}

    Gets the set of answers identified by ids. This is meant for batch fetcing of questions. A useful trick to poll for updates is to sort by activity, with a minimum date of the last time you polled.

  • Read

    GET /answers/{ids}/comments

    Gets the comments on a set of answers. If you know that you have an answer id and need the comments, use this method. If you know you have a question id, use /questions/{id}/comments. If you are unsure, use /posts/{id}/comments.

Apps

  • Read

    GET /apps/{accessTokens}/de-authenticate

    Passing valid accesstokens to this method causes the application that created them to be de-authorized by the user associated with each accesstoken. This will remove the application from their apps tab, and cause all other existing accesstokens to be destroyed.

Badges

  • Read

    GET /badges

    Returns all the badges in the system. Badge sorts are a tad complicated. For the purposes of sorting (and min/max) tagbased is considered to be greater than named.

  • Read

    GET /badges/name

    Gets all explicitly named badges in the system. A named badged stands in opposition to a tag-based badge. These are referred to as general badges on the sites themselves. For the rank sort, bronze is greater than silver which is greater than gold.

  • Read

    GET /badges/recipients

    Returns recently awarded badges in the system. As these badges have been awarded, they will have the badge.user property set. This method returns a list of badges.

  • Read

    GET /badges/tags

    Returns the badges that are awarded for participation in specific tags. For the rank sort, bronze is greater than silver which is greater than gold. Along with sort=rank, set max=gold for just gold badges, max=silver&min=silver for just silver, and min=bronze for just bronze.

  • Read

    GET /badges/{ids}

    Gets the badges identified in id. Note that badge ids are not constant across sites, and thus should be looked up via the /badges method. A badge id on a single site is, however, guaranteed to be stable. Badge sorts are a tad complicated.

  • Read

    GET /badges/{ids}/recipients

    Returns recently awarded badges in the system, constrained to a certain set of badges. As these badges have been awarded, they will have the badge.user property set.

Comments

  • Read

    GET /comments

    Gets all the comments on the site. If you're filtering for interesting comments (by score, creation date, etc.) make use of the sort paramter with appropriate min and max values.

  • Read

    GET /comments/{ids}

    Gets the comments identified in id. This method is most useful if you have a cache of comment ids obtained through other means (such as /questions/{id}/comments) but suspect the data may be stale.

  • Write

    POST /comments/{id}/delete

    Deletes a comment. Use an accesstoken with writeaccess to delete a comment. In practice, this method will never return an object.

  • Write

    POST /comments/{id}/edit

    Edit an existing comment. Use an accesstoken with writeaccess to edit an existing comment. This method return the created comment.

Errors

  • Read

    GET /errors

    Returns the various error codes that can be produced by the API. This method is provided for discovery, documentation, and testing purposes, it is not expected many applications will consume it during normal operation.

  • Read

    GET /errors/{id}

    This method allows you to generate an error. This method is only intended for use when testing an application or library. Unlike other methods in the API, its contract is not frozen, and new error codes may be added at any time.

Events

  • Read

    GET /events

    Returns a stream of events that have occurred on the site. The API considers the following "events": - posting a question - posting an answer - posting a comment - editing a post - creating a user Events are only accessible for 15 minutes after they occurred, and by default only…

Filters

  • Read

    GET /filters/create

    Creates a new filter given a list of includes, excludes, a base filter, and whether or not this filter should be "unsafe". Filter "safety" is defined as follows.

  • Read

    GET /filters/{filters}

    Returns the fields included by the given filters, and the "safeness" of those filters. It is not expected that this method will be consumed by many applications at runtime, it is provided to aid in debugging. {filters} can contain up to 20 semicolon delimited filters.

Inbox

  • Read

    GET /inbox

    Returns a user's inbox. This method requires an accesstoken, with a scope containing "readinbox". This method returns a list of inbox items.

  • Read

    GET /inbox/unread

    Returns the unread items in a user's inbox. This method requires an accesstoken, with a scope containing "readinbox". This method returns a list of inbox items.

Info

  • Read

    GET /info

    Returns a collection of statistics about the site. Data to facilitate per-site customization, discover related sites, and aggregate statistics is all returned by this method. This data is cached very aggressively, by design. Query sparingly, ideally no more than once an hour.

Me

  • Read

    GET /me

    Returns the user associated with the passed accesstoken. This method returns a user.

  • Read

    GET /me/answers

    Returns the answers owned by the user associated with the given accesstoken. This method returns a list of answers.

  • Read

    GET /me/associated

    Returns all of a user's associated accounts, given an accesstoken for them. This method returns a list of network users.

  • Read

    GET /me/badges

    Returns the badges earned by the user associated with the given accesstoken. This method returns a list of badges.

  • Read

    GET /me/comments

    Returns the comments owned by the user associated with the given accesstoken. This method returns a list of comments.

  • Read

    GET /me/comments/{toId}

    Returns the comments owned by the user associated with the given accesstoken that are in reply to the user identified by {toId}. This method returns a list of comments.

  • Read

    GET /me/favorites

    Returns the questions favorites by the user associated with the given accesstoken. This method returns a list of questions.

  • Read

    GET /me/inbox

    Returns the user identified by accesstoken's inbox. This method requires an accesstoken, with a scope containing "readinbox". This method returns a list of inbox items.

  • Read

    GET /me/inbox/unread

    Returns the unread items in the user identified by accesstoken's inbox. This method requires an accesstoken, with a scope containing "readinbox". This method returns a list of inbox items.

  • Read

    GET /me/mentioned

    Returns the comments mentioning the user associated with the given accesstoken. This method returns a list of comments.

  • Read

    GET /me/merges

    Returns a record of merges that have occurred involving a user identified by an accesstoken. This method allows you to take now invalid account ids and find what account they've become, or take currently valid account ids and find which ids were equivalent in the past.

  • Read

    GET /me/notifications

    Returns a user's notifications, given an accesstoken. This method requires an accesstoken, with a scope containing "readinbox". This method returns a list of notifications.

  • Read

    GET /me/notifications/unread

    Returns a user's unread notifications, given an accesstoken. This method requires an accesstoken, with a scope containing "readinbox". This method returns a list of notifications.

  • Read

    GET /me/privileges

    Returns the privileges the user identified by accesstoken has. This method returns a list of privileges.

  • Read

    GET /me/questions

    Returns the questions owned by the user associated with the given accesstoken. This method returns a list of questions.

  • Read

    GET /me/questions/featured

    Returns the questions that have active bounties offered by the user associated with the given accesstoken. This method returns a list of questions.

  • Read

    GET /me/questions/no-answers

    Returns the questions owned by the user associated with the given accesstoken that have no answers. This method returns a list of questions.

  • Read

    GET /me/questions/unaccepted

    Returns the questions owned by the user associated with the given accesstoken that have no accepted answer. This method returns a list of questions.

  • Read

    GET /me/questions/unanswered

    Returns the questions owned by the user associated with the given accesstoken that are not considered answered. This method returns a list of questions.

  • Read

    GET /me/reputation

    Returns the reputation changed for the user associated with the given accesstoken. This method returns a list of reputation changes.

  • Read

    GET /me/reputation-history

    Returns user's public reputation history. This method returns a list of reputationhistory.

  • Read

    GET /me/reputation-history/full

    Returns user's full reputation history, including private events. This method requires an accesstoken, with a scope containing "privateinfo". This method returns a list of reputationhistory.

  • Read

    GET /me/suggested-edits

    Returns the suggested edits the user identified by accesstoken has submitted. This method returns a list of suggested-edits.

  • Read

    GET /me/tags

    Returns the tags the user identified by the accesstoken passed is active in. This method returns a list of tags.

  • Read

    GET /me/tags/{tags}/top-answers

    Returns the top 30 answers the user associated with the given accesstoken has posted in response to questions with the given tags. This method returns a list of answers.

  • Read

    GET /me/tags/{tags}/top-questions

    Returns the top 30 questions the user associated with the given accesstoken has posted in response to questions with the given tags. This method returns a list of questions.

  • Read

    GET /me/timeline

    Returns a subset of the actions the user identified by the passed accesstoken has taken on the site. This method returns a list of user timeline objects.

  • Read

    GET /me/top-answer-tags

    Returns the user identified by accesstoken's top 30 tags by answer score. This method returns a list of top tag objects.

  • Read

    GET /me/top-question-tags

    Returns the user identified by accesstoken's top 30 tags by question score. This method returns a list of top tag objects.

  • Read

    GET /me/write-permissions

    Returns the write permissions a user has via the api, given an access token. The Stack Exchange API gives users the ability to create, edit, and delete certain types.

Notifications

  • Read

    GET /notifications

    Returns a user's notifications. This method requires an accesstoken, with a scope containing "readinbox". This method returns a list of notifications.

  • Read

    GET /notifications/unread

    Returns a user's unread notifications. This method requires an accesstoken, with a scope containing "readinbox". This method returns a list of notifications.

Posts

  • Read

    GET /posts

    Fetches all posts (questions and answers) on the site. In many ways this method is the union of /questions and /answers, returning both sets of data albeit only the common fields.

  • Read

    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.

  • Read

    GET /posts/{ids}/comments

    Gets the comments on the posts identified in ids, regardless of the type of the posts. This method is meant for cases when you are unsure of the type of the post id provided. Generally, this would be due to obtaining the post id directly from a user.

  • Read

    GET /posts/{ids}/revisions

    Returns edit revisions for the posts identified in ids. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for postid, answerid, or questionid on post, answer, and question objects respectively. This method returns a list of revisions.

  • Read

    GET /posts/{ids}/suggested-edits

    Returns suggsted edits on the posts identified in ids. - creation - creationdate - approval - approvaldate - rejection - rejectiondate creation is the default sort.

  • Write

    POST /posts/{id}/comments/add

    Create a new comment. Use an accesstoken with writeaccess to create a new comment on a post. This method returns the created comment.

Privileges

  • Read

    GET /privileges

    Returns the earnable privileges on a site. Privileges define abilities a user can earn (via reputation) on any Stack Exchange site. While fairly stable, over time they do change. New ones are introduced with new features, and the reputation requirements change as a site matures.

Questions

  • Read

    GET /questions

    Gets all the questions on the site. This method allows you make fairly flexible queries across the entire corpus of questions on a site.

  • Read

    GET /questions/featured

    Returns all the questions with active bounties in the system. The sorts accepted by this method operate on the follow fields of the question object: - activity - lastactivitydate - creation - creationdate - votes - score activity is the default sort.

  • Read

    GET /questions/no-answers

    Returns questions which have received no answers. Compare with /questions/unanswered which mearly returns questions that the sites consider insufficiently well answered. This method corresponds roughly with the this site tab.

  • Read

    GET /questions/unanswered

    Returns questions the site considers to be unanswered. Note that just because a question has an answer, that does not mean it is considered answered. While the rules are subject to change, at this time a question must have at least one upvoted answer to be considered answered.

  • Read

    GET /questions/{ids}

    Returns the questions identified in {ids}. This is most useful for fetching fresh data when maintaining a cache of question ids, or polling for changes. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for questionid on question objects.

  • Read

    GET /questions/{ids}/answers

    Gets the answers to a set of questions identified in id. This method is most useful if you have a set of interesting questions, and you wish to obtain all of their answers at once or if you are polling for new or updates answers (in conjunction with sort=activity).

  • Read

    GET /questions/{ids}/comments

    Gets the comments on a question. If you know that you have an question id and need the comments, use this method. If you know you have a answer id, use /answers/{ids}/comments. If you are unsure, use /posts/{ids}/comments.

  • Read

    GET /questions/{ids}/linked

    Gets questions which link to those questions identified in {ids}. This method only considers questions that are linked within a site, and will never return questions from another Stack Exchange site.

  • Read

    GET /questions/{ids}/related

    Returns questions that the site considers related to those identified in {ids}. The algorithm for determining if questions are related is not documented, and subject to change at any time.

  • Read

    GET /questions/{ids}/timeline

    Returns a subset of the events that have happened to the questions identified in id. This provides data similar to that found on a question's timeline page. Voting data is scrubbed to deter inferencing of voter identity.

Revisions

  • Read

    GET /revisions/{ids}

    Returns edit revisions identified by ids in {ids}. {ids} can contain up to 20 semicolon delimited ids, to find ids programatically look for revisionguid on revision objects. Note that unlike most other id types in the API, revisionguid is a string.

Search

  • Read

    GET /search

    Searches a site for any questions which fit the given criteria. This method is intentionally quite limited. For more general searching, you should use a proper internet search engine restricted to the domain of the site in question.

  • Read

    GET /search/advanced

    Searches a site for any questions which fit the given criteria. Search criteria are expressed using the following parameters: - q - a free form text parameter, will match all question properties based on an undocumented algorithm.

Similar

  • Read

    GET /similar

    Returns questions which are similar to a hypothetical one based on a title and tag combination. This method is roughly equivalent to a site's related questions suggestion on the ask page.

Sites

  • Read

    GET /sites

    Returns all sites in the network. This method allows for discovery of new sites, and changes to existing ones. Be aware that unlike normal API methods, this method should be fetched very infrequently, it is very unusual for these values to change more than once on any given day.

Suggested edits

  • Read

    GET /suggested-edits

    Returns all the suggested edits in the systems. This method returns a list of suggested-edits.

  • Read

    GET /suggested-edits/{ids}

    Returns suggested edits identified in ids. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for suggestededitid on suggestededit objects.

Tags

  • Read

    GET /tags

    Returns the tags found on a site. The inname parameter lets a consumer filter down to tags that contain a certain substring. For example, inname=own would return both "download" and "owner" amongst others. This method returns a list of tags.

  • Read

    GET /tags/moderator-only

    Returns the tags found on a site that only moderators can use. The inname parameter lets a consumer filter down to tags that contain a certain substring. For example, inname=own would return both "download" and "owner" amongst others. This method returns a list of tags.

  • Read

    GET /tags/required

    Returns the tags found on a site that fulfill required tag constraints on questions. The inname parameter lets a consumer filter down to tags that contain a certain substring. For example, inname=own would return both "download" and "owner" amongst others.

  • Read

    GET /tags/synonyms

    Returns all tag synonyms found a site. When searching for synonyms of specific tags, it is better to use /tags/{tags}/synonyms over this method.

  • Read

    GET /tags/{tags}/faq

    Returns the frequently asked questions for the given set of tags in {tags}. For a question to be returned, it must have all the tags in {tags} and be considered "frequently asked".

  • Read

    GET /tags/{tags}/info

    Returns tag objects representing the tags in {tags} found on the site. This method diverges from the standard naming patterns to avoid to conflicting with existing methods, due to the free form nature of tag names. This method returns a list of tags.

  • Read

    GET /tags/{tags}/related

    Returns the tags that are most related to those in {tags}. Including multiple tags in {tags} is equivalent to asking for "tags related to tag 1 and tag 2" not "tags related to tag 1 or tag 2".

  • Read

    GET /tags/{tags}/synonyms

    Gets all the synonyms that point to the tags identified in {tags}. If you're looking to discover all the tag synonyms on a site, use the /tags/synonyms methods instead of call this method on all tags. {tags} can contain up to 20 individual tags per request.

  • Read

    GET /tags/{tags}/wikis

    Returns the wikis that go with the given set of tags in {tags}. Be aware that not all tags have wikis. {tags} can contain up to 20 individual tags per request. This method returns a list of tag wikis.

  • Read

    GET /tags/{tag}/top-answerers/{period}

    Returns the top 30 answerers active in a single tag, of either all-time or the last 30 days. This is a view onto the data presented on the tag info page on the sites. This method returns a list of tag score objects.

  • Read

    GET /tags/{tag}/top-askers/{period}

    Returns the top 30 askers active in a single tag, of either all-time or the last 30 days. This is a view onto the data presented on the tag info page on the sites. This method returns a list of tag score objects.

Users

  • Read

    GET /users

    Returns all users on a site. This method returns a list of users.

  • Read

    GET /users/moderators

    Gets those users on a site who can exercise moderation powers. Note, employees of Stack Exchange Inc. will be returned if they have been granted moderation powers on a site even if they have never been appointed or elected explicitly.

  • Read

    GET /users/moderators/elected

    Returns those users on a site who both have moderator powers, and were actually elected. This method excludes Stack Exchange Inc. employees, unless they were actually elected moderators on a site (which can only have happened prior to their employment).

  • Read

    GET /users/{ids}

    Gets the users identified in ids in {ids}. Typically this method will be called to fetch user profiles when you have obtained user ids from some other source, such as /questions.

  • Read

    GET /users/{ids}/answers

    Returns the answers the users in {ids} have posted. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for userid on user or shallowuser objects.

  • Read

    GET /users/{ids}/associated

    Returns all of a user's associated accounts, given their accountids in {ids}. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for accountid on user objects. This method returns a list of networkusers.

  • Read

    GET /users/{ids}/badges

    Get the badges the users in {ids} have earned. Badge sorts are a tad complicated. For the purposes of sorting (and min/max) tagbased is considered to be greater than named.

  • Read

    GET /users/{ids}/comments

    Get the comments posted by users in {ids}. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for userid on user or shallowuser objects.

  • Read

    GET /users/{ids}/comments/{toid}

    Get the comments that the users in {ids} have posted in reply to the single user identified in {toid}. This method is useful for extracting conversations, especially over time or across multiple posts.

  • Read

    GET /users/{ids}/favorites

    Get the questions that users in {ids} have favorited. This method is effectively a view onto a user's favorites tab. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for userid on user or shallowuser objects.

  • Read

    GET /users/{ids}/mentioned

    Gets all the comments that the users in {ids} were mentioned in. Note, to count as a mention the comment must be considered to be "in reply to" a user. Most importantly, this means that a comment can only be in reply to a single user.

  • Read

    GET /users/{ids}/merges

    Returns a record of merges that have occurred involving the passed account ids. This method allows you to take now invalid account ids and find what account they've become, or take currently valid account ids and find which ids were equivalent in the past.

  • Read

    GET /users/{ids}/questions

    Gets the questions asked by the users in {ids}. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for userid on user or shallowuser objects.

  • Read

    GET /users/{ids}/questions/featured

    Gets the questions on which the users in {ids} have active bounties. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for userid on user or shallowuser objects.

  • Read

    GET /users/{ids}/questions/no-answers

    Gets the questions asked by the users in {ids} which have no answers. Questions returns by this method actually have zero undeleted answers.

  • Read

    GET /users/{ids}/questions/unaccepted

    Gets the questions asked by the users in {ids} which have at least one answer, but no accepted answer. Questions returned by this method have answers, but the owner has not opted to accept any of them.

  • Read

    GET /users/{ids}/questions/unanswered

    Gets the questions asked by the users in {ids} which the site consideres unanswered, while still having at least one answer posted. These rules are subject to change, but currently any question without at least one upvoted or accepted answer is considered unanswered.

  • Read

    GET /users/{ids}/reputation

    Gets a subset of the reputation changes for users in {ids}. Reputation changes are intentionally scrubbed of some data to make it difficult to correlate votes on particular posts with user reputation changes.

  • Read

    GET /users/{ids}/reputation-history

    Returns users' public reputation history. This method returns a list of reputationhistory.

  • Read

    GET /users/{ids}/suggested-edits

    Returns the suggested edits a users in {ids} have submitted. {ids} can contain up to 100 semicolon delimited ids, to find ids programatically look for userid on user or shallowuser objects.

  • Read

    GET /users/{ids}/tags

    Returns the tags the users identified in {ids} have been active in. This route corresponds roughly to user's stats tab, but does not include tag scores. A subset of tag scores are available (on a single user basis) in /users/{id}/top-answer-tags and /users/{id}/top-question-tags.

  • Read

    GET /users/{ids}/timeline

    Returns a subset of the actions the users in {ids} have taken on the site. This method returns users' posts, edits, and earned badges in the order they were accomplished. It is possible to filter to just a window of activity using the fromdate and todate parameters.

  • Read

    GET /users/{id}/inbox

    Returns a user's inbox. This method requires an accesstoken, with a scope containing "readinbox". This method is effectively an alias for /inbox.

  • Read

    GET /users/{id}/inbox/unread

    Returns the unread items in a user's inbox. This method requires an accesstoken, with a scope containing "readinbox". This method is effectively an alias for /inbox/unread.

  • Read

    GET /users/{id}/notifications

    Returns a user's notifications. This method requires an accesstoken, with a scope containing "readinbox". This method returns a list of notifications.

  • Read

    GET /users/{id}/notifications/unread

    Returns a user's unread notifications. This method requires an accesstoken, with a scope containing "readinbox". This method returns a list of notifications.

  • Read

    GET /users/{id}/privileges

    Returns the privileges a user has. Applications are encouraged to calculate privileges themselves, without repeated queries to this method. A simple check against the results returned by /privileges and user.usertype would be sufficient.

  • Read

    GET /users/{id}/reputation-history/full

    Returns a user's full reputation history, including private events. This method requires an accesstoken, with a scope containing "privateinfo". This method returns a list of reputationhistory.

  • Read

    GET /users/{id}/tags/{tags}/top-answers

    Returns the top 30 answers a user has posted in response to questions with the given tags. {id} can contain a single id, to find it programatically look for userid on user or shallowuser objects. {tags} is limited to 5 tags, passing more will result in an error.

  • Read

    GET /users/{id}/tags/{tags}/top-questions

    Returns the top 30 questions a user has asked with the given tags. {id} can contain a single id, to find it programatically look for userid on user or shallowuser objects. {tags} is limited to 5 tags, passing more will result in an error.

  • Read

    GET /users/{id}/top-answer-tags

    Returns a single user's top tags by answer score. This a subset of the data returned on a user's tags tab. {id} can contain a single id, to find it programatically look for userid on user or shallowuser objects. This method returns a list of toptag objects.

  • Read

    GET /users/{id}/top-question-tags

    Returns a single user's top tags by question score. This a subset of the data returned on a user's tags tab. {id} can contain a single id, to find it programatically look for userid on user or shallowuser objects. This method returns a list of toptag objects.

  • Read

    GET /users/{id}/write-permissions

    Returns the write permissions a user has via the api. The Stack Exchange API gives users the ability to create, edit, and delete certain types. This method returns whether the passed user is capable of performing those actions at all, as well as how many times a day they can.

See How connections work for access and permissions, or browse all integrations.

Reference date: October 27, 2026. Stack Exchange API docs.