---
order: 970
slug: "/docs/v1/help/previous-home"
title: "Previous Developer documentation reference"
section: "Help and notes"
description: "Preserved detailed reference from the earlier home page, including its unique explanations and examples."
audience: "all"
level: "beginner"
last_updated: "2026-10-17"
version: "v1"
related: ["/docs/v1/start/quickstart","/docs/v1/start/glossary"]
draft: false
layout: "reference"
---
Build your application with a clear licensing contract, starting with a tested [Sandbox](/docs/v1/start/glossary#sandbox) integration.

## What you will learn
- Find a first working [activation](/docs/v1/start/glossary#activation) and the right application architecture.
- Understand the credential and environment boundaries.
- Locate current references, examples and support without an account.

## Prerequisites
- No account is needed to read documentation or use its browser search.
- To execute requests, create a verified Sandbox workspace and test [license](/docs/v1/start/glossary#license).
- See [how to read, search and export these docs](/docs/v1/documentation).

## Start here
:::cards
- [Quickstart in five minutes](/docs/v1/start/quickstart)
- [Choose your application path](/docs/v1/start/choose-your-path)
- [Understand core concepts](/docs/v1/start/core-concepts)
- [Check known SDK limitations](/docs/v1/integration-notes)
:::
Press Ctrl+K or Command+K to search published sections. Search is local to your browser; no account or external search service is required. Without JavaScript, use the sidebar and browser Find.

## Popular pages
- [Authentication and secret handling](/docs/v1/start/authentication)
- [Sandbox versus Live](/docs/v1/start/environments)
- [License lifecycle](/docs/v1/start/license-lifecycle)
- [Activation, validation and deactivation](/docs/v1/start/activation-validation-deactivation)
- [Go live checklist](/docs/v1/start/go-live-checklist)
- [Alphabetical glossary](/docs/v1/start/glossary)

## API reference
The API uses the hosted /api/v1 base path. Begin with [credential selection](/docs/v1/start/authentication#headers-and-environment) and [request flow](/docs/v1/start/activation-validation-deactivation).
These foundation pages explain actual behaviour; they are not an exhaustive endpoint reference. Only complete pages are linked. Do not treat an authenticated legacy export as a substitute for the disclosed compatibility notes.

## SDKs
Four [official SDKs](/docs/v1/start/glossary#official-sdk) share the activation contract:
- [Python 3.9+ setup](/docs/v1/start/quickstart#python-setup)
- [JavaScript: Node.js 18+ / Electron main](/docs/v1/start/quickstart#javascript-setup)
- [PHP 8.2+ setup](/docs/v1/start/quickstart#php-setup)
- [C# / .NET source setup](/docs/v1/start/quickstart#csharp-setup)
Other languages can use HTTPS and JSON. The [cURL transport check](/docs/v1/start/quickstart#curl-setup) is not a complete signature verifier. Consult [runtime and storage limitations](/docs/v1/integration-notes#runtime-and-storage) before production.

## Guides
Choose [desktop](/docs/v1/start/use-cases#desktop-application), [SaaS backend](/docs/v1/start/use-cases#saas-backend), [CLI](/docs/v1/start/use-cases#cli-or-developer-tool) or [plugin/extension](/docs/v1/start/use-cases#plugin-or-extension).
Your own sales backend handles software-buyer payments. Stripe and Mollie in KDPika checkout bill your [platform subscription](/docs/v1/start/glossary#platform-subscription), not those purchases.

## Changelog
2026-10-17: foundation guides, a glossary, annotated flow diagrams and executed online quickstarts are published.
2026-10-15: public documentation adds local section search, Markdown exports, themes and privacy-conscious feedback.
These entries describe documentation changes, not software releases, certifications or uptime guarantees.

## Support
Email [hi@kdpika.com](mailto:hi@kdpika.com) for help. Include your runtime, environment and a [request ID](/docs/v1/start/glossary#request-id) where available; remove passwords, tokens and private [customer](/docs/v1/start/glossary#customer) information. [Platform status](/status) shows recorded health information.
Use the feedback form on a page to explain unclear documentation. It is not a private account-support channel.

## Expected result
You can find the first activation, the relevant architecture and current limitations while signed out.

## Common mistakes
- Looking for buyer payment checkout in a licensing guide: your sales flow is separate.
- Treating a listed runtime minimum as a current vendor support guarantee.
- Assuming an unpublished guide or unsupported capability exists.

## Security notes
Do not paste credentials into search, feedback or issue-report emails. Public exports contain documentation, not your account data.

## Troubleshooting
| Symptom | Cause | Fix |
| --- | --- | --- |
| Search has no match | The term is absent from published content | Try a shorter phrase or browse the topic |
| A future guide is not visible | Only completed content is public | Use the available foundation or contact support |
| Cannot execute activation | No test license or SDK setup | Follow the quickstart in order |

## Next steps
Start with [introduction](/docs/v1/start/introduction), or run the [quickstart](/docs/v1/start/quickstart).

## Related
- [Documentation interface](/docs/v1/documentation)
- [Integration limitations](/docs/v1/integration-notes)
- [Public privacy notice](/legal/privacy)