Request OpenAPI specs for Marketing API and Conversions API

この issue には、既存のファイル、テスト、エントリポイントが記載されていません。まずリポジトリの現在の仕様とカバレッジを確認し、そのうえで、バージョン管理された Marketing API と Conversions API の定義をどのように整理すべきかを決定してください。要求されたエンドポイント、スキーマ、セキュリティの詳細、例を含む正確な仕様を公開することが完了の条件ですが、実装前に設計上の決定が必要です。

This was generated by AI during triage.

Request

Please consider publishing official OpenAPI specifications for the Meta Marketing API and Conversions API in this repository.

APIs requested

• Marketing API, including common Ads Management and Insights endpoints
• Conversions API, including event submission endpoints and related request/response schemas

Why this would help

Official OpenAPI specs would make it much easier for developers and partners to:

• generate typed clients and SDK integrations consistently across languages
• validate request payloads before sending traffic to production APIs
• keep integrations aligned with versioned API changes
• build better internal tooling, mocks, tests, and documentation from a trusted source
• reduce ambiguity around required fields, enum values, nested objects, and error responses

Suggested scope

A useful first version could include:

• versioned specs matching currently supported Marketing API versions
• endpoint paths, methods, parameters, request bodies, and response schemas
• authentication/security scheme details
• reusable schemas for ads, campaigns, ad sets, insights, pixels, events, user data, and error responses
• examples for common workflows such as campaign management, insights reporting, and Conversions API event uploads

Even partial coverage for the highest-usage endpoints would be valuable if complete coverage needs to be phased in.