> For the complete documentation index, see [llms.txt](https://docs.zwapgrid.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zwapgrid.com/key-concepts/terminology.md). # Terminology This is the terminology you will find throughout the documentation and in your communication with us. | Term | Meaning | | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | The Client | You are The Client. You invite Your Customer to Consent to share data from their Accounting System. You can then consume this data using API.1. | | Your Customer | Your Customer can connect their Accounting Systems and share their data with The Client. | | Your Platform | The public-facing or internal software system(s) you develop and use within your organization. | | Consent | Consent is the link between Your Customer in Your Platform and the connection to their Accounting System through API.1. | | Consent ID | A Consent ID is a unique GUID generated when you create a Consent. You can then use it when inviting Your Customer to connect so that you can consume data using API.1. | | Accounting System | An Accounting System is a software system that helps organizations automate and manage accounting for optimal performance. | | Client Portal | This is where you can manage The Client - here you can manage the Onboarding Flow and API Key creation, for example. | | Onboarding Flow | This is the platform that Zwapgrid has developed to enable Your Customer to log in and connect to their Accounting System. | | API.1 | API.1 is the set of APIs that are used by The Client to access the data from the Accounting System that Your Customer uses. | | API Key | The API Key is your access to API.1 APIs. You create and manage API Keys in the Client Portal. | | One-Time Code | A unique code that is generated and used together with the Onboarding Flow, in order to ensure that only Your Customer can access a created Consent. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.zwapgrid.com/key-concepts/terminology.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.