# Advocate Error Codes | Error Code | Message | How to fix it | | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | RS003 | `accountid` is required at initialization. | Check that you are using the auth token (test or live) to match the correct `tenant_alias` when signing requests. | | RS005 | Secure Mode enabled, checksum required. | Make sure to include a checksum or JWT. | | RS006 | The checksum or JWT value is incorrect. |
  1. Check that you are including a checksum or JWT and ensure that the Account SID is included as a child in the header of the JWT.
  2. Check that you are using the Auth Token and Account SID to match your program.
  3. Check that you are not including client-only parameters like mode and locale in your checksum or JWT calculations.
| | RS013 | Unable create user on account. The `accountid` already has reached the maximum number of users per account. (limit 1000 users per `accountid`). | Make sure that you have not erroneously grouped all of your users under a single `accountid`. | | RS014 | An internal error occurred; unable to generate referral code for new user. | Something went wrong inside of the impact.com system. This may be the result of some temporary outage, and in most cases, you should just reload the page and try again. | | RS015 | No tenant alias was provided or the provided tenant alias does not exist. | Contact our [support team](mailto:saasquatch-support@impact.com). | | RS016 | An internal error occurred; unsupported payment system. | Something went wrong inside of the impact.com system. This may be the result of some temporary outage, and in most cases, you should just reload the page and try again. | | RS017 | An internal error occurred. | Something went wrong inside of the impact.com system. This may be the result of some temporary outage, and in most cases, you should just reload the page and try again. | | RS020 | An internal error occurred. | Something went wrong inside of the impact.com system. This may be the result of some temporary outage, and in most cases, you should just reload the page and try again. | | RS021 | An internal error occurred; account already exists. | Make sure the `accountid` you're trying to use to create a new user does not already exist, or use a different `accountid`. | | RS023 | The provided email field is an invalid email address. |
  1. Make sure that the email address is at least 7 characters long.
  2. The email address must have characters before the @ symbol.
  3. The Top Level Domain needs to be at least 2 characters (.ca for example).
| | RS024 | The `first_name` provided is invalid or does not exist. |
  1. Make sure that you include and set the first\_name parameter in your request.
  2. The first\_name field can only contain ASCII character codes 65-90 and 97-122.
| | RS026 | No theme has successfully been published yet. | Something went wrong inside of the impact.com system. This may be the result of some temporary outage, and in most cases, you should just reload the page and try again. | | RS027 | An internal error occurred. | Something went wrong inside of the impact.com system. This may be the result of some temporary outage, and in most cases, you should just reload the page and try again. | | RS031 | The tenant associated with the provided alias has been deleted. | Contact our Contact our [support team](mailto:saasquatch-support@impact.com). | | RS032 | The JWT value is incorrect. |
  1. Check that you are including a checksum or JWT and ensure that the Account SID is included as a child in the header of the JWT.
  2. Check that you are using the API key (test or live) to match the correct tenant\_alias when signing requests.
  3. Check that you are not including client-only parameters like mode and locale in your checksum or JWT calculations.
| | RS033 | Rate limit exceeded. |
  1. Check that multiple referral participants are not incorrectly registered under the same account.
  2. Check that server-side calls being made to Advocate are done so using an API key for authentication and not a JWT.
| | RS034 | The provided `referralCode` is empty or invalid. |
  1. Check that you are including a valid referral code.
  2. Check that you are not including the referralCode as an empty parameter when you do not plan to set a referral code.
| | RS036 | The provided `widgetType`or `widget` field is invalid. | Check that you are including a valid value for `widgetType` or `widget`. These include `p/{programId}/w/referrerWidget` and `p/{programId}/w/websiteReferralWidget`. | | RS037 | The provided `engagementMedium` field is invalid. | Check that you are including a valid value for `engagementMedium`. These include `POPUP` and `EMBED`. | | RS038 | No tenant found for the provided alias. | Contact our [support team](mailto:saasquatch-support@impact.com). | | RS039 | The provided locale field is an invalid locale. |
  1. Check that you are including a locale formatted with the ISO two-character language and country code in the format language\_country.
  2. Check that you are not including the parameter locale when you are not intending to set the value.
| | RS041 | No account found for the provided ID. |
  1. Check that you have included the correct accountid in your UTT calls.
  2. Check that you are using the correct tenant.
| | RS042 | No user found for the provided ID. |
  1. Check that you have included the correct userId in your UTT calls.
  2. Check that you are using the correct tenant.
| | RS043 | The user ID cannot be empty. | Check that you are including a valid `userId`. | | RS044 | The account ID cannot be empty. |
  1. Check that you are including a valid accountid.
  2. Check that you are not including the accountid as an empty parameter when you do not plan to set an accountid.
| | RS045 | The request did not have the necessary authorization credentials. | Check that you are including a JWT. | | RS046 | The request had an incorrect content-type. | Make sure the content-type of your request data is application/JSON. | | RS047 | The request was unauthorized because it must use SSL. | Check that you are using `HTTPS` when making requests to Advocate. | | RS048 | An internal error occurred; user already exists. | Make sure the `user_id` you're trying to use to create a new user does not already exist, or use a different `user_id`. | | RS049 | There has been an error with one of your programs. | Pause the program that is encountering the error and check the configured program rules to confirm that everything is set up correctly. Pausing your program means referrals can't happen at all until you turn it back on. If you are still experiencing errors, please contact our [support team](mailto:saasquatch-support@impact.com). | | RS050 | The user is set to do-not-track. | Contact our [support team](mailto:saasquatch-support@impact.com). | | RS051 | You are using a legacy call that is not compatible with your Growth Automation Program. | Review your API Call against our official list of Advocate API Calls to ensure that the call you are using is designed to work with Growth Automation Programs. | | RS052 | You have passed an invalid cookie value. | Check the `base64` decoded cookie value to make sure that the schema and information are correct. | | RS053 | You have passed an invalid shareLink. | Make sure that you have a custom short domain configured and that the shareLink you are passing is valid and in the correct format. Refer to [Set up a Domain for Advocate](https://help.impact.com/en/support/solutions/articles/155000000325-set-up-a-domain-for-advocate). | --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://integrations.impact.com/brand-api-reference/advocate-api-reference-v1/readme/advocate-error-codes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.