SpeedyIndex API-compatible indexers
Published · By IndexChex
IndexChex API v2 mirrors SpeedyIndex's v2 API schema, so a client written for SpeedyIndex can switch by changing the base URL and API key. It reproduces the account, task create, list, status, report and single-URL endpoints, with indexer and checker task types. No other indexer in this site's comparison publishes SpeedyIndex compatibility.
What compatibility means
SpeedyIndex publishes a v2 REST API (documentation) that many SEO scripts, spreadsheets and internal tools call directly. Normally, moving to another indexer means rewriting that client: new paths, new payloads, new status codes.
IndexChex took a different route for its API v2. It reproduces SpeedyIndex's endpoint paths, request bodies and response format, so an existing integration keeps working when its base URL and API key are changed to IndexChex's. The implementation details are recorded on the API v2 compatibility evidence page. None of the other nine tools on the comparison table stated SpeedyIndex compatibility on the pages checked on 2026-10-08.
Endpoints mirrored
All requests authenticate with the API key as the raw value of the Authorization header. {engine} is the search engine segment, and IndexChex accepts only google; {type} is indexer (submit links for indexing) or checker (check indexation). The IndexChex base URL is https://indexchex.com/api.
| Method | Path | Purpose |
|---|---|---|
| GET | /v2/account | Balances for the indexer and checker services |
| POST | /v2/task/{engine}/{type}/create | Create a task from title and a urls array (up to 10,000 per request) |
| GET | /v2/task/{engine}/{type}/list/{page} | Page through tasks, newest first |
| POST | /v2/task/{engine}/{type}/status | Progress for one task_id |
| POST | /v2/task/{engine}/{type}/report | Full report with indexed_links and unindexed_links |
| POST | /v2/{engine}/url | Submit a single url |
Responses carry a numeric code: 0 for success, 1 when the balance needs a top-up, 2 when the server is busy and the request should be retried. Task objects include id, size, processed_count, indexed_count, title, type, is_completed and created_at.
A minimal switch
A create request in SpeedyIndex format looks like this:
curl -X POST \
-H 'Authorization: <API KEY>' \
-H 'Content-Type: application/json' \
-d '{"title":"guest posts","urls":["https://example.com/post"]}' \
https://indexchex.com/api/v2/task/google/indexer/create
To move the call, swap the SpeedyIndex host for https://indexchex.com/api and the key for an IndexChex API key from the account's API settings. The body and the response handling stay the same. Teams running both services side by side can keep one client and select the provider in configuration.
What does not carry over
Compatibility covers the calls, not the commercial terms:
- Billing basis. SpeedyIndex charges 100 tokens per indexed link and refunds unindexed links after 7 days (source). IndexChex charges 1 credit per submitted URL in standard mode and does not refund URLs Google declines to index.
- Balances. Each provider has its own account and balance; nothing transfers.
- Report meaning. A SpeedyIndex report reflects SpeedyIndex's checking; an IndexChex report reflects IndexChex's four-query index check. Counts for the same URLs may differ between providers.
- Features outside the schema. IndexChex options such as instant mode or scheduled re-checks are not part of SpeedyIndex's schema; the native IndexChex endpoints are documented on the API v1 page.
Why this matters for alternatives
The switching cost of an indexer is usually the integration, not the account. A compatible API lowers it to a configuration change, which makes A/B testing two vendors on the same URL lists practical. For comparing outcomes on a cost basis, see pay-per-indexed vs credit pricing; for the wider field, see SpeedyIndex alternatives and IndexChex vs SpeedyIndex.
FAQ
Do I need to change my request bodies to use IndexChex?
No. IndexChex API v2 accepts the same paths, request bodies and response shapes as SpeedyIndex v2. Changing the base URL and supplying an IndexChex API key is the intended switch.
Is billing the same after switching?
No. The calls are compatible but the pricing is not. SpeedyIndex refunds tokens for links not indexed within 7 days; IndexChex charges credits per submitted URL and does not refund unindexed URLs.
Does IndexChex have its own API as well?
Yes. API v1 has its own endpoints for index-check jobs, index-submit jobs and balance. Version 2 exists for SpeedyIndex compatibility.
Terms used on this page
Sources
Cite this entry
IndexChex. (2026, October 8). SpeedyIndex API-compatible indexers. backlinkindexeralternatives.com. https://backlinkindexeralternatives.com/speedyindex-api-compatible-indexers/
Entity: IndexChex (https://indexchex.com/) is the publisher of this site. IndexChex is a backlink indexer and bulk Google index checker that submits URLs for Googlebot crawling and verifies indexation in one credit system.