> For the complete documentation index, see [llms.txt](https://docs.floral.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.floral.fun/api-v2/v2-overview.md). # Overview V2 adds the public social graph, conversations, search, analytics, bulk reading and webhooks. It's read-only, and it uses the same applications and tokens as V1. ## Authentication Send a bearer token from [Floral Connect](/authentication/floral-connect.md). An app token or a user token both work, and V2 doesn't use scopes. **A token never unlocks anything.** Your application sees what a signed-out stranger sees, even with a user's token, and even for that user's own account. See [Privacy and visibility](/api-v2/v2-privacy.md). ## Endpoints | Area | Endpoints | | --------------- | ------------------------------------------------------------------------------------------------------- | | Users | `GET /v2/users/search`, `/v2/users/{id}`, `/followers`, `/following`, `/activity`, `/communities` | | Posts | `GET /v2/posts/{id}`, `/replies`, `/thread`, `/quotes`, `/reposts`, `/likes`, `/engagement` | | Communities | `GET /v2/communities/search`, `/v2/communities/{id}`, `/activity` | | Topics | `GET /v2/topics/search`, `/v2/topics/{slug}`, `/posts` | | Search and feed | `GET /v2/search/posts`, `/v2/feed/public` | | Analytics | `GET /v2/analytics/posts/{id}`, `/users/{id}`, `/communities/{id}`, `/topics/{slug}`, `/hashtags/{tag}` | | Bulk | `GET /v2/bulk/events`, with approval | The [OpenAPI specification](https://github.com/0xtpsn/floral-gitbook/tree/main/openapi.yaml) has every parameter and schema. ## Pagination List endpoints take `limit` (1-100, default 25) and return `next_cursor`: ```bash curl "https://api.floral.fun/v2/users/@alice/followers?limit=50" \ -H "Authorization: Bearer $TOKEN" ``` ```json { "data": [ { "id": "usr_789", "username": "bob", "display_name": "Bob", "avatar_url": null, "is_bot": false, "url": "https://floral.fun/profile/bob" } ], "next_cursor": "WyIyMDI2..." } ``` Send `next_cursor` back as `cursor`. A null `next_cursor` means the end. **A page can be shorter than `limit`, or empty, with more to come.** The final privacy check runs after rows are found. Always follow `next_cursor`, and don't stop because a page looks short. Treat cursors as opaque. Privacy applies between pages too, so someone who hides their list while you're paging drops out of the rest of it, and a list that becomes hidden returns `403` on the next page. ## Post fields V2 posts have the [V1 post fields](/api-reference/posts.md), plus: ```json { "type": "original", "quality": { "author_is_bot": false, "author_account_age_days": 412 } } ``` `type` is `original`, `reply`, `quote` or `repost`. `quality` holds facts for your own spam rules, and Floral doesn't score posts for you. `quote_post_id` is null when the quoted post isn't public, even though the quote itself is. ## Profile fields `GET /v2/users/{id}` has the [V1 user fields](/api-reference/users.md), plus `follow_lists_public` and `communities_public`, so you can check before asking for a list. ## Threads `GET /v2/posts/{id}/thread` returns the post, the public `ancestors` above it, and public `replies` below it, oldest first. It returns up to 200 replies across 8 levels, and `truncated` is `true` if there are more. Use `/v2/posts/{id}/replies` to page through direct replies. A non-public reply takes its whole branch with it. ## Likes `GET /v2/posts/{id}/likes` returns the count, and doesn't list who liked it: ```json { "likes_count": 12, "likers_available": false } ``` Floral doesn't show anyone who liked a post, so the API doesn't either. To check one user's like, use [verification](/api-reference/verification.md) with their consent. ## Errors V2 uses the [same error shape as V1](/developer-resources/errors.md): | Status | Code | Meaning | | ------ | -------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- | | 400 | `invalid_id`, `invalid_limit`, `invalid_cursor`, `invalid_query`, `invalid_type`, `invalid_date_range`, `invalid_interval` | A parameter is malformed | | 401 | `invalid_token` | Missing, expired or revoked token | | 403 | `visibility_restricted` | This list or activity isn't public | | 403 | `entitlement_required` | This feature needs approval from Floral | | 404 | `not_found` | Doesn't exist, or isn't public | | 429 | `rate_limited`, `quota_exceeded` | See below | | 500 | `server_error` | Retry with backoff | | 503 | `temporarily_unavailable` | Retry later | ## Rate limits and quotas | Limit | Amount | | ----------- | ------------------------------------------------------------------ | | Requests | Your application's per-minute limit, counted apart from V1 | | Developer | 300 requests a minute across a developer's unverified applications | | Search | 60 requests a minute | | Bulk | 30 requests a minute | | Daily quota | 100,000 requests | Responses include the `X-RateLimit-*` headers, plus `X-Quota-Limit`, `X-Quota-Remaining` and `X-Quota-Reset`. Always follow `Retry-After` on a `429`. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.floral.fun/api-v2/v2-overview.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.