> For the complete documentation index, see [llms.txt](https://docs.struct.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.struct.com/developer/app-store/app/app-connections/manage-connection/connection-details.md). # Connection details ## App connection name The name of the app connection. This is required to identify the connection. ## Subscription key Generate a subscription key, either manually or automatically. This key is required when installing the app on a tenant. ## Connection status A short description that displays the current status of the connection, including when it was last modified and by who. The number of revisions for the connection is also shown. ## Extension point Extension points define where your app integrates with Struct PIM. You can view and add the extension points you want to use for the app. These act as integration points between your app and the PIM. Most fields are locked and cannot be changed here, as they are defined at [version](/developer/app-store/app/app-versions/manage-version/version-details.md) level ### Label Enter a label for the extension point which will be shown in the UI. ### Key A key that cannot be changed is generated from the type and label upon creation of the extension point. It is used to match extension point across versions during upgrades. ### Description A description used to describe the extension point. ### Type [Extension point types](/reference/settings/integration/apps/apps-details/extension-points/extension-point-types.md) define where the app will be shown inside the PIM. You can setup multiple extension points, but they can only have one extension point type. ### Embed URL The URL where the app fetches its data from and renders its content within Struct PIM. You can use '@' to insert context values such as slug, user, and language, allowing the app to adapt dynamically to the current context. {% hint style="info" %} Depending on the extension point type, the context options entity type and internal ID may be available. {% endhint %} --- # 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.struct.com/developer/app-store/app/app-connections/manage-connection/connection-details.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.