Hoco Parts API

🔐 API Key Validation

Enter your API key to view personalized documentation based on your access level and profile.

API Key

👤 Your Access Information

🚀 API Overview

The Hoco API provides access to comprehensive motorcycle parts data, including product information, fitment details, and inventory levels. Our API is designed to help motorcycle retailers, parts suppliers, and e-commerce platforms integrate with our extensive database.

Base URL: https://data.hocoparts.com/api

🔐 Authentication: All API requests require a valid API key provided in the X-API-Key header. Contact us to obtain your API key and specify which endpoints you need access to.

🔑 Your Data Access

Based on your API key authorization, you have access to specific data fields and endpoints. The exact data available depends on your contract terms and access level.

POST /validate_api_key ▼

Validate an API key and check access to specific endpoints

📝 Description

This endpoint validates an API key and checks if the key has access to a specific endpoint route. It returns validation status, client information, and access permissions.

📋 Request Body

Parameter	Type	Required	Description
api_key	string	Required	The API key to validate
endpoint_route	string	Required	The endpoint route to check access for (e.g., "/api/products")

💡 Example Request

{
    "api_key": "your-api-key-here",
    "endpoint_route": "/api/products"
}
                        

🌐 cURL Example

curl -X POST "https://data.hocoparts.com/api/validate_api_key" \
  -H "Content-Type: application/json" \
  -d '{
    "api_key": "your-api-key-here",
    "endpoint_route": "/api/products"
  }'
                            

📤 Responses

200 Success - API key is valid

{
    "valid": true,
    "client_id": "12345",
    "client_name": "Your Company Name"
}
                        

400 Bad Request - Missing required parameters

401 Unauthorized - Invalid API key

⚠️ Common Error Codes

Status Code	Description	Common Causes
400	Bad Request	Missing required parameters (e.g., page, pageSize), invalid values (pageSize must be 1-500), invalid request format
401	Unauthorized	Missing API key, invalid API key
403	Forbidden	API key doesn't have access to endpoint, access expired, contract not approved
404	Not Found	No data available for the specified page (page exceeds available data)
500	Internal Server Error	Database connection issues, server-side errors

🚦 Rate Limits & Best Practices

Rate Limits: API usage is monitored and may be subject to rate limiting based on your contract terms
Pagination: Most API endpoints require page and pageSize parameters for pagination. Use page=1 for the first page, page=2 for the second page, etc. The pageSize parameter controls records per page (1-500, recommended: 100). Response headers include X-Page, X-Page-Size, and X-Record-Count for pagination tracking.
Caching: Consider caching responses locally to reduce API calls
Error Handling: Implement proper error handling for all response codes, including 400 for invalid pagination parameters
API Key Security: Keep your API key secure and never expose it in client-side code
Endpoint Expiry: Monitor your endpoint access expiry dates to avoid service interruptions

🆘 Support & Contact

For API access requests, technical support, or questions about upgrading your profile:

Technical Support: Contact your account manager
API Access: Request access to specific endpoints through your contract

📚 API Tester

Test your data access and download the results?

🚀 Launch Interactive API Testing Tool