@reductoai/docx and @reductoai/docx-editor carries your organization’s license. You get it when you install with an install token from Studio. You do not call any license code. The package does two things in the background:
- It checks your license. The first document opens only after a good check. After that, the package checks about every hour in the background, and each good check keeps it working for the next 65 minutes.
- It reports Sessions. A Session is one document in use for up to 60 minutes. Reducto bills you per Session.
What you set up
Set up shows each step.
Terms
A Session here is a billing unit. It is not
DocxSession, the editing type in the API reference.What you pay for
You pay once per Session. A Session starts when you open or create a document, in code or in an editor. Work on the same document in the next 60 minutes is part of that Session. If you save the file and open it again in those 60 minutes, on any machine, it stays in the same Session. A compare or a combine of two documents counts as one Session. Sessions and billing gives examples.When the package stops
The package stops only in these cases. Each call then throws aReductoLicenseError.
Reducto does not cap the number of Sessions, and the package never slows down because of it. It stops only when usage reports cannot be delivered (
undelivered above).
Next steps
- Set up: install, API key and browser proxy
- Sessions and billing: what counts as a Session
- License checks: when the package checks and what happens offline
- Troubleshooting: errors and warnings
- What the package sends: data and encryption, for your security review
- Check protocol: retry timing and request bodies