API: checking status, history and balance

Use /status, /history and /balance to follow submissions, plus the public /plans and /health endpoints and the error codes.

After submitting with POST /api/v1/submit (see Your API key and first call), use these endpoints to follow your URLs. All responses are JSON.

GET /api/v1/status?ids=a,b,c

Returns the status of up to 100 submissions, using the ids that /submit gave you. Requires your API key.

Each item includes status, error, createdAt, submittedAt, botVisitedAt, indexedAt, enginesNotified (for example ["bing", "yandex", "seznam", "naver", "yep"]) and crawlerVisits (verified visit times per engine).

GET /api/v1/history?page=1&limit=50

Your submissions, newest first, with pagination (page, limit, total, pages). limit can be 1 to 100. Requires your API key.

GET /api/v1/balance

Your current credits, the creditCostPerUrl (1) and stats counting your visited, indexed and refunded submissions. Requires your API key.

Public endpoints (no key)

GET /api/v1/plans: active credit packs with priceUsd, credits and perUrlUsd.
GET /api/v1/health: service status, feeders online, today's remaining submission capacity and the current queue size.

Status values

queued: accepted and charged, waiting for a feeder with free capacity.
submitted: crawl signal sent to Google and IndexNow, waiting for Googlebot.
visited: a Googlebot visit was verified by reverse and forward DNS.
indexed: found in Google's index during a follow-up check.
not_indexed: crawled, but still not in the index after the 72-hour check.
refunded: no verified Googlebot visit within 24 hours; the credit was returned.
failed: couldn't be processed; see error.

Error codes

Errors return { "success": false, "error": "…" } with one of these HTTP codes:

400: bad request, such as no valid URLs, more than 500 URLs, or missing ids.
401: missing or invalid API key.
402: not enough credits for the valid URLs sent. Nothing was charged.
403: API access is switched off for this key, or the request IP isn't on your whitelist.
429: rate limit exceeded (20 requests/second on Personal, 50 on Business).

Polling tips

Don't poll every second. Googlebot visits usually take minutes, and index checks happen about 1, 24 and 72 hours after the visit. Checking every few minutes, then every few hours, is plenty.
Batch your ids: one /status call can cover 100 submissions.

The full reference with examples is on the API docs page.