Name: Restaurant Health API: Access Public Inspection Records & Sc
Brand: sitetrace
SKU: api-sitetrace-restaurant-health-inspector
Availability: InStock
Author: API Market

Edy Appenzeller

# 🍽️ Restaurant Health Inspector API — Public Health Inspection Records & Scores

## Overview
The Restaurant Health Inspector API provides comprehensive access to public health inspection records and scores for restaurants. Designed for developers, this API aggregates publicly available data to deliver structured scores, detailed violation history, insightful trend analysis, and precise risk assessments for food establishments. Empower your applications, platforms, and internal systems with critical restaurant safety data, enabling informed decisions for consumers, businesses, and regulatory bodies.

## Features
*   **Inspection History**: Access up to 10 historical inspections per query, including numerical scores, letter grades (A/B/C/F), violation counts, and clear pass/fail results. Understand a restaurant's long-term compliance with health standards.
*   **Violation Severity Breakdown**: Detailed classification of violations into Critical (immediate health risk), Major, and Minor categories, each accompanied by specific issue descriptions for actionable insights.
*   **Trend Analysis**: Automated analysis to determine if a restaurant's health scores are improving, stable, or declining over its recent inspection history, providing a dynamic view of performance.
*   **Risk Classification**: Get an overall LOW, MEDIUM, or HIGH risk rating for each restaurant, based on its history of critical violations and overall compliance, simplifying risk assessment.
*   **Peer Comparison**: Benchmark restaurant scores against city averages with precise percentile rankings, offering valuable context on how an establishment performs relative to its peers.
*   **Actionable Recommendations**: Receive prioritized recommendations for recurring high-priority issues, aiding in quick and effective response actions for improving food safety.

## Use Cases
*   **Food Delivery & Dining Platforms**: Integrate health grades and inspection scores directly into restaurant listings, helping users make safe and informed dining choices. Enhance user trust and platform reputation by prioritizing food safety.
*   **Travel & Hospitality Apps**: Guide travelers and tourists to safer dining options by displaying health inspection data alongside restaurant recommendations, improving the overall travel experience.
*   **Corporate & Event Catering**: Screen potential catering vendors and food suppliers based on their health inspection history and risk profiles, ensuring compliance and reducing health-related liabilities for corporate events and employee meals.
*   **Restaurant Insurance Underwriting**: Assess the risk profiles of restaurants more accurately for insurance purposes, leveraging detailed violation data and risk classifications to tailor premiums and coverage.
*   **Real Estate & Business Investment**: Evaluate the operational risk and potential liabilities of commercial properties or restaurant businesses by analyzing historical health inspection performance before acquisition or investment.

## Pricing


| Plan  | Price   | Calls/Month |
| :---- | :------ | :---------- |
| Basic | Free    | 50          |
| Plus  | $4.99   | 200         |
| Pro   | $9.99   | 1,000       |
| Ultra | $29.99  | 5,000       |
| Mega  | $99.99  | 20,000      |

## API Documentation

### Base URL
All API requests for the Restaurant Health Inspector API should be made to the following base URL:
`https://prod.api.market/api/v1/sitetrace/restaurant-health-inspector`

## Authentication
Authentication is handled via your API key. Include your API key in the `x-api-market-key` header for all requests:

```
x-api-market-key: YOUR_API_MARKET_KEY
```



## Request Example

```json
{
  "restaurant_name": "McDonalds",
  "city": "New York",
  "state": "NY"
}
```

## cURL Example

```bash
curl -X POST "https://prod.api.market/v1/sitetrace/restaurant-health-inspector/api/restaurant-health-inspector" \
  -H "x-api-market-key: YOUR_API_MARKET_KEY" \
  -H "Content-Type: application/json" \
  -d '{"restaurant_name":"McDonalds","city":"New York","state":"NY"}'
```

## Example Response

```json
{
  "success": true
}
```

## Integration Notes

