Knowledgebase

Sort by:
Issue When I go to the Support area of Nation, I do not have full access to all the areas and tools.   Solution Our system is specific about how you need to access the Support Portal before we can authorize you to use it. The proper steps to take for us to authorize, and for you to submit cases, are as follows:   Log into your instance Click the Community tile (step 1 image) Click Support in the top banner (step 2 image) Click Submit a Case option (step 3 image) Choose from top options depending on what you need to do (step 4 image) Create a case, Manage authorized contacts, edit your Info   Simply going straight to the nation.marketo.com will not have the desired result. You must access the Support Portal from your instance by using these steps so that our system recognizes you properly. If this is your first time following these steps, your view of Step 3 will be different- not to worry, as that will be updated for you manually. Step 1 Step 2   Step 3 Step 4   If you experience issues, please email marketocares@marketo.com
View full article
Issue Users for your Marketo instance are unable to log into the instance. Solution Check your landing page URLs and email links. If these are also unavailable, your Marketo instance may have been shut off. Marketo Support can confirm whether your instance has been deactivated, but are not able to reactivate it.  In this situation , please contact your Marketo Account Representative to discuss the status of the instance and regaining access.        
View full article
Issue Issue Description You want to use the /rest/v1/leads/delete.json API endpoint to delete multiple lead from your instance in one call.     Solution Issue Resolution You can include up to 300 lead IDs in the body of the call and delete them at once. To delete more leads than that you will need to make multiple calls with batches of 300 leads or less.   Who This Solution Applies To Customers using the REST API
View full article
Issue Issue Description When a lead is created through an API call, the Reason and Source attributes say "Web Service API" with no further detail.       Solution 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: Web Service API for Original Source Type means Person was discovered by a web service API. 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.    
View full article
Issue Issue Description API user making bulk extract calls is encountering the error "1029, Export daily quota exceeded" but under Admin>Web services> Request in the 7 days shows that you have not reached the "Daily Request limit".     Solution Issue Resolution The "Daily Request Limit" that can be found under Admin>Web Services>API call information is different from the limit that is in place for the bulk extract limit. The API limit is a on the number of calls that can be made, while the bulk extract limit is a limit on the amount of data that can be exported used based on the file size of the bulk extract job. If you notice this behavior, please reach out to your CSM for more information about increasing the Bulk Extract limit.    
View full article
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.    Reference: https://docs.marketo.com/display/public/DOCS/Create+an+API+Only+User    Who This Solution Applies To Admin users
View full article
Issue Issue Description Persons do not trigger Smart Campaigns as expected when using the REST API 'Push Leads to Marketo' endpoint.     Solution Issue Resolution Marketo utilizes a special trigger for persons pushed to Marketo using REST API. The 'Person is Pushed to Marketo' trigger will qualify persons upserted by the 'Push to Marketo' endpoint.    
View full article
Issue You have exported the fields under the Field Management section as mentioned in this document to view the API name of the Marketo fields  You see there are few fields missing and would like to know their API names. Solution Here's a list of the Marketo Standard fields that are available via API. If there are fields which are not available in the list export, it means they likely do not have an API name or not accessible through API calls.    
View full article
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.
View full article
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.
View full article
Issue You make a REST API call and receive an error code 1006 "Field '****' not found." Solution This error lets you know you are referencing a field by the wrong API name. The ****  will let you know which field you are referencing incorrectly. To resolve this Export a list of API names for the fields in your instance. Locate the desired field and its API name in the list Update your REST API call with the correct API field name   Who This Solution Applies To Customers using REST API    
View full article
Issue What to do if you've exceeded your daily limit of API calls.     Solution If you go Admin > Web Services in Marketo, you will see a section called API Call Information. The number next to "Enforced Daily Request Limit" lets you know how many API calls you can make daily. If you need this number to be increased, the best option is to contact your Custom Success Manager; they can help you start the process of increasing your limit.    
View full article
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. 
View full article
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      
View full article
Issue You want to use a non-standard character as a value (or part of a value) in an API call (e.g. é), but when you put it in, the call does not work (either failing with an error or not posting the expected character).     Solution Encode the extended characters using ASCII URL encoding for UTF-8. There are sites that will perform this encoding for you, here is one: https://www.w3schools.com/tags/ref_urlencode.asp . For example: making this call, " https:// <munchkinid>.mktorest.com/rest/asset/v1/folder/{folder id}/tokens.json?access_token=<accesstoken>&name=TestName&value=Hello+%C3%A9marketo&type=text&folderType=Folder " will create a token called "TestName" with a value of "Hello émarketo"      
View full article
Issue You are pulling the folder ID from the UI, but it is not working in your API calls.   Solution Retrieve the Folder ID from an API query call (GET Folder byName), and use the ID given from that call to make additional calls.    
View full article
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.  
View full article
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 ).      
View full article
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.    
View full article
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.  
View full article