Error Codes & Messages

Error Code: 1

<rsp stat="fail" version="1.0">
    <err code="1">Invalid API key or user key</err>
</rsp>

Problem: Either the user and/or API keys are incorrect, or the API key has expired.

Solution: Check the user and API keys in the request. If the user key was entered accurately, then submit a request for a new API key.

Error Code: 2

<rsp stat="fail" version="1.0">
    <err code="2">Invalid action</err>
</rsp>

Problem: The requested operation was not recognized by the API.

Solution: Verify that the requested operation is valid for the target object type. If that operation is allowed, then check for misspellings and other typos.

Error Code: 3

<rsp stat="fail" version="1.0">
    <err code="3">Invalid prospect ID</err>
</rsp>

Problem: Pardot could not find a match for the provided prospect ID.

Solution: Verify that the prospect ID is accurate.

Error Code: 4

<rsp stat="fail" version="1.0">
    <err code="4">Invalid prospect email address</err>
</rsp>

Problem: Pardot could not find a prospect with the provided email address (for read/update/delete), or the prospect email address is too long (> 255 characters) or has invalid syntax (does not match /^[^ @]{1,64}@[^ @]{1,255}\.[^ @]{2,13}$/) (for create/upsert).

Solution: If running create/upsert, verify the email address is valid. If running read/update/delete, verify the a prospect with this email address exists in your Pardot account.

Error Code: 5

<rsp stat="fail" version="1.0">
    <err code="5">Invalid query parameters</err>
</rsp>

Problem: Pardot did not recognize any of the provided search parameters.

Solution: Check parameter spellings. Also, ensure that the specified search parameter is supported by the API. See Supported Search Criteria in Querying Prospects for more details.

Error Code: 6

<rsp stat="fail" version="1.0">
    <err code="6">Invalid time frame</err>
</rsp>

Problem: The value of the timeframe search parameter was not recognized.

Solution: Check for misspellings in the timeframe value. Also, verify that the provided value is supported by the API. See Supported Search Criteria in Prospects for supported timeframe values.

Error Code: 7

<rsp stat="fail" version="1.0">
    <err code="7">Invalid timestamp</err>
</rsp>

Problem: Pardot could not decipher a specified timestamp.

Solution: Verify that the timestamp adheres to GNU standards for date and time input. See GNU Date Input Format & Syntax for more information. Also, ensure all characters in the timestamp are URL safe. See Supported Search Criteria in Prospects for supported values.

Error Code: 8

<rsp stat="fail" version="1.0">
    <err code="8">Invalid time range</err>
</rsp>

Problem: The provided start timestamp is later than the end timestamp.

Solution: Swap the values of the timestamps.

Error Code: 9

<rsp stat="fail" version="1.0">
    <err code="9">A prospect with the specified email address already exists</err>
</rsp>

Problem: The provided email address is already assigned to a prospect within Pardot. This can occur if a create request with the same email address is submitted more than once.

Solution: Check the existing prospect record to see if data can be merged through an update request.

Error Code: 10

<rsp stat="fail" version="1.0">
    <err code="10">Invalid user ID</err>
</rsp>

Problem: The provided user ID does not exist in Pardot.

Solution: Verify that the user ID was typed correctly and matches the intended user in Pardot.

Error Code: 11

<rsp stat="fail" version="1.0">
    <err code="11">Invalid user email address</err>
</rsp>

Problem: The provided user email address could not be found in Pardot.

Solution: Verify that the provided email address belongs to a registered Pardot user and that it was typed correctly.

Error Code: 12

<rsp stat="fail" version="1.0">
    <err code="12">Invalid group ID</err>
</rsp>

Problem: The provided group ID does not exist in Pardot.

Solution: Verify that the group ID was typed correctly and matches the intended group in Pardot.

Error Code: 13

<rsp stat="fail" version="1.0">
    <err code="13">One or more required parameters are missing</err>
</rsp>

Problem: One or more of the required parameters for this type of request are missing.

Solution: Verify that all of the required parameters have been provided. Check that all parameter names were spelled accurately and as specified in Object Field References. Ensure the proper URL punctuation was used, including ? before parameters and & between parameters.

Error Code: 14

<rsp stat="fail" version="1.0">
    <err code="14">Non-existent prospect ID; No email address provided</err>
</rsp>

Problem: The ID provided for the upsert was not valid, and no email address was provided for a new prospect to be created.

Solution: Verify the provided ID. If creating a new prospect was intended, ensure that an email address was provided.

Error Code: 15

<rsp stat="fail" version="1.0">
    <err code="15">Login failed</err>
</rsp>

Problem: The provided email address, password, or user key is invalid.

Solution: Check the provided credentials for typos. Also, ensure that the specified user account has at least "Marketing" access privileges.

Error Code: 16

<rsp stat="fail" version="1.0">
    <err code="16">Invalid ID</err>
</rsp>

Problem: The provided ID is not valid.

Solution: Ensure that only valid integer values were provided.

Error Code: 17

<rsp stat="fail" version="1.0">
    <err code="17">Invalid ID range</err>
</rsp>

Problem: The provided ID range is not valid.

Solution: Swap the values of the specified IDs.

Error Code: 18

<rsp stat="fail" version="1.0">
    <err code="18">Invalid value for profile criteria matching status</err>
</rsp>

Problem: The provided value for a profile criteria's matching status was not recognized.

Solution: Ensure that only the values match, nomatch, or unknown are being used.

Error Code: 19

<rsp stat="fail" version="1.0">
    <err code="19">Invalid value specified for sort_by</err>
</rsp>

Problem: The provided value for the sort_by is not a supported sorting order.

Solution: Check that the specified sorting values are listed in Using (Object Type): Supported Sorting Options section for the target object.

Error Code: 20

<rsp stat="fail" version="1.0">
    <err code="20">Invalid value specified for sort_order</err>
</rsp>

Problem: The provided value for the sort_order is not a supported sorting order.

Solution: Ensure that only the values ascending or descending are being used.

Error Code: 21

<rsp stat="fail" version="1.0">
    <err code="21">Invalid value specified for offset</err>
</rsp>

Problem: The provided value for offset could not be interpreted as an integer.

Solution: Check for typos that may prevent the value from being interpreted.

Error Code: 22

<rsp stat="fail" version="1.0">
    <err code="22">Unsupported feature in this version of the API</err>
</rsp>

Problem: The feature requested by the API call is not implemented in this version of the API.

Solution: Update the request to use the necessary API version.

Error Code: 23

<rsp stat="fail" version="1.0">
    <err code="23">Invalid value specified for limit</err>
</rsp>

Problem: The provided value for limit is invalid.

Solution: Ensure that the provided value is an integer and is no larger than 200.

Error Code: 24

<rsp stat="fail" version="1.0">
    <err code="24">Invalid visitor ID</err>
</rsp>

Problem: The provided visitor ID does not exist in Pardot.

Solution: Verify that the visitor ID was typed correctly and matches the intended visitor in Pardot.

Error Code: 25

<rsp stat="fail" version="1.0">
    <err code="25">Parameter is_starred must be true or false</err>
</rsp>

Problem: The value specified for is_starred could not be interpreted as a boolean.

Solution: Verify that only the values true or false were specified.

Error Code: 26

<rsp stat="fail" version="1.0">
    <err code="26">Parameter assigned must be true or false</err>
</rsp>

Problem: The value specified for assigned could not be interpreted as a boolean.

Solution: Verify that only the values true or false were specified.

Error Code: 27

<rsp stat="fail" version="1.0">
    <err code="27">Parameter deleted must be true or false</err>
</rsp>

Problem: The value specified for deleted could not be interpreted as a boolean.

Solution: Verify that only the values true or false were specified.

Error Code: 28

<rsp stat="fail" version="1.0">
    <err code="28">Parameter new must be true or false</err>
