Adgo Quickeast (Adgogo) Open API

Name: Quickeast (Adgogo) Open API
Brand: Quickeast (Adgogo) Open API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingAdvertisingapiKey3 EndpointsREST

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

Install Jentic One Beta

Connect the Quickeast (Adgogo) Open API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Quickeast (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.

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

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 instance

Jentic 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 Quickeast (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

GET STARTED

Start building with Quickeast (Adgogo) Open API

Explore with Jentic

View OpenAPI Document

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.

Use Cases

Patterns agents use Quickeast (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 from Adgogo and keeps the sales team working on a single timeline.

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.

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.

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 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 quickeast (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 the partner docs and shaping each request body. Through Jentic: under 20 minutes — search, load schema, execute.

FAQs

Specific to using Quickeast (Adgogo) Open API through Jentic.

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

Adgo Quickeast (Adgogo) Open API

Connect the Quickeast (Adgogo) Open API to your agent

Capabilities

Start building with Quickeast (Adgogo) Open API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs