Availability
A public API is not available yet
DNventory does not currently issue API keys or accept third-party requests. Your portfolio remains accessible through the DNventory application.
Developer access, when it is ready
API availability
DNventory does not offer a public API today. Learn what is available now and how future access will be announced.
0.20 compatibility
RDAP-assisted intake is application-only
Single-entry provenance and resilient per-row lookups use the existing authenticated, CSRF-protected application helper. It is not a public endpoint, creates no third-party API contract, and does not change existing API availability.
Move your data
Use imports and exports today
Bring portfolio records into DNventory with CSV preview and validation, then export portfolio, renewal, financial, payment-plan, and restriction reports whenever you need them.
Future access
Designed for useful integrations
Future developer access may include carefully scoped portfolio, watchlist, and reporting capabilities. Privacy and workspace boundaries will remain part of the contract.
Stay informed
Follow product updates
Public API availability, documentation, and compatibility details will be announced on the Updates page before access opens.
0.21 compatibility
Automatic appraisals are application-only
Starting, reviewing, accepting, and approving automatic appraisals requires an authenticated DNventory workspace and is not part of the public API. Provider credentials, normalized evidence, quotas, and appraisal results are never exposed through a public endpoint.
0.22 compatibility
The internal model remains application-only
Market snapshot administration, internal estimates, evidence acceptance, and working-value approval remain authenticated application workflows. Release 0.22 adds no public endpoint and does not change the public API contract.
0.23 compatibility
Provider governance remains application-only
Canonical registrar, DNS, and parking selection, Other-provider suggestions, and administrator review do not add a public endpoint or change the public API contract.
0.23.1 compatibility
In-place folder saves remain private
Asynchronous portfolio organization uses the existing authenticated, CSRF-protected application route. It adds no public endpoint and does not change the public API contract.
0.23.2 compatibility
Canonical folder saves remain private
The corrected in-place organizer posts only to the authenticated Portfolio route. It adds no public endpoint and does not change the public API contract.
0.24 compatibility
UX preferences remain application-only
Saved portfolio views, personal review-triage decisions, report navigation, and responsive controls use authenticated application routes. Release 0.24 adds no public endpoint and does not change the public API contract.
0.24.1 compatibility
Folder rail behavior remains private
The corrected collapse and expand control is a client-side Portfolio refinement. It adds no endpoint and does not change the public API contract.
0.24.2 compatibility
Watchlist action menus remain private
The hardened More menu is a client-side Watchlist refinement. It adds no endpoint and does not change the public API contract.
0.25 compatibility
Tag workflows remain application-only
Creating, assigning, filtering, bulk-editing, archiving, and restoring workspace tags use authenticated application routes. Release 0.25 adds no public endpoint and does not change the public API contract.
0.26 compatibility
Portfolio downloads remain application-only
Filtered Portfolio CSV downloads are generated by the authenticated member application and preserve workspace boundaries. Release 0.26 adds no public endpoint, API key, or third-party response contract.
0.27 compatibility
Auction tracking remains application-only
Watch reasons, auction episodes, marketplace suggestions, deadline reminders, and outcome actions use authenticated workspace routes. Release 0.27 adds no public endpoint, API key, or third-party response contract.
0.28 compatibility
Email delivery remains application-only
Email verification, personal delivery preferences, signed unsubscribe actions, digest scheduling, and delivery operations are authenticated application workflows. Release 0.28 adds no public API endpoint or API credential.
0.28.1 compatibility
Watch email batching remains application-only
Consolidating related watch changes affects only the private notification and email-delivery pipeline. Release 0.28.1 adds no public endpoint, API credential, or response-contract change.
0.29 compatibility
Live portfolio search remains application-only
Portfolio and Watchlist filtering runs inside the authenticated workspace with a server-rendered fallback. Release 0.29 adds no public endpoint, API credential, or response-contract change.
0.30 compatibility
Auction entry remains application-only
Notification status changes, auction URL assistance, marketplace suggestions, and timezone conversion use authenticated workspace routes. Release 0.30 adds no public endpoint, API credential, or response-contract change.
0.30.1 compatibility
Inbox and timezone presentation remain private
Notification inbox filtering and wider auction-timezone controls are authenticated interface refinements. Release 0.30.1 adds no public endpoint, API credential, or response-contract change.
0.31 compatibility
Workspace Connections remain application-only
Cloudflare OAuth authorization, optional API-token fallback, synchronization, provider snapshots, reconciliation, and provider-only imports use authenticated workspace routes and a protected CLI worker. Release 0.31.8 carries the tenant-scoped connection ID through every connection action without adding a public API endpoint, API key, or response-contract change.
0.32 compatibility
GoDaddy Connections remain application-only
Workspace-managed GoDaddy Personal Access Tokens, Domains v3 synchronization, nameserver evidence, credential replacement, and reconciliation use authenticated application routes and the existing protected Connections worker. Release 0.32 adds no public endpoint, public API credential, or response-contract change.
0.32.1 compatibility
Canonical reconciliation remains application-only
Provider aliases and label-equivalent reconciliation decisions remain private workspace behavior. Release 0.32.1 adds no public endpoint, API credential, or response-contract change.
0.33 compatibility
Dynadot Connections remain application-only
Workspace-owned Dynadot API keys, HMAC request signing, REST v2 synchronization, source evidence, credential replacement, and reconciliation use authenticated application routes and the protected Connections worker. Release 0.33 adds no public endpoint, public API credential, or response-contract change.
0.34 compatibility
Porkbun Connections remain application-only
Workspace-owned Porkbun API keys, API v3 synchronization, permitted nameserver evidence, credential replacement, and reconciliation use authenticated application routes and the protected Connections worker. Release 0.34 adds no public endpoint, public API credential, or response-contract change.
0.35 compatibility
Internal Model 2.0 remains application-only
Name classification, robust aggregate blending, liquidity guidance, snapshot administration, evidence acceptance, and working-value approval remain authenticated DNventory workflows. Release 0.35 adds no public endpoint and does not change the public API contract.
0.36 compatibility
Registry Desk is presentation-only
Registry Noir 4.0 changes navigation grouping, responsive composition, motion, and interaction feedback without adding a public endpoint or changing authentication, routes, payloads, workspace boundaries, or response contracts.
0.36.1 compatibility
Application polish does not change the API
The corrective Registry Desk pass changes authenticated CSS, responsive composition, and progressive interaction feedback only. It adds no public endpoint and changes no authentication requirement, route, request or response payload, workspace boundary, or compatibility contract.
0.37 compatibility
Workbench workflows remain application-only
Portfolio and Watchlist pagination, live search, sorting, inline appraisal review, provider branding, and bulk connection reconciliation use authenticated application routes. Release 0.37 adds no public endpoint, API credential, or response-contract change.
0.38 compatibility
Watchlist organization remains application-only
Independent Watchlist folders, saved views, column and density preferences, deterministic auction sorting, and bulk connection reconciliation use authenticated workspace routes and the primary database. Release 0.38 adds no public endpoint, API credential, or response-contract change.
0.38.1 compatibility
Editor and appraisal fixes do not change the API
Watchlist editor containment, numeric aggregate-keyword handling, bounded provider retries, safe failure references, and stale appraisal-run recovery remain authenticated application and worker behavior. Release 0.38.1 adds no public endpoint, API credential, request payload, response contract, or database migration.
0.38.2 compatibility
Responsive workbenches do not change the API
Earlier rail compaction, adaptive folder placement, filter reflow, contained tables, and tablet cards are authenticated presentation behavior. Release 0.38.2 adds no public endpoint, API credential, request payload, response contract, or database migration.
0.38.3 compatibility
Rail and listing preferences remain application-only
The saved member-rail width and container-responsive Watchlist presentation are authenticated browser behavior. Release 0.38.3 adds no public endpoint, API credential, request payload, response contract, database field, or migration.
0.38.4 compatibility
Watchlist table sizing does not change the API
Full-width desktop column distribution and action placement are authenticated presentation behavior. Release 0.38.4 adds no public endpoint, API credential, request payload, response contract, database field, or migration.
0.39 compatibility
Mobile workflow composition does not change the API
Phone folder disclosures, scan-first cards, Settings navigation, and owned-domain section controls are authenticated presentation behavior. Release 0.39 adds no public endpoint, credential, request payload, response contract, database field, or migration.
0.39.1 compatibility
Mobile layout correction changes no API contract
Compact registry-ledger rows, full-width Settings and domain records, and responsive disclosures are presentation-only. No public endpoint, authentication requirement, request payload, response contract, database field, or migration changed.
0.39.2 compatibility
Signal-first mobile tickets remain application-only
Portfolio and Watchlist ticket hierarchy, stable live-search pairing, responsive disclosures, and mobile interaction states are authenticated presentation behavior. No public endpoint, authentication requirement, request payload, response contract, database field, or migration changed.
0.39.3 compatibility
Timing and workbench corrections change no API contract
UTC auction countdown interpretation, Watchlist return-context preservation, archive alert cleanup, desktop table containment, and Overview wording are authenticated application behavior. No public endpoint, authentication requirement, request payload, response contract, database field, or migration changed.
0.39.4 compatibility
Adaptive tables and confirmation polish are presentation-only
Content-aware Portfolio and Watchlist column allocation, earlier folder-rail reflow, and the clearer confirmation-dialog heading affect authenticated application presentation only. No public endpoint, authentication requirement, route, request payload, response contract, database field, worker, or migration changed.
0.39.5 compatibility
Public contact pages add no API contract
The marketing Contact and Thank you routes are static presentation surfaces. The Contact form intentionally uses a placeholder action and has no delivery handler, storage, email workflow, authentication requirement, or public API endpoint.
0.39.6 compatibility
Contact delivery remains outside the public API
The public Contact form now posts from the visitor's browser to the approved FormBastion endpoint. DNventory adds no contact endpoint, authentication requirement, request or response contract, message storage, mail worker, database field, or migration.
0.39.7 compatibility
Contact form simplification changes no API contract
Removing the public Contact form's _gotcha field changes only browser-submitted marketing markup. The FormBastion destination remains external to DNventory, and no public endpoint, authentication requirement, request or response contract, database field, worker, or migration changed.
0.39.8 compatibility
Enhanced browser protection remains outside the API
The public Contact page now prepares signed FormBastion browser attempts through the provider's client script. DNventory adds no public endpoint, API credential, authentication requirement, request or response contract, message storage, database field, worker, or migration.