---
slug: "/docs/v1/integration-guide/understand"
title: "Understand the idea"
description: "Stage 1: understand the idea with a clear outcome, verification steps and one next action."
section: "Integration Guide"
order: 16
audience: "all"
level: "beginner"
last_updated: "2026-10-20"
version: "v1"
related: []
draft: false
layout: "guide"
---
A [license key](/docs/v1/start/glossary#license-key) is like a ticket. Your software checks the ticket before allowing a protected [feature](/docs/v1/start/glossary#feature).
## What you will do
Understand the four actions without writing code.
An API is the HTTPS interface your program calls. An SDK is a ready-made client library that makes those calls and checks responses. A signed response includes proof that the server's access decision was not changed.
Customer buys → gets a license key → your app activates → your app checks access.
1. Your [customer](/docs/v1/start/glossary#customer) receives a key, manually or after a verified purchase.
2. **Activate** connects that key to one installation: one installed copy of your app.
3. **Validate** asks whether that installation still has access.
4. **Deactivate** releases its [device](/docs/v1/start/glossary#device) seat when moving to another computer.
A device seat is one allowed installation. An entitlement is a feature or limit, such as PDF export or two devices.
## Expected result
You can explain why receiving a key is not the same as permission to unlock a feature.
## If it does not work
If you only want to send keys, skip coding and use the non-programmer route in [Stage 12](/docs/v1/integration-guide/deliver).
## Stage checklist
- I know the difference between a key, an installation and a signed access decision.

## Next steps
[Continue to Stage 2: Set up your Sandbox](/docs/v1/integration-guide/sandbox)