Issue Issue Description API Only user is not appearing when creating a service in [Admin > LaunchPoint]
Solution Issue Resolution It is highly likely that the reason why the API user was not appearing because it did not have "API Only" ticked. This can be checked in [Admin > Users & Roles > User > Edit User]. However, this cannot be modified once the API user is created, so in order for the API user to appear in LaunchPoint, "API Only" must be ticked when the API user is created.
Who This Solution Applies To Admin users
Issue When making API calls, Marketo reports the daily API limit has been reached but does not show when the limit resets.
Solution When Marketo shows the daily API limit has been reached, it will reset itself that night at midnight central time, and then will allow for the API calls to resume. These are the reset times according to US time zones.
10:00 PM Pacific 11:00 PM Mountain 12:00 AM Central 01:00 AM Eastern
Issue Do webhook calls contribute to the daily API limit/quota visible in [Admin > Integration > Web Services > API Call Information] ?
Solution No, webhook calls are not counted as part of the daily API limit. Webhooks do not have any execution limits.
Issue REST API call, Get Lead Activities , is returning 603 error
Solution Error 603 refers to 'access denied' where authentication is successful but the user doesn’t have sufficient permission to call this API. Additional permissions may need to be assigned to the user role. http://developers.marketo.com/rest-api/error-codes/
Go to Admin > Users and Roles Select API User and identify what role it is assigned to (e.g. API role) Go to Roles and check the permissions assigned to the API role Check to see if the API role has 'Read-Only Activity' or 'Read-Write Activity' permission
In order to make a Get Lead Activities REST API call with the API user, the API role of the user must be modified to have permissions to 'Read-Only Activity' or 'Read-Write Activity'. If you use Workspaces and Partitions, make sure the API User has the necessary access to the workspaces/partitions being called.
Issue The Get Lead Activities REST API is not returning any activities even though t he lead referenced definitely has multiple activities of the type being called.
Solution The Get Lead Activity REST API are reliant on timestamps for their nextPageToken. Each Get Lead Activity call will go through 300 activities of ALL types from the timestamp placed on the nextPageToken. This is supported by the article http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#/Activities/getLeadActivitiesUsingGET
"By default, the endpoints mentioned in this section will return 300 activity items at a time. If the moreResult attribute is true, this means that more results are available. Continue to call the endpoint until the moreResult attribute returns false, which means that there are no more results available."
Based on that, the reason why the API call does not return any activities is that it does not find any activities of type 46 in the 300 activities it checks from the timestamp placed on the nextPageToken
So when making a Get Lead Activity call for a specific activity type, ensure that nextPageToken is as close as to the timestamp of the specific activities
Issue After you have created an API User with the correct access for making REST API calls to your Marketo instance, you still receive a response with Error 603 Access Denied even when making API calls using an up-to-date access token that you manually created.
Solution Issue Resolution The most likely resolution is that you have Web Service IP Restrictions enabled on your instance.
Go to Admin > Web Services Click the Edit button next to the IP Restrictions box
If IP Restrictions are turned on and there are no IP addresses listed, all calls to the Marketo REST API endpoint will fail. If IP Restrictions are turned on and the IP making the API call is not listed, add it to the list and save. You can also set up wildcard IP addresses here to cover a range of IP addresses.
You can learn more about whitelisting IP addresses in Marketo in the article " Create a Whitelist for IP-Based API Access ".
If you have confirmed that IP Restrictions are NOT enabled and have also gone through our API User documentation to ensure the API User is set up correctly but your calls are still failing as Access Denied, please create a support case.
Issue Does the email address assigned to the API user need to be an email address maintained by an actual person?
Solution The email address assigned to an API user does not need to be an existing email address or an actual person.
It is used as an identifier for the API user. Generally, customers name the API user according to the integration the API user is being used for (e.g. email@example.com ). This is useful for tracking where API calls are coming from when there are multiple integrations configured with Marketo via the API
Issue Calls made to the REST API return response code 611 "System Error".
Solution Submit a Customer Support ticket with the following information
The full body of the REST API call including the endpoint being called The full body of the REST API response The date and time that the call was made
Customer Support will work to diagnose the root cause of the error and the reason a more identifiable error code is not being returned instead.
Issue How to use the REST API to check for deleted leads.
Solution You would need to use the specific endpoint : http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Activities/getDeletedLead s
This will pull a list of leads deleted within a specific timeframe. Deletions older than 30 days may be pruned.
Issue Issue Description Occasionally Bulk Import API calls will return a blank response.
Solution Issue Resolution
You can add the following header:
to your API calls and it will fix this issue. Please note that adding this header on the client side will cause cURL to send data in chunks.
Issue You want to view your current usage of the Marketo API.
Solution Current usage of both REST and SOAP API can be found by following these steps:
Go to Admin > Web Services Look at the API Call Information section.
In the API Call Information section, you will see a line that says "Requests in the Last 7 Days:". The number next to that is the number of calls made to this instance in that time frame.
The number is also a hyper-link that will allow you to break this down by API user. Each individual REST user will be its own row, while the SOAP requests will be in one line, using the given SOAP User ID within the SOAP API section just below.
Issue You changed the Label name of the field and want the API name to match.
Solution I Outside applications rely on API names and changes to these names can make your Marketo instance unstable. For this reason, it is not possible to change API names of fields. Instead, we suggest creating new field with the correct API name.
Issue Clearing cache and cookies in your browser will fix a number of different problems related to page display, browser errors, and login issues.
Solution Here are links to the support articles on how to clear cache and cookies for the most commonly used browsers.
Clear cache and cookies - Computer - Google Account Help
How to clear the Firefox cache | Firefox Help
Safari for Mac: Manage cookies and website data using Safari
Microsoft Edge, browsing data, and privacy – Microsoft privacy
Issue When using the GET Activities API with a specific list Id in the parameter, the response will get all the specified activities from other assets as well.
This is the endpoint for this article.
Solution Instead of using list Id (listId) as a parameter, change that to asset Ids (assetId) in the API call.
The Asset ID (assetId) is the Id of the primary asset for an activity.
Then, the response will narrow down the activities associated to the primary asset by looking up the Id during the call.
Issue Issue Description
A REST API call on the Company API or Opportunity API fails with the error "1018: CRM Enabled -- The action could not be carried out, because the instance has a native CRM integration enabled."
Solution Issue Resolution
Per the documentation on developers.marketo.com, the Company and Opportunity APIs are only available on instances that are not currently synced with a CRM such as Salesforce or MS Dynamics. If your instance is synced to a CRM, you will need to update Company and Opportunity information through the CRM rather than the API.
Documentation for these APIs can be found here:
Who This Solution Applies To
Marketo instances with a CRM sync
Marketo Support's Mission is:
"To provide fast and friendly world-class support through creative, flexible solutions to empower Marketo Automation Software success."
Areas of Responsibility:
Technical Support Engineers (TSEs) are your initial point of contact for any questions or concerns. TSEs are responsible for troubleshoot issues within your Marketo instance. Common areas within a Marketo instances which TSEs will assist with are:
My Marketo Marketing Activities Design Studio Lead Database Analytics Revenue Explorer (RCA/RCE) Calendar Deliverability Tools Search Engine Optimization (SEO) Web Personalization (RTP) Admin Community
Simple Munchkin Code Asynchronous Munchkin Code Asynchronous jQuery Munchkin Code SOAP API REST API
Our technical support engineers are here to assist you and our support commitment to our customers is to always work towards providing an above and beyond support experience.
Note: Our team is not against looking at custom code and, based on the subject matter expertise, our TSEs might be able to offer suggestions and recommendations, but we do want to make it clear that they are not responsible for fixing or updating any custom code that has been implemented.
Our Technical Support Engineers are bound to responding to your cases and issues within the Service Level Agreements from your account's level of support services. We track response milestones to ensure that your cases are being handled in a timely manner as dictated by our agreed to Service Level Targets.
Issue Description You need to revert a data value change for a field on multiple leads. Issue Resolution There is no way through the UI to "undo" a data value change (unless it was a boolean field, in which case there are only two possible values.) You can certainly use a Smart List to identify whose values have changed, but there no way to go back to the old value (unless it's stored elsewhere in another field or through another data store, along with the API). However, you can use the API to extract the data value change activity from the activity log, which would include the old and new values, extract the original values, then use the API to rewrite the old values back to the lead record. http://developers.marketo.com/rest-api/endpoint-reference/lead-database-endpoint-reference/#!/Activities/getLeadChangesU… Is this article helpful ? YesNo
Issue Would a requested campaign via API show in activity log if filtered? Ex: You request a campaign, and the lead does not qualify due to a filter. Will the activity log show the request occurring?
Solution Yes, the request will show no matter if the lead runs through the flow or not. The request campaign action will be recorded, but the lead will not go through the flow steps if they do not meet the requested campaign's Smart List requirements.
Issue You receive a Web Services Error 612 on a REST API call.
Solution The 612 error code denotes that there was an invalid Content Type in the REST API call. If you see this error, add a content type header specifying JSON format to your request. For example, try using "content type: application/json".
Since this error is in the formatting of the REST API call that is being made to the Marketo instance, we recommend working with a developer to update the API call to resolve the error message. Here is a Link to StackOverflow that helps to discuss this kind of error message further: ( http://stackoverflow.com/questions/28181325/why-invalid-content-type ).
Issue Description When a lead is created through an API call, the Reason and Source attributes say "Web Service API" with no further detail. Issue Resolution As described in the doc here, https://docs.marketo.com/display/DOCS/Understanding+System+Managed+Fields, "Source" and "Reason" fields are managed by Marketo: 1. Web Service API for Original Source Type means Person was discovered by a web service API. 2. For Registration Source Type, it states that Person was created via SOAP/REST API When a lead is created via API, no additional "Source" or "Reason" is provided to Marketo. A possible workaround is to create a custom field and populate it as needed through the API.