canonical: https://jentic.com/apis/adgo.co/adgo

# Adgo Quickeast (Adgogo) Open API

Jentic publishes the only available OpenAPI specification for Quickeast (Adgogo) Open API, keeping it validated and agent-ready. Adgogo (formerly Quickeast) is a multi-platform digital advertising operations tool used by Asia-Pacific marketers to manage paid social and search campaigns. The Open API exposes three POST endpoints: an ad-list query, a leads query, and a report query - designed for periodic pulls into a customer's BI or CRM stack rather than real-time creative editing. Authentication is an AccessKey passed in the AccessKey header.

## For AI agents

Pull ad lists, lead records, and reporting metrics out of Adgogo (Quickeast) for syncing into BI dashboards or CRMs. Used by reporting and lead-routing agents in APAC ad-ops teams.

## Scope

Does not create, edit, or pause ads and campaigns - use for pulling ad lists, leads, and report data only.

## Capabilities

- 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

### 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 from Adgogo and keeps the sales team working on a single timeline.

Example prompt: POST /leads/list with a date filter set to the last hour, then map each lead to the CRM's contact schema and post it upstream.

### Daily ad performance reporting

Performance marketers track spend and ROAS across every channel they run. POST /report/get against Adgogo returns daily metrics that can be piped into a BI warehouse alongside data from other ad platforms. Reporting agents can produce a unified daily roll-up rather than logging into each platform's dashboard.

Example prompt: POST /report/get with start_date yesterday and end_date yesterday for the requested account, then load 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, letting an automation cross-reference it against the campaign brief and flag any ads that are missing or unexpectedly running. This catches misconfigurations before budget drains.

Example prompt: 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 handles header injection from your Jentic One instance.

Example prompt: 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

| 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 |

## Key resources

- **Ad** — An advertisement configured in Adgogo, returned by the ad-list operation.
- **Lead** — A captured prospect record from active campaigns, returned by the leads-list operation.
- **Report** — Aggregated performance metrics for a date range, returned by the report operation.

## Why Jentic

- **Setup:** Wiring the Quickeast (Adgogo) Open API by hand means attaching the AccessKey header on every call and mapping reporting intents onto its list, leads, and report endpoints without a published spec. Through Jentic you install once, import the Adgogo Open API from the API Directory, store the AccessKey once, and your agent calls it.
- **Permission scoping:** These endpoints take query and filter details in the request body rather than a resource id in the URL, so limit the agent to the operations it needs, such as pulling leads or report data. You choose the operations it may call, so the ad-list pull is not included unless you add it.
- **Credential handling:** Your Adgogo AccessKey is stored once, encrypted, by your own Jentic One instance and injected into the AccessKey header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'get adgogo leads' or 'get adgogo report data', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs, which matters because Adgogo does not publish a public OpenAPI spec.

## Related APIs

- **Adgogo Open API** — The same Adgogo product exposed under the adgogo.co host with identical endpoint shapes.
- **Criteo API** — Performance ad platform with a richer reporting and creative API surface.
- **Outbrain API** — Native advertising platform with campaign management and reporting endpoints.

## FAQ

### Why is there no official OpenAPI spec for Quickeast (Adgogo) Open API?

Adgogo does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Quickeast (Adgogo) Open API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### 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 your Jentic One instance 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 its 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 three 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.

### Can I limit what my agent is allowed to do with the Adgogo Open API?

Yes. Because you run Jentic One yourself, you decide which of the three operations your agent can call: the leads pull (POST /leads/list), the report pull (POST /report/get), and the ad-list pull (POST /ad/list). Since these endpoints take their query and filter details in the request body rather than a resource id in the URL, you scope access by choosing the operations the agent may use, so a reporting agent can be given only /report/get while the ad-list pull stays off unless you add it. Your own rules govern which operations and which stored AccessKey the agent is permitted to use at execution time.