Plans and history
What a customer's plan allows your integration to read, how much history a key reads, and how to react when the plan changes.
Every customer key is tied to one Vitruve organization and to its plan. Vitruve checks the plan on every request, without caching, so what a key can do follows the customer's subscription in real time.
Which plans include integrations
Export integrations are included in the Elite and Professional plans, and during a trial. A customer on any other plan cannot create a key for you, and an existing key answers 403 once the organization moves to a plan without them.
How much history a key reads
All of it. Every plan that includes integrations reads the customer's whole history: a list returns everything from the from you ask for, and any workout answers on detail, however old.
When the plan changes
| What happened | What you see | What to do |
|---|---|---|
| The plan no longer includes integrations, the trial ended, or a paid subscription ended more than 30 days ago | 403 Your plan no longer includes API access | Pause the customer and tell them. The same key works again as soon as the plan is restored: check it at most once a day. |
Plan changes take effect on the next request. When an Elite or Professional subscription ends without renewal, the key keeps working for a 30-day grace period after the end date; a trial stops on its end date. There is no webhook.
What a key never exposes
Partner access is read-only: any method other than GET answers 405 Method not allowed, and a customer key never creates, changes or deletes data. Passwords, credentials and raw device payloads are never returned, and a key never reaches another organization: ids from another customer answer 404, as if they did not exist.