</rsp>

Problem: The value specified for new could not be interpreted as a boolean.

Solution: Verify that only the values true or false were specified.

Error Code: 29

<rsp stat="fail" version="1.0">
    <err code="29">Invalid value specified for score</err>
</rsp>

Problem: The value specified for score could not be interpreted as an integer.

Solution: Check for typos that may prevent the value from being interpreted correctly.

Error Code: 30

<rsp stat="fail" version="1.0">
    <err code="30">Invalid score range specified</err>
</rsp>

Problem: The provided score range is not valid.

Solution: Swap the values of the specified scores.

Error Code: 31

<rsp stat="fail" version="1.0">
    <err code="31">Invalid combination of parameters for score</err>
</rsp>

Problem: A conflicting set of query criteria for the prospect's score has been specified.

Solution: Make sure that score_equal_to is not being used in combination with score_greater_than or score_less_than.

Error Code: 32

<rsp stat="fail" version="1.0">
    <err code="32">Invalid value specified for grade</err>
</rsp>

Problem: The value specified for grade is not one of the allowed options.

Solution: Check for typos that may prevent grade from being interpreted correctly. See Supported Search Criteria in Prospects for supported values. Also, ensure that the specified grades are URL-encoded.

Error Code: 33

<rsp stat="fail" version="1.0">
    <err code="33">Invalid grade range specified</err>
</rsp>

Problem: The provided grade range is not valid.

Solution: Swap the values of the specified grades.

Error Code: 34

<rsp stat="fail" version="1.0">
    <err code="34">Invalid combination of parameters for grade</err>
</rsp>

Problem: A conflicting set of query criteria for the grade has been specified.

Solution: Make sure that grade_equal_to is not being used in combination with grade_greater_than or grade_less_than.

Error Code: 35

<rsp stat="fail" version="1.0">
    <err code="35">Invalid opportunity ID</err>
</rsp>

Problem: Pardot could not find a match for the provided opportunity ID.

Solution: Verify that the opportunity ID is accurate.

Error Code: 36

<rsp stat="fail" version="1.0">
    <err code="36">One or more required parameter values are missing</err>
</rsp>

Problem: Some of the parameters necessary to complete the specified API request were omitted from the request.

Solution: Ensure that all required parameters have been included. In addition, check from typos in the parameter names. Also check that the request has been properly formatted.

Error Code: 37

<rsp stat="fail" version="1.0">
    <err code="37">A SalesForce connector was detected</err>
</rsp>

Problem: Your Pardot account has a SalesForce connector. When a SalesForce connector is present, opportunities cannot be modified by Pardot.

Solution: (NOT RECOMMENDED) Deleting the SalesForce connector will allow for opportunity modification to be done through the API. However, doing so will disable synchronization with SalesForce. If a SalesForce connector is present, modifications to opportunities must be done within SalesForce.

Error Code: 38

<rsp stat="fail" version="1.0">
    <err code="38">Invalid campaign ID</err>
</rsp>

Problem: Pardot could not find a match for the provided campaign ID.

Solution: Verify that the campaign ID is accurate.

Error Code: 39

<rsp stat="fail" version="1.0">
    <err code="39">Invalid profile ID</err>
</rsp>

Problem: Pardot could not find a match for the provided profile ID.

Solution: Verify that the profile ID is accurate.

Error Code: 40

<rsp stat="fail" version="1.0">
    <err code="40">Invalid opportunity probability</err>
</rsp>

Problem: The value specified for probability is not valid.

Solution: Ensure that the specified value is a number between 0 and 100 inclusive.

Error Code: 41

<rsp stat="fail" version="1.0">
    <err code="41">Invalid probability range specified</err>
</rsp>

Problem: The specified probability range is not valid.

Solution: Ensure that the specified values are numbers between 0 and 100 inclusive. It may also be necessary to swap the values of the specified probabilities.

Error Code: 42

