> ## Documentation Index > Fetch the complete documentation index at: https://postmesh.app/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get a post's numbers > Views, likes, comments and shares for one post on each network, with how they changed. Needs an API key with the `read` scope. ## OpenAPI ````yaml /openapi.json get /posts/{id}/analytics openapi: 3.1.0 info: title: PostMesh API version: 1.0.0 description: >- The PostMesh API posts, schedules and reads your posts on every network you connected, with JSON in and out. **Authentication.** Send an API key from Settings, API & MCP as `Authorization: Bearer pm_live_...`. Each key has scopes (read, drafts, publish, media); every endpoint says which it needs. **Retries.** Send an `Idempotency-Key` header (up to 255 printable characters, a UUID is ideal) with every POST. Sending the same key again within 24 hours answers with the first request's status and body instead of posting twice, and says so with `Idempotent-Replayed: true`. A request still running under the key answers 409; one that failed with a 5xx or 429 frees the key, so the retry runs. The same key with a different body is refused with 422. **Rate limits.** Each key may make 120 requests a minute. Every answer carries `X-RateLimit-Limit`, `X-RateLimit-Remaining` and `X-RateLimit-Reset` (Unix seconds); a 429 also carries `Retry-After`. Posting and uploads have their own, smaller limits. **Errors.** A refusal is JSON with `error` (plain words) and `code` (stable, to act on). servers: - url: https://postmesh.app/api/v1 security: - apiKey: [] tags: - name: Posts description: Send, schedule, change and read posts. - name: Drafts description: Posts saved for later. - name: Media description: Images and videos for posts. - name: Accounts description: Your connected accounts and your plan. - name: Analytics description: How your posts did. paths: /posts/{id}/analytics: get: tags: - Analytics summary: Get a post's numbers description: >- Views, likes, comments and shares for one post on each network, with how they changed. Needs an API key with the `read` scope. operationId: getPostAnalytics parameters: - name: id in: path required: true description: The post's id. schema: type: string format: uuid - name: refresh in: query required: false schema: type: string enum: - 'true' - 'false' description: >- true reads every post's numbers from the networks now (a few times a minute at most). responses: '200': description: The post's numbers. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' content: application/json: schema: $ref: '#/components/schemas/Analytics' '400': $ref: '#/components/responses/BadRequest' '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/TooManyRequests' '503': $ref: '#/components/responses/Unavailable' components: headers: X-RateLimit-Limit: description: Requests this key may make in a minute. schema: type: integer X-RateLimit-Remaining: description: Requests left this minute. schema: type: integer X-RateLimit-Reset: description: When the minute resets, in Unix seconds. schema: type: integer schemas: Analytics: type: object additionalProperties: {} description: >- The numbers PostMesh reads from each network for your posts, as the Analytics page shows them. Error: type: object properties: error: type: string description: What went wrong, in plain words. code: type: string description: >- A stable code to act on, such as invalid_request, rate_limited or idempotency_key_reused. field: description: The request field that was refused. type: string retry_after: type: integer minimum: -9007199254740991 maximum: 9007199254740991 required: - error - code additionalProperties: false description: Every refusal looks like this. responses: BadRequest: description: >- The request was refused: a field is missing or invalid. `field` names it. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' content: application/json: schema: $ref: '#/components/schemas/Error' Unauthorized: description: No API key, or one that isn't valid any more. content: application/json: schema: $ref: '#/components/schemas/Error' Forbidden: description: >- The key can't do this: it needs another scope (`code` is `api_key_scope`), or it is in approval mode. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' content: application/json: schema: $ref: '#/components/schemas/Error' NotFound: description: No such item in your PostMesh. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' content: application/json: schema: $ref: '#/components/schemas/Error' TooManyRequests: description: Too many requests. Wait for `Retry-After` seconds. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' Retry-After: description: Seconds to wait. schema: type: integer content: application/json: schema: $ref: '#/components/schemas/Error' Unavailable: description: PostMesh can't answer right now. Try again shortly. headers: X-RateLimit-Limit: $ref: '#/components/headers/X-RateLimit-Limit' X-RateLimit-Remaining: $ref: '#/components/headers/X-RateLimit-Remaining' X-RateLimit-Reset: $ref: '#/components/headers/X-RateLimit-Reset' content: application/json: schema: $ref: '#/components/schemas/Error' securitySchemes: apiKey: type: http scheme: bearer description: 'An API key from Settings, API & MCP: pm_live_...' ```` ## Related topics - [Get a post](https://postmesh.app/docs/api-reference/posts/get-a-post.md) - [MCP tool reference](https://postmesh.app/docs/mcp-tools.md) - [Get analytics](https://postmesh.app/docs/api-reference/analytics/get-analytics.md) - [Analytics for posts sent from PostMesh](https://postmesh.app/docs/analytics.md) - [PostMesh docs](https://postmesh.app/docs/index.md) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.