mocop
Browse · Docs · Guide · Analyze

Maeve Social API

API by Maeve Social · rest

Public API for managing Maeve workspaces, integrations, content, media, inbox, analytics, workbench data, and API keys. Use Authorization: Bearer <credential> for API requests. - API keys (ezb_live_...) are best for CI, servers, scripts, and long-running automation. - CLI browser login is best for a person using a terminal. Run maeve auth:login or npx maeve-cli auth:login. It creates a revocable local ezb_cli_... token that lasts 90 days from its last use. - CLI credential order is --api-key, --api-key-env <name>, MAEVE_API_KEY, then the stored login for the selected API URL. - Connect agents to /mcp on the API environment you intend to use. MCP browser sign-in is separate from CLI login. API keys are a fallback for clients without OAuth and server automation. - Read workspaces, integrations and integration capabilities before creating content. Start with a draft, then schedule or publish when ready. - API, CLI and MCP expose different operations. Use the current…

Verification: observed. Source: crawl.

Capabilities (445)

  • List workspaces
  • List ad accounts
  • Read account balance spend and pacing
  • List paid campaigns
  • Change a campaign or ad set budget
  • Read budget requirements for a campaign or ad set
  • List rejected ad sets and ads
  • Pause or resume paid campaigns
  • Read a paid campaign
  • Read ad account capabilities
  • List creatives with performance
  • List every ad set or ad in an ad account
  • Read the refresh state of an ad account
  • Refresh an ad account's saved campaigns and results
  • Read paid ad results by age gender country or placement
  • Read the client report
  • Export the client report as CSV
  • Read the daily paid ad series
  • Read paid ad totals
  • Read today's paid ad figures
  • Read a campaign creation approval
  • List Google ad groups
  • List Google ads
  • List Performance Max asset groups
  • Find Google audience segments and saved audiences
About · Contact · Privacy