How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Marketo Leads API

Leads Controller

Marketo Leads API is one of 45 APIs that Marketo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Leads. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, and authentication docs.

This API exposes 22 operations across 18 paths, and defines 51 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://localhost:8080/.

22 operations 18 paths 51 schemas 12 GET10 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{munchkinId}.mktorest.com/rest
Terms of Service
Resource Areas
1

Paths & Operations 22

Across 18 paths, the API surfaces 22 operations — 12 GET, 10 POST. Each is listed below with its method, path, parameters, and response codes.

Leads 22

Leads Controller

GET
/rest/v1/lead/{leadId}.json
Get Lead by Id
getLeadByIdUsingGET 2 params → 200
GET
/rest/v1/leads.json
Get Leads by Filter Type
getLeadsByFilterUsingGET 5 params → 200
POST
/rest/v1/leads.json
Sync Leads
syncLeadUsingPOST body → 200
POST
/rest/v1/leads/delete.json
Delete Leads
deleteLeadsUsingPOST 1 param body → 200
GET
/rest/v1/leads/describe.json
Describe Lead
describeUsingGET_2 → 200
GET
/rest/v1/leads/describe2.json
Describe Lead2
describeUsingGET_6 → 200
GET
/rest/v1/leads/schema/fields/{fieldApiName}.json
Get Lead Field by Name
getLeadFieldByNameUsingGET 1 param → 200
POST
/rest/v1/leads/schema/fields/{fieldApiName}.json
Update Lead Field
updateLeadFieldUsingPOST 1 param body → 200
GET
/rest/v1/leads/schema/fields.json
Get Lead Fields
getLeadFieldsUsingGET 2 params → 200
POST
/rest/v1/leads/schema/fields.json
Create Lead Fields
createLeadFieldUsingPOST body → 200
GET
/rest/v1/program/members/describe.json
Describe Program Member
describeProgramMemberUsingGET → 200
GET
/rest/v1/leads/partitions.json
Get Lead Partitions
getLeadPartitionsUsingGET → 200
POST
/rest/v1/leads/partitions.json
Update Lead Partition
updatePartitionsUsingPOST body → 200
GET
/rest/v1/leads/programs/{programId}.json
Get Leads by Program Id
getLeadsByProgramIdUsingGET 4 params → 200
POST
/rest/v1/leads/programs/{programId}/status.json
Change Lead Program Status
changeLeadProgramStatusUsingPOST 1 param body → 200
POST
/rest/v1/leads/push.json
Push Lead to Marketo
pushToMarketoUsingPOST body → 200
POST
/rest/v1/leads/submitForm.json
Submit Form
SubmitFormUsingPOST body → 200
POST
/rest/v1/leads/{leadId}/associate.json
Associate Lead
associateLeadUsingPOST 2 params → 200
POST
/rest/v1/leads/{leadId}/merge.json
Merge Leads
mergeLeadsUsingPOST 4 params → 200
GET
/rest/v1/leads/{leadId}/listMembership.json
Get Lists by Lead Id
getListMembershipUsingGET 3 params → 200
GET
/rest/v1/leads/{leadId}/programMembership.json
Get Programs by Lead Id
getProgramMembershipUsingGET 7 params → 200
GET
/rest/v1/leads/{leadId}/smartCampaignMembership.json
Get Smart Campaigns by Lead Id
getSmartCampaignMembershipUsingGET 5 params → 200

Schemas 51

The contract defines 51 schemas that model the data the API accepts and returns. The most detailed are LeadField (10 properties), Program (9 properties), ResponseOfLeadPartition (7 properties), ResponseOfProgramMemberAttributes (7 properties). Each schema is shown below with its type and property counts.

ResponseWithoutResult
object
5 properties 2 required
ResponseOfLeadAttribute
object
7 properties 5 required
Lead
object
Lead record. Always contains id, but may have any number of other fields, depending on the fields available in the target instance.
4 properties
ResponseOfLeadAttribute2
object
7 properties 5 required
LeadMapAttribute
object
2 properties 1 required
ResponseOfProgramMemberAttributes
object
7 properties 5 required
LeadAttribute
object
6 properties 3 required
LeadFormFields
object
Form fields. Always contains email, but may have any number of other fields depending on the fields available in the form.
1 property 1 required
ProgramMemberAttribute
object
2 properties 1 required
LeadAttribute2Fields
object
6 properties 5 required
CreateLeadFieldRequest
object
1 property 1 required
Reason
object
2 properties 2 required
ResponseOfSmartCampaigns
object
7 properties 5 required
Error
object
2 properties 2 required
FormResponse
object
Disposition of lead
3 properties 2 required
UpdateLeadPartition
object
2 properties 2 required
ResponseOfCreateLeadField
object
7 properties 5 required
ResponseOfPushLeadToMarketo
object
5 properties 5 required
LeadAttribute2
object
3 properties 3 required
ResponseOfLists
object
7 properties 5 required
DeleteLeadRequest
object
1 property 1 required
Program
object
9 properties 7 required
VisitorData
object
Page visit related data. Used to populate additional activity fields for filtering and triggering.
4 properties
ProgramMembership
object
7 properties 2 required
ResponseOfChangeLeadProgramStatusOutputData
object
7 properties 5 required
ResponseOfLead
object
7 properties 5 required
LeadPartition
object
3 properties 2 required
Warning
object
2 properties 2 required
ResponseOfSubmitForm
object
5 properties 5 required
CreateLeadField
object
Lead field record for create
7 properties 3 required
Form
object
Form field data. May have any number of fields depending on the fields available in the form.
3 properties 1 required
LeadFieldStatus
object
Lead field update status
2 properties 2 required
LeadInputData
object
Lead record containing only lead id
1 property 1 required
LeadAttribute2SearchableFields
array
List of searchable fields
ResponseOfPrograms
object
7 properties 5 required
List
object
3 properties 3 required
UpdateLeadFieldRequest
object
1 property 1 required
SyncLeadRequest
object
5 properties 1 required
PushLeadToMarketoRequest
object
7 properties
ChangeLeadProgramStatusRequest
object
2 properties 2 required
LeadField
object
Lead field record
10 properties 9 required
LeadLookupInputData
object
1 property 1 required
ResponseOfLeadField
object
7 properties 5 required
ResponseOfUpdateLeadField
object
7 properties 5 required
ChangeLeadProgramStatusOutputData
object
3 properties 2 required
SmartCampaign
object
3 properties 3 required
UpdateLeadPartitionRequest
object
1 property 1 required
UpdateLeadField
object
Lead field record for update
5 properties
ResponseOfLeadPartition
object
7 properties 5 required
SubmitFormRequest
object
3 properties 2 required
PushLead
object
Lead record. Always contains id, but may have any number of other fields, depending on the fields available in the target instance.
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

marketo-leads-api-openapi.yml Raw ↑

Other APIs Marketo publishes across the network.

Marketo Campaigns API
Marketo Channels API
Marketo Email Templates API
Marketo Emails API
Marketo File Contents API
Marketo Files API
Marketo Folders API
Marketo Form Fields API
Marketo Forms API
Marketo Landing Page Content API
Marketo Landing Page Redirect Rules API
Marketo Landing Page Templates API
Where this information came from

This is an independent, third-party profile of Marketo Leads API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.