<rsp stat="fail" version="1.0">
    <err code="42">Invalid opportunity value</err>
</rsp>

Problem: The value specified for value is not valid.

Solution: Ensure that the specified value is a non-negative number.

Error Code: 43

<rsp stat="fail" version="1.0">
    <err code="43">Invalid opportunity value range specified</err>
</rsp>

Problem: The specified value range is not valid.

Solution: Ensure that the specified values are non-negative numbers. It may also be necessary to swap the specified values.

Error Code: 44

<rsp stat="fail" version="1.0">
    <err code="44">The provided prospect_id and prospect_email parameters do not match</err>
</rsp>

Problem: The specified prospect_email and prospect_id parameters do not correspond to the same prospect.

Solution: Ensure that the specified email address and the ID both correspond to the desired prospect. (Note: Typically, only one of these parameters is required. Consider omitting one of them.)

Error Code: 45

<rsp stat="fail" version="1.0">
    <err code="45">The provided user_id and user_email parameters do not match</err>
</rsp>

Problem: The specified user_id and user_email parameters do not correspond to the same user.

Solution: Ensure that the specified email address and the ID both correspond to the desired user. (Note: Typically, only one of these parameters is required. Consider omitting one of them.)

Error Code: 46

<rsp stat="fail" version="1.0">
    <err code="46">This API user lacks sufficient permissions for the requested operation</err>
</rsp>

Problem: The currently authenticated API user has does not have the necessary permissions to perform the requested operation.

Solution: Some API operations are only available to users with Administrative permissions. If the requested operation has such a requirement, re-authenticate as an administrative user and resubmit the request. See the Authentication section for more information.

Error Code: 47

<rsp stat="fail" version="1.0">
    <err code="47">Multiple assignment targets were specified</err>
</rsp>

Problem: More than one object was specified as a target for this ASSIGN request. For example, both a group and user may have been specified as targets of a prospect assignment.

Solution: Ensure that only one target is specified when submitting an ASSIGN request.

Error Code: 48

<rsp stat="fail" version="1.0">
    <err code="48">Invalid visit ID</err>
</rsp>

Problem: The provided visit ID does not exist in Pardot.

Solution: Verify that the visit ID was typed correctly and matches the intended visit in Pardot.

Error Code: 50

<rsp stat="fail" version="1.0">
    <err code="50">Invalid boolean</err>
</rsp>

Problem: Need a valid boolean value, like true.

Solution: Make sure to use lowercase.

Error Code: 51

<rsp stat="fail" version="1.0">
    <err code="51">Invalid parameter</err>
</rsp>

Problem: Object type is invalid.

Solution: Change the object type to one of the allowed types.

Error Code: 53

<rsp stat="fail" version="1.0">
    <err code="53">Client IP address/location must be activated before accessing API</err>
</rsp>

Problem: IP is not whitelisted.

Solution: Whitelist IP address to access the API

Error Code: 54

<rsp stat="fail" version="1.0">
    <err code="54">Email address is already in use</err>
</rsp>

Problem: Email address is already being used by other prospect

Solution: Use different email address.

Error Code: 55

<rsp stat="fail" version="1.0">
    <err code="55">Invalid list ID</err>
</rsp>

Problem: You either did not specify the list ID, or that List ID doesn't exist.

Solution: Specify an ID, or check to make sure using the correct ID.

Error Code: 56

<rsp stat="fail" version="1.0">
    <err code="56">Invalid number entered for field</err>
</rsp>

Problem: The value entered doesn't match the field's type of Number.

Solution: Verify that there are no characters in the value.

Error Code: 57

<rsp stat="fail" version="1.0">
    <err code="57">Invalid date entered for field</err>
</rsp>

Problem: The value entered doesn't match the field's type of Date, it is an invalid format.

Solution: Verify that the timestamp adheres to GNU standards for date and time input. See GNU Date Input Format & Syntax for more information. Also, ensure all characters in the timestamp are URL safe. See Supported Search Criteria in Prospects for supported values.

