> ## Documentation Index > Fetch the complete documentation index at: https://aisa.one/docs/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > - Base URLs: models `https://api.aisa.one/v1` (Gemini GenerateContent: `https://api.aisa.one/v1beta`); data APIs `https://api.aisa.one/apis/v1`. The `servers` of each operation in https://aisa.one/openapi.yaml is authoritative. > - Auth: `Authorization: Bearer $AISA_API_KEY`. Never print, log, or commit the key. > - MCP (preferred for agents): `https://mcp.aisa.one/mcp`, signed in with OAuth, so there is no key to paste. > - Agent Skill: `npx skills add AIsa-team/agent-skills --skill aisa`. Fallback with the AIsa CLI: `aisa skills install aisa`. > - Spending: docs, https://aisa.one/models, https://aisa.one/api, `/v1/models`, and MCP `search`, `list_categories`, `get_details`, `batch_quote`, and the `account` operation are free. Quote the exact calls before running them (MCP `batch_quote`, CLI `aisa quote --json`). If the quote reports `auto_execute_eligible: true`, run it unless the user set a tighter limit or asked only for a quote. Otherwise, tell the user in one message the planned calls, the quoted price, and a total USD budget for the task, then wait for approval. Direct HTTP calls follow the stricter rule at https://aisa.one/docs/get-started/cli.md#direct-http-fallback. Do not make paid calls to test availability. Full rule: https://aisa.one/llms.txt # Get Facebook post monetization earnings > Analytics. Read only; needs social:read. Ids are yours: accounts acc_..., profiles prf_..., posts pst_...; every other object id is checked against your accounts before the call. Returns lifetime monetization earnings for ONE Facebook post, read live from Meta on every request. ### Lifetime totals only Earnings are CUMULATIVE since the post was published, not earnings within a date range. So this endpoint takes no since/until, and the totals must not be summed across dates or across posts. Page-level daily earnings live on /apis/v1/social/analytics/facebook/page-insights. ### Zeros and missing metrics - A post on a Page that is not enrolled in monetization, or that earned nothing, returns "total": 0 rather than an error: Meta does not distinguish the two. - A metric Meta returned no bucket for at all is reported in "unavailableMetrics" and omitted from "metrics", never as a 0. Amounts are the platform's raw numbers in the stated "unit" and are never rescaled by AIsa. ### Rejected parameters These are rejected with 400: - "breakdown": breakdown dimensions are not exposed. - "since", "until", "period", and "metricType": scoping this endpoint to a window is not possible. Silently returning the lifetime total for a window would let a caller sum a year of weekly requests into a figure ~52x the post's real earnings. 当前未提供请求参考价格；请使用接口支持的报价功能确认费用。 最终费用以账户适用价格及实际结算为准。 ## 请求规范 * **方法与路径:** GET /apis/v1/social/analytics/facebook/post-earnings * **可用状态:** enabled * **请求 URL 模板:** `https://api.aisa.one/apis/v1/social/analytics/facebook/post-earnings` * **accountId:** query; 必填 * **postId:** query; 必填 * **metrics:** query; 可选 * **Runtime 事实版本:** 99acb5bddbedc8d3352e7c4fef86c3e6d8852c14772bcd18dbcf415237a642bd [完整 OpenAPI 定义](https://aisa.one/docs/reference-contracts/zh/aisa-social.json) 有效请求与价格声明（包括认证和引用的 schema）： ```json theme={null} { "operationId": "get_aisa_social_apis_v1_social_analytics_facebook_b22e2b", "method": "GET", "path": "/apis/v1/social/analytics/facebook/post-earnings", "servers": [ { "url": "https://api.aisa.one" } ], "parameters": [ { "description": "One of your social accounts (acc_...).", "in": "query", "name": "accountId", "required": true, "schema": { "pattern": "^acc_[0-9A-Za-z]{22}$", "type": "string" } }, { "description": "The platform post ID, exactly as returned in platformAnalytics[].platformPostId by\n/apis/v1/social/analytics: \"{pageId}_{postId}\", or the bare video ID for Reels.", "in": "query", "name": "postId", "required": true, "schema": { "type": "string" } }, { "description": "Comma-separated list of monetization metrics. Defaults to both:\n - content_monetization_earnings\n - monetization_approximate_earnings\n\ncontent_monetization_earnings always carries unit \"micro_amount\" plus an ISO 4217\n\"currency\". monetization_approximate_earnings is always a bare number, so its unit is\n\"unspecified\" and its \"currency\" is null. The two are on different scales and are not\ncomparable to each other. Any other metric name is rejected with 400.", "in": "query", "name": "metrics", "required": false, "schema": { "type": "string" } } ], "security": [ { "bearerAuth": [] } ], "x-aisa-status": "enabled", "x-aisa-pricing": { "description": "Included with your connected social accounts: AIsa does not charge per call.", "kind": "no_customer_charge" }, "components": { "securitySchemes": { "bearerAuth": { "scheme": "bearer", "type": "http" } } } } ``` ## 费用与请求规则 当前未提供请求参考价格；请使用接口支持的报价功能确认费用。 最终费用以账户适用价格及实际结算为准。 公开参考值不是你的账户报价或最终扣费。对于支持 X-AISA-Cost-Mode: quote 的接口，执行前请针对完整请求获取免费报价；执行后通过响应费用元数据和 Usage Logs 核对结算费用。1 USD 等于 1,000,000 个整数 micro-USD。 ## OpenAPI ````yaml reference-contracts/zh/aisa-social.json GET /apis/v1/social/analytics/facebook/post-earnings openapi: 3.1.0 info: description: '' title: AIsa Social version: '1' x-aisa-capabilities: idempotency: Idempotency-Key max_price: X-AISA-Max-Price-USD quote: header: X-AISA-Cost-Mode value: quote x-aisa-configured-paths: [] x-aisa-document: facts_hash: 99acb5bddbedc8d3352e7c4fef86c3e6d8852c14772bcd18dbcf415237a642bd generator_version: '3' protocol_version: '1' schema_version: '1' composer_version: '27' response_pending: [] document_hash: sha256:7f9742cb1ea233c648dcb290fdfbf24e53a27dcf900ec1386f83a8ef2e6b1bf9 x-aisa-plans: builder: 1 display_plan: payg payg: 1 similarweb_payg: 1 team: 1 version: e70a0959cd1b93b84ae16dffd7a538273ddb9c1d46277b82823c37ff1b6bc0fb x-aisa-provider: aisa-social x-aisa-catalogs: aisa-social: title: AIsa Social description: '' x-aisa-document: facts_hash: 99acb5bddbedc8d3352e7c4fef86c3e6d8852c14772bcd18dbcf415237a642bd generator_version: '3' protocol_version: '1' schema_version: '1' x-aisa-plans: builder: 1 display_plan: payg payg: 1 similarweb_payg: 1 team: 1 version: e70a0959cd1b93b84ae16dffd7a538273ddb9c1d46277b82823c37ff1b6bc0fb x-aisa-capabilities: idempotency: Idempotency-Key max_price: X-AISA-Max-Price-USD quote: header: X-AISA-Cost-Mode value: quote servers: - url: https://api.aisa.one security: - bearerAuth: [] paths: /apis/v1/social/analytics/facebook/post-earnings: get: summary: Get Facebook post monetization earnings description: >- Analytics. Read only; needs social:read. Ids are yours: accounts acc_..., profiles prf_..., posts pst_...; every other object id is checked against your accounts before the call. Returns lifetime monetization earnings for ONE Facebook post, read live from Meta on every request. ### Lifetime totals only Earnings are CUMULATIVE since the post was published, not earnings within a date range. So this endpoint takes no since/until, and the totals must not be summed across dates or across posts. Page-level daily earnings live on /apis/v1/social/analytics/facebook/page-insights. ### Zeros and missing metrics - A post on a Page that is not enrolled in monetization, or that earned nothing, returns "total": 0 rather than an error: Meta does not distinguish the two. - A metric Meta returned no bucket for at all is reported in "unavailableMetrics" and omitted from "metrics", never as a 0. Amounts are the platform's raw numbers in the stated "unit" and are never rescaled by AIsa. ### Rejected parameters These are rejected with 400: - "breakdown": breakdown dimensions are not exposed. - "since", "until", "period", and "metricType": scoping this endpoint to a window is not possible. Silently returning the lifetime total for a window would let a caller sum a year of weekly requests into a figure ~52x the post's real earnings. 当前未提供请求参考价格；请使用接口支持的报价功能确认费用。 最终费用以账户适用价格及实际结算为准。 operationId: get_aisa_social_apis_v1_social_analytics_facebook_b22e2b parameters: - description: One of your social accounts (acc_...). in: query name: accountId required: true schema: pattern: ^acc_[0-9A-Za-z]{22}$ type: string - description: >- The platform post ID, exactly as returned in platformAnalytics[].platformPostId by /apis/v1/social/analytics: "{pageId}_{postId}", or the bare video ID for Reels. in: query name: postId required: true schema: type: string - description: >- Comma-separated list of monetization metrics. Defaults to both: - content_monetization_earnings - monetization_approximate_earnings content_monetization_earnings always carries unit "micro_amount" plus an ISO 4217 "currency". monetization_approximate_earnings is always a bare number, so its unit is "unspecified" and its "currency" is null. The two are on different scales and are not comparable to each other. Any other metric name is rejected with 400. in: query name: metrics required: false schema: type: string responses: '200': content: application/json: schema: description: >- Lifetime monetization earnings for one Facebook post. Same "unit" / "currency" contract and same unavailable-vs-zero contract as the Page-level response; there is no date range, no metricType, and no daily "values", because the single lifetime bucket IS the total. properties: accountId: description: One of your social accounts (acc_...). pattern: ^acc_[0-9A-Za-z]{22}$ type: string dataDelay: type: string metrics: additionalProperties: properties: currency: description: >- ISO 4217 currency, or null when Meta omitted it. Always null on monetization_approximate_earnings; always present on content_monetization_earnings. type: - string - 'null' total: description: >- Lifetime earnings in "unit", exactly as Meta returned them. Never rescaled. type: number unit: description: >- "micro_amount": Meta returned an object shape carrying a micro amount, and "total" is that integer, unconverted. AIsa does not publish a divisor because Meta does not document one; divide by the scale you have verified against the Page's own Meta Business Suite export. This is always content_monetization_earnings. "unspecified": Meta returned a bare number with no unit metadata, passed through as-is; Meta does not state whether it is major or minor currency units. This is always monetization_approximate_earnings. enum: - micro_amount - unspecified type: string type: object description: >- One entry per served metric. A metric reported here with "total": 0 genuinely earned nothing (or its Page is not enrolled, which Meta reports identically). type: object period: description: >- Always "lifetime": the total is cumulative since publication and must not be summed across dates or across posts. enum: - lifetime type: string platform: type: string postId: description: The platform post ID that was queried, echoed back. type: string success: type: boolean unavailableMetrics: description: >- Requested metrics Meta could not serve. Present only when at least one metric is unavailable, and absent otherwise. Each listed metric is OMITTED from "metrics" rather than reported as 0. The request itself still succeeds with HTTP 200. items: properties: message: description: >- Platform-provided explanation when available (access tokens redacted), otherwise AIsa copy. type: string metric: description: The requested metric name. type: string reason: description: >- Why the metric is unavailable: - "not_enrolled": the account is not enrolled in the program behind this metric. - "permission_missing": the connected user lacks access to this metric. - "unsupported_metric": Meta does not accept this metric name on the API version AIsa uses. - "no_data": Meta returned no bucket for this metric. - "unreadable_value": Meta returned a value shape AIsa cannot read, so no total is reported. - "mixed_currency": readable values disagree on currency or unit. - "upstream_error": any other platform failure. "no_data" is the common case in practice; the others are defensive. enum: - not_enrolled - permission_missing - unsupported_metric - no_data - unreadable_value - mixed_currency - upstream_error type: string type: object type: array type: object description: Lifetime per-post monetization earnings default: content: application/json: schema: properties: error: properties: code: type: - string - 'null' details: additionalProperties: {} type: - object - 'null' message: type: - string - 'null' param: type: - string - 'null' retryHint: enum: - never - after_delay - after_reconnect - reconcile_first - null type: - string - 'null' retryable: type: - boolean - 'null' type: type: - string - 'null' type: - object - 'null' type: object description: Error. The code field is stable; see the error catalog. components: securitySchemes: bearerAuth: scheme: bearer type: http ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.