Install Jentic One Beta

Connect the Marketo REST API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Marketo REST 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://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmarketo.com%2Fmarketo" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmarketo.com%2Fmarketo" | 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 Marketo REST API.

Query, create, update, and delete leads

Read lead activities and change data

Manage static lists and their membership

Administer assets such as programs and emails

Work with companies, opportunities, and custom objects

GET STARTED

Start building with Marketo REST API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use Marketo REST API for, with concrete tasks.

★ Lead Sync and Enrichment

An AI agent connected through Jentic can keep lead records current. It queries leads by filter, creates or updates them in batches, and reads the describe metadata to map fields, so an assistant can sync records from another system into Marketo without hand-built payloads.

Create or update a batch of leads from an external list and return the results

Campaign and List Management

Marketers run programs against segmented lists. The Marketo REST API manages static lists and their membership and administers programs and emails, letting an agent add leads to a list or read program membership as part of a campaign workflow.

Add a set of leads to a static list and confirm their membership

Activity and Engagement Tracking

Reporting needs the record of what a lead did. The API returns lead activities, activity types, and change data with paging tokens, so an agent can pull recent engagement for a segment and feed it into analysis or a downstream action.

Fetch recent lead activities since a paging token and summarize engagement

Key Endpoints

103 endpoints — the marketo rest api manages marketing automation data in an adobe marketo engage instance.

METHOD

PATH

DESCRIPTION

GET

/rest/v1/leads.json

Get leads by filter type

POST

/rest/v1/leads.json

Create or update leads

GET

/rest/v1/lead/{leadId}.json

Get a lead by ID

GET

/rest/v1/activities.json

Get lead activities

GET

/rest/asset/v1/programs.json

Get programs

GET

/rest/v1/lists.json

Get static lists

GET

/rest/v1/leads.json

Get leads by filter type

POST

/rest/v1/leads.json

Create or update leads

GET

/rest/v1/lead/{leadId}.json

Get a lead by ID

GET

/rest/v1/activities.json

Get lead activities

GET

/rest/asset/v1/programs.json

Get programs

GET

/rest/v1/lists.json

Get static lists

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Marketo REST API by hand means registering a service, exchanging client credentials for an access token, refreshing it before expiry, and mapping the describe metadata yourself. Through Jentic you install once, import Marketo from the API Directory, store the client credentials once, and your agent calls the lead, activity, and asset operations directly.

Permission scoping

You choose which of the operations your agent may call. You might allow lead queries and activity reads while blocking lead deletion and asset changes, so the agent can report without editing the instance.

Credential isolation

Your Marketo client credentials are stored once, encrypted, by your own Jentic One instance, and the access token is obtained and injected at execution time. Secrets never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'create or update leads', and Jentic returns the matching Marketo operation with its input schema so the agent calls it with the right records.

FAQs

Specific to using Marketo REST API through Jentic.

What authentication does the Marketo REST API use?

It uses OAuth 2.0: your agent exchanges a client ID and secret at the identity endpoint for a bearer access token, then sends that token as a Bearer credential on each call. Through Jentic the client credentials are stored once, encrypted, by your own self-hosted instance, and the token is obtained and injected at execution time, so secrets never appear in the agent's prompt or logs.

Can I limit what my agent is allowed to do with the Marketo REST API?

Yes. You choose which operations the agent may call. You might allow lead queries and activity reads while blocking lead deletion and asset changes, so the agent can report without editing the instance, with every call logged by your own instance.

Is there a Marketo MCP server?

You don't need an MCP server to give your agent the Marketo REST API. Jentic connects it directly from the API Directory: import it, store your client credentials once, and your agent calls the lead, activity, and asset operations. Operations are discovered on demand, so nothing extra loads into the agent's context.

What are the rate limits for the Marketo REST API?

The OpenAPI spec does not define rate limits. Marketo enforces per-instance daily quotas and concurrency limits, so check the Adobe Marketo Engage documentation for the limits on your instance before running high-volume jobs.

What can the Marketo REST API do?

It manages leads, activities, lists, companies, opportunities, and custom objects, administers assets such as programs and emails, and runs bulk import and export of leads and activities within an Adobe Marketo Engage instance.

How do I sync leads to Marketo through Jentic?

Search Jentic by intent, for example 'create or update leads', and Jentic returns the matching Marketo operation with its input schema. Your agent supplies the lead records and reads back the per-record result. To run it on your own infrastructure, install Jentic One from its GitHub repo.

Marketo REST API

Name: Marketo REST API
Brand: Marketo REST API
Availability: InStock

Official vendor OpenAPI document · agent-readyMarketingMarketing AutomationOAuth 2.0 (Bearer token)103 EndpointsREST

For Agents

Query and update leads, read activities, manage lists and membership, and administer assets like programs and emails in a Marketo instance. Uses OAuth 2.0 to obtain a bearer access token.

Use for: Get leads matching a filter, Create or update a batch of leads, Retrieve a lead by its identifier, List recent lead activities

Not supported: Does not handle web analytics or ad spend. Use the Marketo REST API for lead management, activities, lists, smart campaigns, and marketing assets within a Marketo instance.

The Marketo REST API manages marketing automation data in an Adobe Marketo Engage instance. It queries, creates, updates, and deletes leads, reads lead activities and change data, manages static lists and their membership, works with companies, opportunities, and custom objects, and administers assets such as programs and emails. Bulk import and export operations move large lead and activity sets in and out.

Jentic One on Github View OpenAPI Document

Connect the Marketo REST API to your agent

Capabilities

Start building with Marketo REST API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

Marketo REST API