Error Code: 58

<rsp stat="fail" version="1.0">
    <err code="58">That prospect is already a memeber of that list. Update the membership instead.</err>
</rsp>

Problem: The prospect is a member of the list already.

Solution: Update the membership.

Error Code: 59

<rsp stat="fail" version="1.0">
    <err code="59">A CRM connector was detected/err>
</rsp>

Problem: Your Pardot account has a CRM connector. When a CRM connector is present, opportunities cannot be modified by Pardot.

Solution: (NOT RECOMMENDED) Deleting the CRM connector will allow for opportunity modification to be done through the API. However, doing so will disable synchronization with your CRM. If a CRM connector is present, modifications to opportunities must be done within your CRM.

Error Code: 60

<rsp stat="fail" version="1.0">
    <err code="60">Invalid HTTP request method</err>
</rsp>

Problem: Cannot delete with this method.

Solution: Use methods POST or DELETE.

Error Code: 61

<rsp stat="fail" version="1.0">
    <err code="61">Invalid prospect account id</err>
</rsp>

Problem: Prospect Account ID was incorrect or doesn't exist.

Solution: Verify that the prospect account ID was typed correctly and matches the intended Propsect Account in Pardot.

Error Code: 62

<rsp stat="fail" version="1.0">
    <err code="62">Conflicting Update</err>
</rsp>

Problem: Another update is occurring at the same time.

Solution: Wait before performing this action.

Error Code: 63

<rsp stat="fail" version="1.0">
    <err code="63">Too many IDs specified</err>
</rsp>

Problem: There is a limit on how many IDs you can specify for this query

Solution: Lower the amount of IDs you are querying for.

Error Code: 64

<rsp stat="fail" version="1.0">
    <err code="64">Email content missing required variables</err>
</rsp>

Problem: The content of the email is missing required variables

Solution: Ensure that all required variables, such as unsubscribe link, are present

Error Code: 65

<rsp stat="fail" version="1.0">
    <err code="65">Invalide email format</err>
</rsp>

Problem: Doesn't have all required fields present or are not in proper format, such as from address

Solution: Ensure all fields are present, populated, and in proper format.

Error Code: 66

<rsp stat="fail" version="1.0">
    <err code="66">You have exceeded your concurrent request limit.  Please wait, before trying again</err>
</rsp>

Problem: Have made too many requests in this time period.

Solution: Wait a little before making more requests.

Error Code: 67

<rsp stat="fail" version="1.0">
    <err code="67">You have reached or exceeded the limit of how many of this type of object you may have.</err>
</rsp>

Problem: You have too many of this object type to create more

Solution: Delete some of the object if you need to make more

Error Code: 68

<rsp stat="fail" version="1.0">
    <err code="68">Template with this id does not exist.</err>
</rsp>

Problem: The template you are trying to access does not exist

Solution: Make sure you are using the correct template ID or create a new one to use.

Error Code: 70

<rsp stat="fail" version="1.0">
    <err code="70">Batch processing is limited to 50 prospects at once.</err>
</rsp>

Problem: You are requesting to batch more prospects in an operation than we allow

Solution: Ensure that your batch request has 50 or fewer prospects

Error Code: 71

<rsp stat="fail" version="1.0">
    <err code="71">Input needs to be valid JSON or XML</err>
</rsp>

Problem: You've inputted invalid JSON or XML

Solution: Ensure that your request is properly formatted

Error Code: 72

<rsp stat="fail" version="1.0">
    <err code="72">JSON has been corrupted, hash does not match</err>
</rsp>

Problem: The encoded JSON has been corrupted at some point

Solution: Please ensure that you are sending the correct information

Error Code: 73

<rsp stat="fail" version="1.0">
    <err code="73">Currently there is not an Email Plug-in Campaign associated to successfully track this email. Please contact your Pardot administrator to ensure there is a proper campaign associated with the Account Settings in Pardot.</err>
