To find your ManyChat error logs, navigate to Settings > Logs. Here you will see all of the errors that have occurred in your account over the past two weeks.

If you see more errors than expected, do not be concerned! Some Seller.Tools flows will register a “Response Mapping’ error each time you run an external request. This accounts for a throttling message that will only be present in your flows if the external request does not run properly; thus, there will be nothing to map to this particular custom field if runs properly.

Find the error log for the issue that you are seeing. You may need to click through multiple logs to find the one that relates to the issue at hand. We’d recommend finding the rough time frame when the error occurred.

Once you have found the error log, expand “General”, “Details”, and “Response Body”.

Screen_Shot_2020-07-06_at_11.24.24_AM.png

What we are looking for will be found under General > Response Code. This resource will help you make sense of what that code means! See below for a breakdown of each error code for each action that you will be using the Seller.Tools API call for.

Error Codes

We'll cover all relevant error codes with an explanation and recommended next steps for the action items below:

Get Order Information

Wallet: Get Wallet Balance

Wallet: Issue Gift Card

Add to Blacklist

Check Blacklist

MCF: Create an MCF Order

MCF: Check the Status of an MCF Order

Counter: Check Value

Counter: Update Counter


Get Order Information

[Pulls all relevant information about an Amazon Order ID, such as order status, buyer information, price information, product information.]

400: Missing Data

There was a field in your request that was left blank. Make sure all of your fields are filled out with a valid custom field or value before proceeding. This can also happen if you have set up the request correctly, but the custom field did not contain any user data.

401: Invalid Credentials Provided

This means you used the incorrect API key. Check your app settings to make sure your API key matches exactly in your Seller.Tools account, and that there are no extra spaces before or after your API key.

Here’s a video resource on how to find your API key. You can edit your API key by navigating to your Seller.Tools App settings in ManyChat (Settings > Apps > Seller.Tools > Gear Icon).

When you click the gear icon, your Live and Test API Key input will pop up. You can edit your API keys at any time by replacing the text in those input fields.

Also, as a best practice, be sure to always copy and paste your API key. We don’t recommend typing it out.

As a final check, if you are still using the older method of external requests to access the Seller.Tools API and are using bot fields for your API keys, please make sure that the bot field that contains your API key (check this in Settings > Custom Fields > Custom Bot Fields > 'Value' of your bot field) matches the bot field that is actually used in your external request.


Wallet: Get Wallet Balance

[Gets the current value of your Seller.Tools Wallet balance.]

401: Invalid Credentials Provided

This means you used the incorrect API key. Check your app settings to make sure your API key matches exactly in your Seller.Tools account, and that there are no extra spaces before or after your API key.

Here’s a video resource on how to find your API key. You can edit your API key by navigating to your Seller.Tools App settings in ManyChat (Settings > Apps > Seller.Tools > Gear Icon).

When you click the gear icon, your Live and Test API Key input will pop up. You can edit your API keys at any time by replacing the text in those input fields.

Also, as a best practice, be sure to always copy and paste your API key. We don’t recommend typing it out.

As a final check, if you are still using the older method of external requests to access the Seller.Tools API and are using bot fields for your API keys, please make sure that the bot field that contains your API key (check this in Settings > Custom Fields > Custom Bot Fields > 'Value' of your bot field) matches the bot field that is actually used in your external request.


Wallet: Issue Gift Card

[Sends a virtual gift card using funds from your Seller.Tools Wallet balance.]

400: Missing Data

There was a field in your request that was left blank. Make sure all of your fields are filled out with a valid custom field or value before proceeding. This can also happen if you have set up the request correctly, but the custom field did not contain any user data.

401: Invalid Credentials Provided

This means you used the incorrect API key. Check your app settings to make sure your API key matches exactly in your Seller.Tools account, and that there are no extra spaces before or after your API key.

Here’s a video resource on how to find your API key. You can edit your API key by navigating to your Seller.Tools App settings in ManyChat (Settings > Apps > Seller.Tools > Gear Icon).

When you click the gear icon, your Live and Test API Key input will pop up. You can edit your API keys at any time by replacing the text in those input fields.

Also, as a best practice, be sure to always copy and paste your API key. We don’t recommend typing it out.

