curl -X POST "https://api.sinhcoms.com/grank/search"
-H "Authorization: Bearer YOUR_API_KEY"
-H "Content-Type: application/json"
-d '{
"keyword": "dentist",
"latitude": 28.4595,
"longitude": 77.0266,
"radius_km": 5,
"business_name": "32 Dental House",
"place_id": "",
"country_code": "IN",
"language_code": "en",
"max_results": 20
}'
# Position requires keyword, latitude, longitude and business_name
curl -X POST "https://api.sinhcoms.com/grank/position"
-H "Authorization: Bearer YOUR_API_KEY"
-H "Content-Type: application/json"
-d '{
"keyword": "dentist",
"latitude": 28.4595,
"longitude": 77.0266,
"business_name": "32 Dental House",
"radius_km": 5,
"country_code": "IN",
"language_code": "en",
"max_results": 20
}'Grank API
The GRank API exposes the ranking utility through an active controller catalogue containing health, search and position routes. It is intended for applications that need to query the ranking workflow programmatically and manage usage through the normal Vismrit API subscription controls.
What this API is designed to do
Search-ranking utility API with health, search and position routes.
Where it can fit
These are common integration scenarios; the exact implementation depends on your application, data-handling requirements and subscription tier.
Published routes and methods
The endpoint list below is read from the existing API controller catalogue. Website Management can explain the API, but it cannot invent or replace live endpoint routes.
/grankIndex/grank/healthHealth/grank/positionPosition/grank/searchSearchAuthentication, request shape and response handling
These examples are presentation content managed by Website Management. Always compare them with the live API documentation and endpoint catalogue before production integration.
Use Authorization: Bearer YOUR_API_KEY or X-API-Key. Search and position requests accept JSON, form-data or x-www-form-urlencoded input.
The GRank controller returns the ranking-service JSON received from its upstream WebSocket workflow. Check the ok flag and handle non-2xx status values returned by the service.Documented error states
422Required search or position parameter is missing/invalid401API key authentication or product authorization failed429Daily request limit exceeded502Ranking WebSocket/upstream service errorFrom subscription to first request
Use the customer dashboard as the control point for keys, whitelist rules and plan limits.
Select a GRank subscription tier
Create or assign an API key
Use the health route for readiness checks
Integrate search and position routes according to the expected parameters
Store only the result data your application actually needs and monitor usage
Choose the request capacity you need
Pricing and limits below are read from the active subscription tiers in the API system.
- 1,000,000 requests/day
- 10,000,000 requests/month
Before you go live
Search-engine behaviour and third-party result formats can change. Build calling applications to tolerate transient errors and changing result availability.
Already a customer? Continue from your dashboard.
Sign in to keep purchases, licenses, API keys, downloads, invoices and project requests connected to one account.