Skip to main content

Troubleshooting

Troubleshoot common Mashvisor API issues, including missing data, empty responses, API key problems, credit limits, request errors, and endpoint parameter issues.

Written by Mashvisor Advisor

If you are having trouble with Mashvisor API, this guide can help you check the most common issues before contacting support.

1. Check your API key

Make sure you are using the correct API key from your developer dashboard:

If your API key is missing, inactive, copied incorrectly, or connected to a different account, your requests may fail.

2. Check your API credits

If your account does not have enough API credits, API requests may stop working or return an error.

You can review your credit usage from your developer dashboard:

If you need more credits, you may need to upgrade your plan or contact our team.

3. Check the endpoint URL

Make sure you are using the correct endpoint from the API documentation:

For newer documentation, you can also check:

A small typo in the endpoint URL can cause the request to fail.

4. Check required parameters

Many endpoints require specific parameters such as address, city, state, zip code, latitude, longitude, property ID, or listing status.

If required parameters are missing or formatted incorrectly, the response may fail or return no results.

Before contacting support, confirm that:

  • Required parameters are included

  • Address fields are spelled correctly

  • City and state are included when needed

  • Zip code is valid

  • Latitude and longitude are correctly formatted

  • Filters are not too restrictive

5. Empty response or no results

An empty response does not always mean the API is broken.

It may mean:

  • The property was not found

  • The address format needs adjustment

  • The endpoint does not support that location

  • The requested field is not available

  • No matching listings or comps were found

  • The filters are too narrow

  • The market has limited data availability

Try testing another property, city, or zip code to confirm whether the issue is specific to one location.

6. Coverage-related issues

Data availability can vary by location, property, endpoint, and source availability.

Not every market will have every field available.

If your workflow depends on specific fields or zip codes, we recommend testing those locations first before scaling.

7. Credit usage seems high

If your API credits are being used faster than expected, review your workflow.

Common reasons include:

  • Making repeated requests for the same property

  • Calling multiple endpoints for each property

  • Running requests in loops

  • Not caching results

  • Testing too many records at once

  • Refreshing data more often than needed

To reduce unnecessary usage, consider caching results and only calling the endpoints you need.

8. Rate limit issues

If you send too many requests too quickly, some requests may fail or be delayed.

Mashvisor API has request limits to protect performance and reliability.

If you are building a high-volume workflow, we recommend adding request throttling, retries, and proper error handling.

9. Authentication or permission errors

If you receive an authentication or permission error, check:

  • API key is correct

  • API key is active

  • Account has available credits

  • Subscription is active

  • Endpoint is included in your access

  • Request headers are correct

10. What to send support

If you still need help, please contact us and include:

  • Account email

  • Endpoint URL

  • Request parameters

  • Sample request

  • Sample response

  • Error message

  • Date and time of the issue

  • Target property, city, or zip code

This helps our team investigate faster and give you a more accurate answer.

Did this answer your question?