Glossary and support
Find definitions and prepare a safe support request.
On this page
Use these terms consistently when reading results or discussing an integration.
Core terms
| Term | Meaning |
|---|---|
| Account | The owner of applications and data. |
| Application | Calling software attributed to one account. |
| Key | A secret credential for an application, not a human login. |
| Workspace | An authorized boundary for business work. |
| Operation | One immutable, authorized intent and its lifecycle. |
| Artifact | A durable result, with a version and ownership. |
| Evidence | A source-backed observation with provenance and time. |
| Hypothesis | A modeled or proposed conclusion, not an observed fact. |
State language
Draft is not launch. A route is not dispatch. Proof submitted is not proof accepted. Accepted proof is not settled earnings or a completed payout. An exported file is not a destination publication. A successful authentication check is not business access.
Support
Start with errors and troubleshooting and the article for your intended outcome. Use the public contact page for help, with safe metadata and a clear symptom.
Do not send secrets, verification codes, private recordings or raw customer evidence. A support request is not approval to charge, repair historical data, resume work or contact a third party.
Documentation feedback
Name the page and describe what was unclear. A published guide can be corrected independently of a runtime release; its last-reviewed date is not a production verification timestamp.