Stackexchange

Connector for the stackexchange API, generated deterministically from its OpenAPI spec (endpoints, auth, and methods match the spec exactly — nothing is invented).

• Base URL: https://api.stackexchange.com/2.0
• Auth: OAuth 2.0 (user-delegated) — attach an InTouch oauth credential. Mint one with itcli.py /oauth <provider> (device-code) or /google-auth (Google); the server auto-refreshes the access token before each run, so the connector never handles or stores tokens.

Operations

• get_access_tokens_accesstokens — GET /access-tokens/{accessTokens} — Reads the properties for a set of access tokens.

{accessTokens} can contain up - get_access_tokens_accesstokens_invalidate — GET /access-tokens/{accessTokens}/invalidate — Immediately expires the access tokens passed. This method is meant to allow an a - get_answers — GET /answers — Returns all the undeleted answers in the system.

The sorts accepted by this me - get_answers_ids — GET /answers/{ids} — Gets the set of answers identified by ids.

This is meant for batch fetcing of - get_answers_ids_comments — GET /answers/{ids}/comments — Gets the comments on a set of answers.

If you know that you have an answer id - get_apps_accesstokens_de_authenticate — GET /apps/{accessTokens}/de-authenticate — Passing valid access_tokens to this method causes the application that created t

Inputs

• a linked oauth credential (no key inputs) — the server injects a fresh Authorization: Bearer from it
• operation — one of the operations above
• path parameters when an operation's path contains {...}
• query — optional JSON object of query params
• body — JSON object for create/update ops

Example

operation: get_access_tokens_accesstokens
# (attach an 'oauth' credential to the task — no inline secrets)