Before you start
You need access to manage API users in SiteLink Corporate Control Center. A dedicated API user, the correct API password and rights to each location are all required.
Step 1 / Open Corporate Control
Sign in to Corporate Control Center
Log into SiteLink Corporate Control Center with an account that can create API users and manage security rights.
Open Setup → Websites, Kiosks, and Call Center → Permissions: API Users and Rights. In some layouts, you may find this under Corporate Control → API Users and Rights. If you cannot see the option or edit users, ask your SiteLink administrator to complete the setup.
Step 2 / Create the API user
Create a dedicated API user
Choose Add to create an API user for StorIQ. We normally use StorIQ as the username so you can identify the integration later.
Set the password for this dedicated API user in the Password and Confirm Password fields. This is the API / Call Center password we need, not your normal SiteLink login password. Sending a regular staff login password instead of this API user’s password can cause the connection to be rejected.
Save the API username and API password. Keep the password private and use the secure sharing method agreed with your StorIQ contact.
Use the API / Call Center password, not your normal SiteLink login password.
Step 3 / Enable API rights
Enable API rights, except API Admin
For StorIQ’s setup, we request all available API rights except API Admin. This applies to the API permissions, not every administrative permission in SiteLink.
On the permissions screen, these include API Aggregator, API All Reports, API Insurance Reports and API Regular. Leave API Admin unchecked. If your security policy requires narrower access, ask your StorIQ contact to confirm the selection before saving it.
What if we need to limit API permissions?
The core access needed includes API Regular and the TenantIDByUnitNameOrAccessCode and LedgersByTenantID API methods. The last two are API method names, not individual permissions checkboxes; SiteLink’s API access levels control the available methods. These alone are not a substitute for the full setup above or location security rights. Ask StorIQ to confirm the required permissions for your connection before using a narrower selection.
Do not grant API Admin access.
Step 4 / Grant location access
Grant security rights to each location
Assign this API user security rights to every SiteLink location you want connected to StorIQ. Creating the user and enabling API rights is not enough if the user has no access to the location itself.
Use All Sites if every location in the corporation should be connected. Otherwise, select the participating locations individually. Make sure the access matches the location codes you will send us, then save the user and rights changes.
An “insufficient security rights” error usually means the user is missing rights for the requested location.
Step 6 / Confirm the connection
We will check the connection
Once we receive the details, the StorIQ team will check the credentials and access for each requested location. If a location cannot be accessed, we will let you know what needs to be corrected.
Let your StorIQ contact know if you change the API password, remove user rights or add a new location later. Those changes can interrupt access or require the connection details to be updated.
Common setup issues
The API rejects the username or password
Confirm you sent the API username and API / Call Center password, not a regular SiteLink staff login. Check for extra spaces when copying the details. If the API password has changed, share the updated value securely with your StorIQ contact.
We see an “insufficient security rights” error
Open the API user’s rights and confirm access to the specific location code being requested. Enable the required API rights as well as security rights for that location, then save the changes. API permissions and location permissions both matter.
One location works, but another does not
Check that the second location is included in the API user’s permitted sites and that its corporation and location codes are correct. Keep any leading zeros. If the site belongs to a different corporation, ask your StorIQ contact to confirm the appropriate connection details for it.
If the issue continues, send your StorIQ contact the facility name, location code and exact error message. Remove passwords and tenant information from any screenshots.
SiteLink reference