> For the complete documentation index, see [llms.txt](https://connect.socios.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://connect.socios.com/partner-web-app/integration.md).
# Integration
Integrating the Socios.com Partner Web App
You can seamlessly incorporate our Partner Web App into your website.
To achieve this, you must use this Partner URL:
```url
https://app.socios.com/partner/[PARTNER_ID]?partnerWebAppId=[PARTNER_ID]
```
An example URL would be the one from the Bern football club [BSC Young Boys](https://www.bscyb.ch/):
{% code overflow="wrap" fullWidth="false" %}
```url
https://app.socios.com/partner/5796d2d6-da2a-4914-82fe-3eeaba3c1bca?partnerWebAppId=5796d2d6-da2a-4914-82fe-3eeaba3c1bca
```
{% endcode %}
You can retrieve the `Partner ID` you want by browsing on app.socios.com and looking for the specific partner detailed page. The id will be located after `/partner/` in the URL.
They designed the integration to look like this:
Try it for yourself:
## Web integration
You can insert the Partner Web App into an iframe for a responsive website.
The necessary HTML code is:
{% code overflow="wrap" %}
```html
```
{% endcode %}
### **SEO Optimisations**
Here are two ways to improve the findability of your Fan Token page from search engines:
* Fill the `` HTML tag with "\[Partner shortname] Fan Token", so that it appears clearly in the browser tab. \
For instance, for Apollon Limassol fan token: `<title>APL Fan Token`
* Make sure to mention this string in the URL of the page. \
For instance:
## Mobile integration
For mobile apps, you can create a native WebView using the following URL:
```url
https://app.socios.com/partner/[PARTNER_ID]?partnerWebAppId=[PARTNER_ID]
```
This way the web app will be seamlessly implemented within your mobile app. It can work on both native or hybrid mobile app.
Of course, building a native WebView requires much more work than just using this URL -- starting with the fact that a native implementation will require you to develop it twice (iOS + Android).
See for instance how French rugby club Stade Français did it:
---
# 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://connect.socios.com/partner-web-app/integration.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.
