Loading…

Features Pricing

Log in Get started

Idempotency

Idempotency

Concepts

Idempotency means performing an operation multiple times produces the same result as performing it once. Idempotent operations are safe to retry: if a request fails or times out, retrying with the same idempotency key avoids duplicate processing.

When Idempotency Matters

Upload — Retrying document upload with the same idempotency key avoids duplicate documents
Extraction — Re-running extraction with the same inputs returns the same outputs
Webhooks — DocLD may retry webhook delivery; your handler should be idempotent (e.g., deduplicate by event ID)

Related Concepts

Idempotency enables safe retries for API calls and webhook handlers. Jobs and batch processing benefit when operations are idempotent.

Related terms

API
Job
Webhook

Frequently Asked Questions

Idempotency means performing an operation multiple times produces the same result as once. Idempotent operations are safe to retry without duplicate processing.

Retries (e.g., after timeout or rate limit) should not create duplicate documents or duplicate webhook handling. Use idempotency keys for uploads and deduplicate webhook events by event ID.

Pass an idempotency key (e.g., your internal document ID) in the request. DocLD can use it to avoid creating duplicate documents on retry.

Each event has a unique ID. Store processed IDs and skip or ignore duplicates if you receive the same event more than once (e.g., retries).

Running extraction twice on the same document produces two job IDs and two result sets. Idempotency keys for extraction may be supported; check the API.

Reusing a key within the idempotency window typically returns the same result as the first request. Key scope and window are documented in the API.

Support may vary by endpoint. Upload and other mutating operations are the most important for idempotency; check the API reference.

Keys are typically valid for a short window (e.g., 24 hours). After that, the same key may be treated as a new request.

DocLD may expect a specific header (e.g., Idempotency-Key). Use the header name and format documented in the API.

See the DocLD documentation and glossary for details, and check the API reference for related endpoints and options.

On this page

When Idempotency Matters
Related Concepts
Frequently Asked Questions

Product

Features
Pricing
API Reference

Industries

Insurance
Construction
Professional Services
Finance
Energy & Utilities
View all

Company

About
Careers

Resources

Documentation
Blog
Help Center
Status

Legal

Privacy Policy
Terms of Service
Trust

Connect

X
GitHub
Discord

© 2026 DocLD, Inc.SOC audit in progress