What we do
Tools
Industries
Department
How we workLet's talk →
Home/Marketo
Adobe Marketo Engage

Marketo API Access That Survives the Daily Quota

A Marketo integration that worked fine in testing often starts failing a few weeks later, partway through a busy day, because the subscription's call allowance has run out. Marketo Engage's REST API is well documented and dependable. Whether yours holds up comes down to how it authenticates, which endpoint it uses for each job and how many calls it spends doing it.

Where Marketo stops

Nurture programs exist to hand qualified leads to sales, and that handoff still has gaps.

Stuck on Marketo? Let's solve it →
Marketo REST API in four lines

Credentials: create an API-only user with its own role, then a Custom service in LaunchPoint tied to that user. View Details on the service shows the Client ID and Client Secret.

Admin Integration LaunchPoint

Endpoint: the REST endpoint and Identity URL are listed under Web Services. Both contain your Munchkin ID, so they look like https://123-ABC-456.mktorest.com/rest.

Admin Integration Web Services

Token: request /identity/oauth/token?grant_type=client_credentials with the ID and secret. The token lasts an hour and goes in an Authorization: Bearer header, not the URL.

Limits: 50,000 calls a day per subscription unless Adobe has raised yours, reset at midnight Central time. Also 100 calls per 20 seconds and no more than 10 at once.

Which Marketo API suits which job

The job Use Watch for
Sign-ups or account data from another system, sent to Marketo as they happen Lead upsert: POST /rest/v1/leads.json with createOrUpdate, up to 300 records a call The lookup field, email by default, decides what counts as the same person. Pick the wrong one and you create duplicates.
A big list or a nightly file of product usage Bulk import: POST /bulk/v1/leads.json with a CSV, up to a 10 MB body It runs as a job. Poll its status and read the failures file, or rejected rows disappear without anyone noticing.
Leads, activities or program members copied to a warehouse Bulk extract: create the job, enqueue it, poll status, then fetch the file Each job covers at most 31 days, two run at once, ten can queue, and exports share a 500 MB daily quota.
Recent activity for a known set of leads Activities: get a paging token from /rest/v1/activities/pagingtoken.json, then page forward Ask only for the activity types you need. Every page is a call against the daily total.
Something outside Marketo should happen the moment a lead qualifies A webhook called from a smart campaign flow step It's defined under Admin, but marketing ops decides when the campaign fires it, so agree who owns that campaign.

Marketo errors that arrive with an HTTP 200

Marketo's REST API usually answers 200 even when a call failed. The real result is the success flag and the errors array in the body.

Logging the HTTP status and nothing else

How you'll know: The integration log says every call worked, but records are missing in Marketo.

Fix: Check success on every response and log each error code with the record it belongs to. Upserts also return a status per record, so one bad row doesn't hide among good ones.

601 and 602: the token

How you'll know: Calls fail every hour or so, then recover after a restart.

Fix: 601 means the token is invalid and 602 means it expired. Watch expires_in and ask the Identity endpoint again before it runs out. Asking early just returns the same token with its remaining life.

606: more than 100 calls in 20 seconds

How you'll know: Bursts fail when several jobs start at the same moment.

Fix: Throttle on your side, and send up to 300 leads per upsert instead of one call per person.

607: the daily quota is gone

How you'll know: Everything stops in the afternoon and works again after midnight Central.

Fix: Move large reads to bulk extract, where one job returns a whole file instead of a call per page, and check usage under Web Services to see which integration spends the most.

615: too many requests in flight

How you'll know: Parallel workers fail at random under load.

Fix: Marketo processes 10 requests at a time per subscription. Cap your worker pool below that, leaving room for other tools on the same instance.

1029: the bulk queue or export quota

How you'll know: Enqueuing an extract fails, or exports stop for the rest of the day.

Fix: Ten jobs fit in the queue and exports share 500 MB a day. Split by date range and stagger jobs instead of firing them all at once.

Account context in, qualified leads out

Most Marketo API work runs in two directions. Inward, it's the context Marketo never had: whether the account is already a customer, an open support ticket, a renewal date, product usage. Pulled in nightly through bulk import or as it changes through lead upsert, that data can count toward a score or keep a customer out of a prospect nurture.

Outward, it's what should happen when a lead crosses a score threshold or finishes a program. Marketo changes a field. Turning that into a task for the right rep, a Slack alert or an update in a CRM other than Salesforce is integration work, done with a smart campaign webhook or a scheduled pass over recent activity.

n-frames builds both directions on the Marketo REST and bulk APIs, with the call budget planned up front so a busy campaign week doesn't stop the sync.

Questions people ask

Does Marketo have an API?

Yes. Marketo Engage has a REST API for leads, activities, programs, campaigns and assets, plus bulk import and bulk extract endpoints for large volumes. Integrations use it to pull Marketo data into other systems and push outside data into Marketo's scoring and segmentation.

Where do I find my Marketo Munchkin ID and REST endpoint?

In Marketo, go to Admin, then Integration, then Web Services. The REST API section shows the endpoint and Identity URL, and the Munchkin ID is the 123-ABC-456 style part at the start of both.

What is Marketo?

Adobe Marketo Engage is an enterprise marketing automation platform, now part of Adobe Experience Cloud. B2B marketing teams use it for lead scoring, nurture programs, email campaigns and landing pages, usually next to a separate CRM that sales works in. n-frames works on top of whatever Marketo instance a business already runs, building the integrations around it.

How much does Marketo cost?

Adobe doesn't publish list pricing for Marketo Engage. It's quoted per customer, based mainly on the size of your contact database and the package you choose, so Adobe's sales team has the current figure.

Is Marketo a CRM?

No. Marketo runs marketing automation, scoring and nurture. It doesn't manage deals or a sales pipeline, so most companies pair it with a CRM, often Salesforce or Microsoft Dynamics, and sync the two.

How does Marketo compare with HubSpot?

They're built for different teams. Marketo suits larger B2B marketing departments running long, multi-step nurture programs on top of a separate CRM. HubSpot bundles its own CRM with its marketing tools and tends to fit small and mid-size teams. The choice is yours to make on your sales process. Once it's made, n-frames builds the connections to the rest of your systems.

How do I get Marketo certified, or hire a Marketo consultant?

Certification and training are run by Adobe. A Marketo consultant usually handles setup, administration or campaign strategy. n-frames does neither: we build API integrations and automation on top of your instance, however and by whoever it was configured.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.