Public developer reference

QuickIndexing API Documentation

Submit URLs for processing and check credits from your server.

Base URL: https://quickindexing.com/api/v1. These examples describe requests; this page does not send them. Acceptance is not proof of Google indexing.

Authentication and key handling

Send your key in X-API-KEY. Create, replace or revoke one active key in API Access after signing in. Newly created keys are displayed once. Existing administrator-issued keys continue working.

Keep keys in server environment variables. Never put them in a query string, public frontend code or support screenshots. Replace or revoke an exposed key before continuing.

POST /indexing/submit

Send JSON with Content-Type: application/json and the authentication header.

Submission request fields

Field	Type	Contract
urls	Array of strings; required	1–100 HTTP(S) URLs; each URL at most 2,048 characters. The JSON body is limited to 256 KiB.
drip_enabled	Boolean; optional	Default false. True processes the first URL now and schedules the rest.
drip_interval	Integer minutes; optional	Default 60. The API bounds the interval to 1–10,080 minutes.

Export QUICKINDEXING_API_KEY in your server environment before using the example below. Replace the example batch key once for each intentional batch; persist that key and the exact payload before sending.

curl 'https://quickindexing.com/api/v1/indexing/submit' \
  --request POST \
  --header "X-API-KEY: $QUICKINDEXING_API_KEY" \
  --header 'Content-Type: application/json' \
  --header 'Idempotency-Key: example-batch-20261023-001' \
  --data-binary '{"urls":["https://example.com/page-one","https://example.com/page-two"],"drip_enabled":false}'

Illustrative immediate-processing response, not a live result:

{
  "success": true,
  "data": {
    "submitted_count": 2,
    "pending_count": 0,
    "total_processed": 2,
    "remaining_credits": 98,
    "message": "2 link(s) processed successfully."
  }
}

Some accepted URLs can remain in pending_count. Drip responses also report scheduled work through drip_scheduled. Review the returned counts and validation details rather than assuming every input string was accepted. None of these counters means “indexed by Google.”

Exact duplicate valid URLs within a request are charged once. Separate intentional requests can charge again. Drip work reserves credits for all valid unique URLs up front. Use the batch checklist before sending a large workload.

GET /credits

This read-only endpoint does not charge credits and needs no request body.

curl 'https://quickindexing.com/api/v1/credits' \
  --header "X-API-KEY: $QUICKINDEXING_API_KEY"

Illustrative response:

{"success":true,"data":{"credits":98}}

Idempotency and safe retries

Idempotency-Key is optional for backwards compatibility and recommended for submissions. Use 16–128 letters, digits, dots, underscores, colons or hyphens. Save the key with the exact JSON bytes.

• After a timeout, reuse the same key and body. A completed request can replay its original response without a second charge.
• Changed body bytes with the same key return 409. An unfinished request can also return 409 and may need support review.
• A validation failure consumes the key; use a new key for corrected input.
• Without an idempotency key, a retry is a new submission and can charge again. Do not automatically retry a 500 with a new key.
• Replayed balance values are snapshots. Use GET /credits for a fresh balance.

After authentication and request admission, submission responses include X-Request-ID. Keep it for support. Early authentication and validation failures may not include it. Rate limits are configurable and apply per IP; both endpoints share the rate limit. On 429, wait for Retry-After.

Error handling

HTTP outcomes and next actions

Status	Meaning and action
400	Invalid input, too many URLs or malformed idempotency key. Correct the input before making a new intentional request.
401	Missing or invalid API key. Check API Access; do not put the key in your support message.
402	Insufficient credits. Check the balance and available packages.
405	Wrong method. Use POST for submission and GET for credits.
409	Idempotency conflict or unfinished request requiring review. Retain the original key/body and contact support when unresolved.
413	Body exceeds the size limit. Reduce the batch payload.
429	Rate limited. Wait for Retry-After instead of sending more concurrent requests.
500	Server error or submission requiring review. Do not force a new charged submission with a fresh key.
503	Request storage unavailable. Retry later with the original key and body.

Errors can contain an error object with a code and message; some rate-limit responses use a string. Check the HTTP status before assuming a success response shape.

Scope and support

This is the QuickIndexing customer API, separate from Google's content-restricted Indexing API. There is no public Google indexing-status lookup endpoint in this reference. Review integration guidance and contact support with a request ID and redacted error details when needed.

By QuickIndexing · Reviewed 23 October 2026