As a final check, if you are still using the older method of external requests to access the Seller.Tools API and are using bot fields for your API keys, please make sure that the bot field that contains your API key (check this in Settings > Custom Fields > Custom Bot Fields > 'Value' of your bot field) matches the bot field that is actually used in your external request.

402: Insufficient Funds

This means that your Wallet balance was not enough to create the gift card. Try adding additional funds to your Wallet and trying again. We also recommend configuring auto top-up to make sure you never run out of funds.

422: The given data was invalid.

One or more of the values in your request was not properly formatted or consisted of real values. Ex: an email address was submitted that was not a real, valid email address.


Add to Blacklist

[Adds Values to your Seller.Tools Blacklist.]

400: Missing Data

There was a field in your request that was left blank. Make sure all of your fields are filled out with a valid custom field or value before proceeding. This can also happen if you have set up the request correctly, but the custom field did not contain any user data.

401: Invalid Credentials Provided

This means you used the incorrect API key. Check your app settings to make sure your API key matches exactly in your Seller.Tools account, and that there are no extra spaces before or after your API key.

Here’s a video resource on how to find your API key. You can edit your API key by navigating to your Seller.Tools App settings in ManyChat (Settings > Apps > Seller.Tools > Gear Icon).

When you click the gear icon, your Live and Test API Key input will pop up. You can edit your API keys at any time by replacing the text in those input fields.

Also, as a best practice, be sure to always copy and paste your API key. We don’t recommend typing it out.

As a final check, if you are still using the older method of external requests to access the Seller.Tools API and are using bot fields for your API keys, please make sure that the bot field that contains your API key (check this in Settings > Custom Fields > Custom Bot Fields > 'Value' of your bot field) matches the bot field that is actually used in your external request.

422: The given data was invalid.

One or more of the values in your request was not properly formatted or consisted of real values. Ex: an email address was submitted that was not a real, valid email address.


Check Blacklist

[Checks to see if a given value is on your Seller.Tools Blacklist.]

400: Missing Data

There was a field in your request that was left blank. Make sure all of your fields are filled out with a valid custom field or value before proceeding. This can also happen if you have set up the request correctly, but the custom field did not contain any user data.

401: Invalid Credentials Provided

This means you used the incorrect API key. Check your app settings to make sure your API key matches exactly in your Seller.Tools account, and that there are no extra spaces before or after your API key.

Here’s a video resource on how to find your API key. You can edit your API key by navigating to your Seller.Tools App settings in ManyChat (Settings > Apps > Seller.Tools > Gear Icon).

When you click the gear icon, your Live and Test API Key input will pop up. You can edit your API keys at any time by replacing the text in those input fields.

Also, as a best practice, be sure to always copy and paste your API key. We don’t recommend typing it out.

As a final check, if you are still using the older method of external requests to access the Seller.Tools API and are using bot fields for your API keys, please make sure that the bot field that contains your API key (check this in Settings > Custom Fields > Custom Bot Fields > 'Value' of your bot field) matches the bot field that is actually used in your external request.


MCF: Create an MCF Order

400: Missing Data

There was a field in your request that was left blank. Make sure all of your fields are filled out with a valid custom field or value before proceeding. This can also happen if you have set up the request correctly, but the custom field did not contain any user data.

401: Invalid Credentials Provided

This means you used the incorrect API key. Check your app settings to make sure your API key matches exactly in your Seller.Tools account, and that there are no extra spaces before or after your API key.

Here’s a video resource on how to find your API key. You can edit your API key by navigating to your Seller.Tools App settings in ManyChat (Settings > Apps > Seller.Tools > Gear Icon).

When you click the gear icon, your Live and Test API Key input will pop up. You can edit your API keys at any time by replacing the text in those input fields.

Also, as a best practice, be sure to always copy and paste your API key. We don’t recommend typing it out.

As a final check, if you are still using the older method of external requests to access the Seller.Tools API and are using bot fields for your API keys, please make sure that the bot field that contains your API key (check this in Settings > Custom Fields > Custom Bot Fields > 'Value' of your bot field) matches the bot field that is actually used in your external request.

422: The given data was invalid.

One or more of the values in your request was not properly formatted or consisted of real values. Ex: an email address was submitted that was not a real, valid email address.

