Skip to main content
You need curl and an internet connection. No application registration, account, client secret or bearer token is needed for this public read.
A successful request returns HTTP 200 and a JSON object with a posts array. The array can be empty. Each available post is a public network contribution, subject to the network’s availability rules. To inspect the HTTP status and response headers, add --include. If you receive HTTP 429, wait for the number of seconds in Retry-After before retrying. See anonymous limits.

​
Explore the reference

Open API reference → Social → Read the public or following feed, leave authentication empty and select Send. Anonymous operations have no security requirement in the OpenAPI description. The reference also generates examples for curl, JavaScript and Python. For an authorized operation, use an access token obtained by your registered confidential client through authorization code with PKCE. Paste the access token into the playground’s bearer authentication field; do not paste your client secret. Private social operations require the documented scopes. OAuth token, introspection and revocation endpoints use confidential client Basic authentication instead of bearer authentication. Use synthetic credentials when exploring a preview. The interactive playground sends requests to the API through Mintlify’s proxy. Responses and tokens remain sensitive even when used from documentation. Continue with the generated operation descriptions for parameters, response shapes, status codes and authentication requirements. Do not use anonymous reads to bypass a refusal in a signed-in experience.