Developer Resources — OneClick Ads
This page gathers, in one place, everything a developer — or an AI agent — needs to integrate with OneClick Ads.
OneClick Ads MCP server
Section titled “OneClick Ads MCP server”The MCP server address is:
https://mcp.oneclickads.com.br/mcpThis is how an AI assistant reads and operates your account: ad accounts, campaigns, ad sets, ads, optimizations and the conversions recorded by OneClick Tracking.
- Connect an AI assistant (MCP) — the two ways
to authenticate: OAuth (interactive login, as in the Claude connector) and an API key
in the
Authorization: Bearer <token>header, with acurlexample. - What you can ask the assistant — the full list of MCP articles.
Your API keys and connected apps are under Connections → Connected apps, where you can also revoke access for any integration.
Conversion webhook (OneClick Tracking)
Section titled “Conversion webhook (OneClick Tracking)”If your platform isn’t in the list of ready-made integrations, you send conversions through a custom webhook:
- Custom Integration — the webhook step by step, including a ready-made Make scenario.
- Integration catalog — Hotmart, Kiwify, Shopify, Nuvemshop, HubSpot, Pipedrive, Kommo, RD Station CRM and the other supported platforms.
- Attribution modes — how each conversion is linked to the campaign it came from by its UTM.
Machine-readable files
Section titled “Machine-readable files”This documentation is also published in formats that agents can consume directly:
| Address | What it is |
|---|---|
/llms.txt | Index of every page, with title, description and Markdown link |
/llms-full.txt | The full documentation content in a single Markdown file |
/AGENTS.md | Instructions for agents: when to use this documentation and how to search it |
/sitemap-index.xml | XML sitemap of every page |
In addition, every page has a Markdown version at the same address with the .md
suffix — for example, …/en/faq/ also responds at …/en/faq.md.