Core Capabilities and Architecture
The fuzzy search endpoint provides flexible matching across multiple corporate identifiers, including entity names, 15-digit registration numbers, and 18-digit unified social credit codes. Responses deliver structured payloads containing entity category enumerations (e.g., 0 for standard enterprises, 4 for associations, 5 for law firms, 6 for Hong Kong entities), legal representatives, and founding dates. By default, the system returns the top 10 most relevant matches, though cached queries may yield up to 19 records. The billing mechanism operates on a success-based model, charging only when valid data is retrieved.
Endpoint Specification
Request Parameters
| Requirement | Parameter | Type | Validation |
|---|---|---|---|
| Mandatory | auth_token | String | Access credential obtained via registration |
| Mandatory | search_term | String | Must contain at least 4 characters |
# Shell request demonstration
curl -G "https://api.corp-search.io/v1/fuzzy" \
--data-urlencode "search_term=Chongqing Tech" \
--data-urlencode "auth_token=YOUR_ACCESS_TOKEN"
Security Notice: The auth_token serves as a unique identifier and must be secured to prevent unauthorized usage.
Response Schema
{
"status": 200,
"message": "Query successful.",
"results": [
{
"entityId": 1105,
"recordTimestamp": 1695260987000,
"matchField": "Entity Name",
"registrationId": "500113014353471",
"foundingDate": "2021-06-02",
"entityName": "Chongqing Tech Development Co., Ltd.",
"legalRepresentative": "Zhang Wei",
"socialCreditCode": "91500113MAABRA7D0H",
"entityCategory": "0"
}
]
}
Field Definitions
| JSON Path | Type | Description |
|---|---|---|
| results[].socialCreditCode | String | 18-digit unified social credit identifier |
| results[].foundingDate | String | Establishment date (ISO 8601 format) |
| results[].entityCategory | String | Entity type enumeration code |
Error Handling
| HTTP Status | Error Code | Resolution |
|---|---|---|
| 403 | 40301 | Verify the auth_token parameter validity |
| 400 | 40002 | Ensure search_term meets the 4-character minimum |
| 429 | 42901 | Daily complimentary quota depleted |
Integration Patterns
Financial System Validation
# Invoice header verification logic
def verify_invoice_header(target_org_name):
api_response = requests.get(
"https://api.corp-search.io/v1/fuzzy",
params={
"search_term": target_org_name[:20],
"auth_token": os.environ['API_TOKEN']
}
)
payload = api_response.json()
if payload.get('status') == 200:
matched_entities = payload['results']
return any(entity['entityName'] == target_org_name for entity in matched_entities)
return False
Supply Chain Management
During vendor qualification audits, the API enables:
- Automated supplier name completion
- Social credit code authenticity checks
- Dynamic calculation of corporate longevity
Data Platform Caching
// Java Spring caching implementation
@Cacheable(value = "corpSearchCache",
key = "#searchTerm",
unless = "#result == null || #result.getBody().getResults().isEmpty()")
public ResponseEntity<Map<String, Object>> fetchCorporateData(String searchTerm, String authToken) {
// API invocation implementation
}
Performance and Billing Optimization
Cost Management
The transaction-based pricing model applies fees exclusively to successful data retrievals:
- Successful match: Nominal micro-fee per request
- Empty result set: No charge applied
- New accounts: Complimentary 20 daily queries
Query Optimization Strategies
- Search Term Refinement: Prefer distinct entity name fragments. Including regional prefixes (e.g., "Beijing", "Shanghai") significantly boosts match accuracy.
- Local Caching: Store high-frequency queries locally with a TTL of 300 seconds. Employ asynchronous I/O for concurrent batch processing.
Quota Monitoring
Administrators can track utilization metrics and remaining complimentary allocations through the developer dashboard metrics portal.