Adgogo Open API
★ Only Publicly Available OpenAPI DocumentMarketingAdvertisingapiKey3 EndpointsREST
For Agents
Pull ads, leads, and report data out of Adgogo via three POST endpoints. Used by reporting and lead-routing agents to keep BI dashboards and CRMs in step with Adgogo campaigns.
Use for: Get the list of ads currently running in the Adgogo account, Pull all leads captured by Adgogo campaigns yesterday, Retrieve a weekly performance report from Adgogo, I need to sync Adgogo leads into a CRM
Not supported: Does not create, edit, or pause ads and campaigns — use for pulling ad lists, leads, and report data only.
Jentic publishes the only available OpenAPI specification for Adgogo Open API, keeping it validated and agent-ready. Adgogo (also branded Quickeast) is a digital advertising operations platform popular with APAC marketers running paid social and search campaigns. The Open API has three POST endpoints — ad list, leads list, and report — designed for periodic pulls into a customer's BI warehouse or CRM rather than real-time creative editing. Authentication is an AccessKey passed in the AccessKey header.
Install Jentic One Beta
Connect the Adgogo Open API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Adgogo Open API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Adgogo Open API.
Retrieve a list of ads currently configured in the Adgogo account
Pull captured lead records from active campaigns into a CRM or warehouse
Fetch report data covering spend, impressions, clicks, and conversions
Filter results by campaign, date range, and other request-body parameters
Schedule periodic exports of leads and reporting into downstream systems
Use Cases
Patterns agents use Adgogo Open API for, with concrete tasks.
★ Lead sync from Adgogo to CRM
Marketing operations want every Adgogo-generated lead to land in the company CRM within minutes. POST /leads/list returns the recently captured leads, which a sync job maps to CRM contact fields and posts upstream. This avoids manual CSV exports and keeps sales teams working from a single timeline.
POST /leads/list with a date filter set to the last hour, then map each lead to the CRM contact schema and post it upstream.
Daily ad performance reporting
Performance marketers track spend and ROAS across every paid channel. POST /report/get against Adgogo returns daily metrics that can be loaded into a BI warehouse alongside data from other ad platforms, allowing a reporting agent to produce a unified daily roll-up rather than logging into each platform's dashboard.
POST /report/get with start_date and end_date both set to yesterday, then write the response into the BI warehouse's ad-spend table.
Ad inventory audit
Account managers periodically check which ads are live and which are paused. POST /ad/list returns the current ad inventory so an automation can cross-reference it against the campaign brief and flag any ads that are missing or unexpectedly running. This catches misconfigurations before budget drains.
POST /ad/list and compare the returned ads against the planned campaign list, flagging any discrepancies for the account manager to review.
AI agent reporting via Jentic
An AI marketing assistant uses Jentic to fetch yesterday's Adgogo report whenever the user asks for a performance summary. The agent searches 'get adgogo report data', loads the POST /report/get schema, fills the date range, and summarises the response in plain language. The AccessKey never enters the agent's context — Jentic injects it from the MAXsystem vault.
Use Jentic to search 'get adgogo report data', load the POST /report/get schema, and execute with start_date and end_date set to yesterday for the requested account.
Key Endpoints
3 endpoints — jentic publishes the only available openapi specification for adgogo open api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/ad/list
Get the list of configured ads
POST
/leads/list
Pull captured leads
POST
/report/get
Fetch report data for a date range
POST
/ad/list
Get the list of configured ads
POST
/leads/list
Pull captured leads
POST
/report/get
Fetch report data for a date range
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Adgogo AccessKey is stored encrypted in the Jentic MAXsystem vault and added to the AccessKey header at execute time. Agents never see the key in their context.
Intent-based discovery
Agents search by intent (e.g., 'get adgogo leads' or 'get adgogo report data') and Jentic returns the matching POST operation with its input schema — important because Adgogo does not publish a public OpenAPI spec.
Time to first call
Direct integration without a published spec: half a day reading partner docs and shaping each request body. Through Jentic: under 20 minutes — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Adgogo Open API through Jentic.
Why is there no official OpenAPI spec for Adgogo Open API?
Adgogo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Adgogo Open API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.
What authentication does the Adgogo Open API use?
The API uses an API-key scheme: a value called AccessKey is sent in the AccessKey HTTP header on every request. Jentic stores the AccessKey encrypted in the MAXsystem vault and adds the header at execute time so it never appears in agent context.
Can I sync leads from Adgogo into a CRM with this API?
Yes. POST /leads/list returns the recent leads captured across active campaigns. A sync job can poll this endpoint on a schedule (for example every five minutes) and post each lead into the destination CRM via that CRM's own API.
How do I pull a daily performance report through Jentic?
Search Jentic for 'get adgogo report data', load the POST /report/get schema, and execute with start_date and end_date set to the day you want. Jentic returns the metrics body so you can write it into your BI warehouse.
Are there rate limits on the Adgogo Open API?
Adgogo does not declare explicit rate limits in this spec. The endpoints are pull-only and intended for periodic syncs — schedule polls at a reasonable cadence (every few minutes for leads, hourly or daily for reports) and respect any 429 surfaced through Jentic.
Can I edit ads or campaigns with this API?
No. The Open API is pull-only — it returns ads, leads, and reports but does not create or update campaigns. Creative changes still need to be made in the Adgogo dashboard or via internal Adgogo tooling.
GET STARTED