Request OpenAPI specs for Marketing API and Conversions API

The issue names no existing files, tests, or entry points. Start by reviewing the repository's current specifications and coverage, then determine how versioned Marketing API and Conversions API definitions should be organized. Done means publishing accurate specs with the requested endpoints, schemas, security details, and examples, but the scope requires design decisions before implementation.

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.