REST API

Last update: December 19, 2024

CREATED FOR:

  • Admin

Marketo exposes a REST API which allows for remote execution of many of the system’s capabilities. From creating programs to bulk lead import, there are many options which allow fine-grained control of a Marketo instance.

These APIs generally fall into two broad categories: Lead Database, and Asset. Lead Database APIs allow for retrieval of, and interaction with Marketo person records and associated object types, such as Opportunities and Companies. Asset APIs allow interaction with marketing collateral and workflow-related records.

NOTE
The SOAP API is being deprecated and will no longer be available after October 31st 2025. All new development should be done with the Marketo REST API, and existing services should be migrated by that date to avoid interruptions in service. If you have a service which uses the SOAP API, please consult the SOAP API Migration Guide for information on how to migrate.
  • Daily Quota: Subscriptions are allocated 50,000 API calls per day (which resets daily at 12:00AM CST). You can increase your daily quota through your account manager.
  • Rate Limit: API access per instance is limited to 100 calls per 20 seconds.
  • Concurrency Limit:  Maximum of ten concurrent API calls.

The size of standard calls is limited to a URI length of 8KB, and a body size of 1MB, though the body can be 10MB for our bulk APIs. If there is an error in with your call, the API will typically still return a status code of 200, but the JSON response will contain a “success” member with a value of false, and an array of errors in the “errors” member. More on errors here.

Getting Started

The following steps require admin privileges in your Marketo instance.

For your first call to Marketo, you retrieve a lead record. To begin working with Marketo, you must obtain API credentials for making authenticated calls to your instance. Log in to your instance and go to the Admin -> Users and Roles.

Admin Users and Roles

Click the Roles tab, and then New Role and assign at least the “Read-Only Lead” (or “Read- Only Person”) permission to the role in the Access API group. Be sure to give it a descriptive name and click Create.

New Role

Now, back to the Users tab and click Invite New User. Give your user a descriptive name that indicates that it is an API user, and an Email Address and click Next.

New User Info

Then, check the API Only option and award your user the API role that you created and click Next.

New User Permissions

To complete the user creation process, click Send.

New User Message

Next, go to the Admin menu and click LaunchPoint.

Launchpoint

Click the New menu and select New Service. Give your service a descriptive name and select Custom from the Service dropdown menu. Give it a description, then select your new user from the API Only User dropdown menu and click Create.

New Launchpoint Service

Click View Details for your new service to access the Client ID and Client Secret. For now you can click the Get Token button to generate an access token which is valid for one hour. Save the token in a note for now.

Get Token

Next, go to the  Admin menu, then to Web Services.

Web Services

Find the Endpoint in the REST API box and save in a note for now.

REST Endpoint

When making calls to REST API methods, an access token must be included in every call for the call to be successful. The access token must be sent as an HTTP header.

Authorization: Bearer cdf01657-110d-4155-99a7-f986b2ff13a0:int
IMPORTANT
Support for authentication using the access_token query parameter is being removed on June 30, 2025. If your project uses a query parameter to pass the access token, it should be updated to use the Authorization header as soon as possible. New development should use the Authorization header exclusively.

Open a new browser tab and enter the following, using the appropriate information to call Get Leads by Filter Type

<Your Endpoint URL>/rest/v1/leads.json?&filterType=email&filterValues=<Your Email Address>

If you don’t have a lead record with your email address in your database, substitute it for one that you know is there. Hit enter in your URL bar, and you should get back a JSON response resembling this:

{
    "requestId":"c493#1511ca2b184",
    "result":[
       {
           "id":1,
           "updatedAt":"2015-08-24T20:17:23Z",
           "lastName":"Elkington",
           "email":"developerfeedback@marketo.com",
           "createdAt":"2013-02-19T23:17:04Z",
           "firstName":"Kenneth"
        }
    ],
    "success":true
}

API Usage

Each of your API users is reported individually in the API usage report, so splitting up your web services by user allows you to easily account for the usage of each of your integrations. If the number of API calls to your instance are exceeding the limit and causing subsequent calls to fail, using this practice allows you to account for the volume from each of your services and let you evaluate how to resolve the issue. See your usage by going to Admin -> Integration > Web Services and clicking the number of calls in the past seven days.

Previous pageUser Profiles
Next pageAssets

Marketo Engage


Marketo Migration to the Adobe Admin Console - (Pre-Migration)

Experience Cloud Tech Sessions

Tuesday, Mar 4, 6:00 PM UTC

Join Adobe's Customer Experience and Identity Team to prepare for a smooth Marketo migration to the Adobe Admin Console. Learn key steps, best practices, and how to avoid roadblocks for a seamless transition.

Register

Marketo Migration to the Adobe Admin Console - (Post-Migration)

Experience Cloud Tech Sessions

Tuesday, Mar 11, 4:00 PM UTC

Migrated Marketo to the Adobe Admin Console? Join our webinar to master key features, best practices, and troubleshooting tips. Learn how to manage users,, settings, and more. register now!

Register

Connect with Experience League at Summit!

Get front-row access to top sessions, hands-on activities, and networking—wherever you are!

Learn more

Register now