For MCF orders, this is a common error if any item in your request was not formatted correctly, usually occurs with address information.

429: Too Many Requests

This means that you called this API endpoint for too many times in a short time period. The limit is set to 5 requests per second.

If you're seeing this issue consistently in your flow, please add a 1-minute wait step before the request to create an MCF Order. This should help mitigate the issue.


MCF: Check the Status of an MCF Order

400: Missing Data

There was a field in your request that was left blank. Make sure all of your fields are filled out with a valid custom field or value before proceeding. This can also happen if you have set up the request correctly, but the custom field did not contain any user data.

404: Not Found

The order ID that you entered was not found. Confirm that the order was actually created in your Seller Central account, as there may have been an error.

401: Invalid Credentials Provided

This means you used the incorrect API key. Check your app settings to make sure your API key matches exactly in your Seller.Tools account, and that there are no extra spaces before or after your API key.

Here’s a video resource on how to find your API key. You can edit your API key by navigating to your Seller.Tools App settings in ManyChat (Settings > Apps > Seller.Tools > Gear Icon).

When you click the gear icon, your Live and Test API Key input will pop up. You can edit your API keys at any time by replacing the text in those input fields.

Also, as a best practice, be sure to always copy and paste your API key. We don’t recommend typing it out.

As a final check, if you are still using the older method of external requests to access the Seller.Tools API and are using bot fields for your API keys, please make sure that the bot field that contains your API key (check this in Settings > Custom Fields > Custom Bot Fields > 'Value' of your bot field) matches the bot field that is actually used in your external request.

422: The given data was invalid.

One or more of the values in your request was not properly formatted or consisted of real values. Ex: an email address was submitted that was not a real, valid email address.

For MCF orders, this is a common error if any item in your request was not formatted correctly, usually occurs with address information. This could also mean that the order was not found.

429: Too Many Requests

If you're seeing this issue consistently in your flow, please add a 1-minute wait step before the request to check the status of an MCF Order. This should help mitigate the issue.


Counter: Check Value

[Checks the current value of your counter without modifying it; usually occurs at the beginning of your flow.]

401: Invalid Credentials Provided

This means you used the incorrect API key. Check your app settings to make sure your API key matches exactly in your Seller.Tools account, and that there are no extra spaces before or after your API key.

Here’s a video resource on how to find your API key. You can edit your API key by navigating to your Seller.Tools App settings in ManyChat (Settings > Apps > Seller.Tools > Gear Icon).

When you click the gear icon, your Live and Test API Key input will pop up. You can edit your API keys at any time by replacing the text in those input fields.

Also, as a best practice, be sure to always copy and paste your API key. We don’t recommend typing it out.

As a final check, if you are still using the older method of external requests to access the Seller.Tools API and are using bot fields for your API keys, please make sure that the bot field that contains your API key (check this in Settings > Custom Fields > Custom Bot Fields > 'Value' of your bot field) matches the bot field that is actually used in your external request.

422: The given data was invalid.

This occurs when the counter name is less than 5 characters long. Try entering a counter name that is at least five characters long, and be sure it does not include any spaces or special characters.


Counter: Update Counter

[Increases, decreases, or resets your counter’s value.]

401: Invalid Credentials Provided

This means you used the incorrect API key. Check your app settings to make sure your API key matches exactly in your Seller.Tools account, and that there are no extra spaces before or after your API key.

Here’s a video resource on how to find your API key. You can edit your API key by navigating to your Seller.Tools App settings in ManyChat (Settings > Apps > Seller.Tools > Gear Icon).

When you click the gear icon, your Live and Test API Key input will pop up. You can edit your API keys at any time by replacing the text in those input fields.

Also, as a best practice, be sure to always copy and paste your API key. We don’t recommend typing it out.

As a final check, if you are still using the older method of external requests to access the Seller.Tools API and are using bot fields for your API keys, please make sure that the bot field that contains your API key (check this in Settings > Custom Fields > Custom Bot Fields > 'Value' of your bot field) matches the bot field that is actually used in your external request.

422: The given data was invalid.

This occurs when the counter name is less than 5 characters long. Try entering a counter name that is at least five characters long, and be sure it does not include any spaces or special characters.

Did this answer your question?