</rsp>

Problem: Currently there is not an Email Plug-in Campaign associated to successfully track this email

Solution: Please contact your Pardot administrator to ensure there is a proper campaign associated with the Account Settings in Pardot

Error Code: 74

<rsp stat="fail" version="1.0">
    <err code="74">The email client is not supported by the plugin API</err>
</rsp>

Problem: The email client used is not supported by this API

Solution: Please use an appropriate email client

Error Code: 75

<rsp stat="fail" version="1.0">
    <err code="75">There was an error processing the request for the account variable tags</err>
</rsp>

Problem: There was an error processing the request for the account variable tags

Solution: Please review the variable tags, and resubmit the request

Error Code: 76

<rsp stat="fail" version="1.0">
    <err code="76">API access was disabled</err>
</rsp>

Problem: API access for your account has been disabled

Solution: Contact customer support

Error Code: 77

<rsp stat="fail" version="1.0">
    <err code="77">Invalid prospect fid</err>
</rsp>

Problem: The provided Prospect FID was invalid

Solution: Please provide a valid Prospect FID

Error Code: 79

<rsp stat="fail" version="1.0">
    <err code="79">Invalid CRM_FID</err>
</rsp>

Problem: The CRM FID provided is invalid

Solution: Please provide a valid CRM FID that can be accessed by your account, or is already attached to a prospect

Error Code: 80

<rsp stat="fail" version="1.0">
    <err code="80">Invalid CRM_TYPE</err>
</rsp>

Problem: The CRM type provided or used is invalid

Solution: Please specify a correct CRM type

Error Code: 81

<rsp stat="fail" version="1.0">
    <err code="81">Prospect ID and FID do not match</err>
</rsp>

Problem: The provided Prospect ID and FID do not match a single prospect

Solution: Please provide a prospect ID and FID that match a single prospect

Error Code: 83

<rsp stat="fail" version="1.0">
    <err code="83">No valid CRM connectors available</err>
</rsp>

Problem: Your account does not have an available CRM connector

Solution: Please add a CRM connector to your account

Error Code: 85

<rsp stat="fail" version="1.0">
    <err code="85">Unable to save the prospect</err>
</rsp>

Problem: For some reason, the prospect was not saved

Solution: Please resubmit the request or review the original request for errors

Error Code: 86

<rsp stat="fail" version="1.0">
    <err code="86">Invalid Template id</err>
</rsp>

Problem: The template ID provided does not correspond to a template

Solution: Please provide a template ID that is valid

Error Code: 88

<rsp stat="fail" version="1.0">
    <err code="88">Your account must use version 4 of the API.</err>
</rsp>

Problem: You have requested version 3 of the API, but your account must use version 4.

Solution: Please make the request using /version/4 in place of /version/3

Error Code: 89

<rsp stat="fail" version="1.0">
    <err code="89">Your account is unable to use version 4 of the API.</err>
</rsp>

Problem: You have requested version 4 of the API, but your account must use version 3.

Solution: Please make the request using /version/3 in place of /version/4

Error Code: 90

<rsp stat="fail" version="1.0">
    <err code="90">Prospect array should be a flat array of attributes</err>
</rsp>

Problem: The prospect array given was not a flat array, and it should have been

Solution: Resubmit the request with a flat array. example

Error Code: 91

<rsp stat="fail" version="1.0">
    <err code="91">Prospect array must be keyed by email address</err>
</rsp>

Problem: The prospect array given was not keyed by email addresses, but should have been

Solution: Resubmit the request with an array keyed by email addresses. example

Error Code: 10000

<rsp stat="fail" version="1.0">
    ...
    <err code="10000" param="...">...</err>
    ...
</rsp>

Problem: An error occurred when processing the parameter designated in the param attribute of the <err> node. Several <err> nodes may be contained within the `` <rsp> node if multiple errors occurred.

Solution: The msg attribute of each <err> node should contain advice as to how to remedy the error(s).