> For the complete documentation index, see [llms.txt](https://chekin.gitbook.io/chekin-public-api/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://chekin.gitbook.io/chekin-public-api/faqs/hosts-sdk.md).

# Hosts SDK

* **How new Chekin account creation would work through Host SDK? Would it be done automatically?**\
  \
  Accounts should be created by partner's system trough our *Account Creation API*.\
  Each of the partner customers, should have their own API token and SDK API Key.<br>
* **Would Host SDK automatically generate API key in the Chekin dashboard to connect Guest SDK? Or this step would need to be done manually still?**\
  \
  Partners system should generate both SDK API Keys, for each host.\
  It can be done via API: [API Key for SDK](/chekin-public-api/chekin-embedded-sdks/api-key-for-sdk.md)<br>
* **Does Host SDK collect Police portal logins?**\
  \
  Host SDK will help host configuring the connection between Chekin (in white label in your system) and the authorities portals on partners side, so no need to jump in Chekin for this.\
  PMSs usually add this on the property/listing set up adding a section that will request the extra and mandatory fields depending on each listing location.\
  Partners won't need to understand the logic on each region as that will change depending on the location of each listing.<br>
* **How it works if the client has multiple logins of different property owners?**\
  \
  No problem for that, through Host SDK per each property in PMS a different configuration can be done, meaning that property 1 e.g. can be set to send guests data to one authority portal login and property 2 to another one.<br>
* **What information or documents are needed for this Police portal connection?**\
  \
  Through the host SDK login information to authorities portals needed will adapt automatically depending on the country where property is based; usually it is requested to add the username and the password of the login to portal authorities, sometimes also to select from a dropdown menu that retrieves properties list from the authority portal account of the host the right property (e.g. when a host may have more than 1 property registered under the same authority portal account).<br>
* **How it works if new property owners is onboarded and, for example, new portal login is needed?**\
  \
  Simply through the Host SDK in your listing configuration (if you will launch it there), the host will have the chance to configure the connection to the authority portal for the new unit too, no matter if this has been added after the initial configuration of units he started with.<br>
* **How it works if new listings are added?**\
  \
  Partner can create them via API in Chekin system [Create Housing](/chekin-public-api/api-reference/housings/create-housing.md)\
  After that, the property will be available in Hosts SDK for configuration of authorities.<br>
* **In general, how Host SDK work with Guest SDK?**\
  \
  Host SDK is for propety settings, police connection and legal documents. It should be included in Partner's Hosts portal.\
  Guest SDK is for Check-in online experience: Collecting guest data, Identity verification, Remote Access, payments.. It should be included in Partner's Guest portal.<br>
* **What are the best implementation practices from your experience?**\
  \
  I suggest to build the integration in your side, creating properties and reservations. This way you will have control of everything, get quicker results and having a better performance.

  Integrate the Host SDK, just the "single property settings view" inside the PMS listing configuration view.