Developer API

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.

api-grank
Published endpoints4
Active plans1
Base daily limit1,000
Base monthly limit30,000
Capabilities

What this API is designed to do

Search-ranking utility API with health, search and position routes.

Check API health before workflow execution
Run the published search operation
Query the published position operation
Manage keys, quotas and whitelist restrictions centrally
Use cases

Where it can fit

These are common integration scenarios; the exact use depends on your application, data handling requirements and subscription tier.

SEO monitoring dashboards
Keyword or result-position workflows
Scheduled ranking checks
Internal reporting and search-visibility tools
Endpoint catalogue

Published routes and methods

The endpoint list is read from the existing API controller catalogue. It changes automatically when the catalogue is refreshed.

MethodRoutePurpose
ANY/grankIndex
ANY/grank/healthHealth
ANY/grank/positionPosition
ANY/grank/searchSearch
Integration flow

From subscription to first request

Keep access and usage manageable by using the customer dashboard as the control point for keys, whitelist rules and plan limits.

01

Select a GRank subscription tier

02

Create or assign an API key

03

Use the health route for readiness checks

04

Integrate search and position routes according to the expected parameters

05

Store only the result data your application actually needs and monitor usage

Plans

Choose the request capacity you need

Pricing and limits below are read from the active subscription tiers in the API system.

Star

INR 499.00/month

  • 1,000,000 requests/day
  • 10,000,000 requests/month
Integration notes

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.