- Send JSON requests with the required fields shown in the request example.
- Successful responses return structured JSON suitable for dashboards, automations, enrichment pipelines, and backend workflows.
- Validate user input before sending requests, especially URLs, domains, emails, phone numbers, business names, or free-text prompts.
- If the API returns a validation error, check the response message and confirm that all required fields are present.

## Status Codes
A comprehensive list of HTTP status codes and their meanings:

*   **200 OK**: The request was successful. For `POST /predictions`, this means the prediction was successfully initiated. For `GET /predictions/{id}`, it means the status or results were retrieved.
*   **201 Created**: (Not typically used by this API for predictions, but standard for resource creation).
*   **400 Bad Request**: The request was malformed, or essential input parameters were missing or invalid. Check the request body and parameters against the schema.
*   **401 Unauthorized**: Your API key is missing from the `x-api-market-key` header, or it is invalid. Ensure your API key is correctly provided.
*   **403 Forbidden**: Your API key is valid, but you do not have sufficient permissions to access this resource or perform this action. This might indicate a plan limitation or an issue with your subscription.
*   **404 Not Found**: The requested resource could not be found. For `GET /predictions/{id}`, this means the provided prediction ID does not exist.
*   **429 Too Many Requests**: You have exceeded the rate limit for your current subscription plan. Implement retry logic with exponential backoff.
*   **500 Internal Server Error**: An unexpected error occurred on the server. This indicates an issue on our end. Please report this if it persists.
*   **503 Service Unavailable**: The service is temporarily unable to handle the request due to maintenance or overload. Try again after a short delay.

## Rate Limits
API usage is subject to rate limits based on your subscription plan (refer to the Pricing section). If you exceed your plan's call limit, you will receive a `429 Too Many Requests` HTTP status code.

**How to handle rate limits:**
*   **Monitor Usage**: Keep track of your API call volume to stay within your plan's limits.
*   **Exponential Backoff**: When a `429` error is received, implement a retry mechanism with exponential backoff. This means waiting for progressively longer periods between retries (e.g., 1s, 2s, 4s, 8s).
*   **Upgrade Plan**: If you consistently hit rate limits, consider upgrading your subscription plan to accommodate higher usage volumes.



## FAQ

**Q: What kind of restaurant data does the API provide?**
A: The API provides public health inspection records, including scores, grades, violation history (critical, major, minor), trend analysis, risk classifications (LOW/MEDIUM/HIGH), and peer comparisons against city averages.

**Q: How up-to-date is the inspection data?**
A: The API aggregates publicly available health inspection records. The freshness of the data depends on the update frequency of the original public sources, which varies by jurisdiction. The API strives to provide the most recent available data.

**Q: Can I search for restaurants without a specific address, only by name, city, and state?**
A: Yes, `restaurant_name`, `city`, and `state` are required. `address` and `zip` are optional but highly recommended for more accurate and precise results, especially for common restaurant names.

**Q: What happens if a restaurant is not found?**
A: If a restaurant cannot be found based on the provided parameters, or if there is no inspection data available for it, the prediction will likely complete with a `status: "failed"` and an informative `error` message in the response.

**Q: Are there any geographical limitations to the data?**
A: The API aggregates data from various publicly available sources, primarily within the United States. Coverage may vary by city and state. We continuously work to expand our data coverage.

**Q: How do I get an API key?**
A: You can obtain an API key by subscribing to one of our plans on API.market. Your subscription key will be available in your API.market dashboard.

**Q: Can I use this API for commercial applications?**
A: Yes, the API is designed for commercial use cases, including food delivery platforms, travel apps, corporate catering, and insurance underwriting. Please refer to our pricing plans for usage limits.

## Contact Us
If you have any questions or need assistance, you can reach out to us through the embedded chat on the bottom right corner of the page or send an email to hello@magicapi.com.

Access public health inspection records, scores, violation history, and trend analysis for restaurants. Ensure food safety, assess risk, and make informed decis

Restaurant Health API: Access Public Inspection Records & Sc

Basic