Upgrade Guides
Check Your API Version
Before you start any API upgrade, you need to know which version your integration is currently targeting. This page walks you through how to find that information.
Search Your Source Code
Search your application's source code for the API version in two places:
- The
X-Accellion-VersionHTTP header value — this is the version explicitly sent on every request. - The
apiVersionquery parameter — an alternative supported on some endpoints.
bash
# Find the version header in your code
grep -r "X-Accellion-Version" ./src
# Find the apiVersion query parameter
grep -r "apiVersion" ./src
When the header is set explicitly, it looks like this:
check-version.sh
curl -s -H "Authorization: Bearer $TOKEN" \
-H "X-Accellion-Version: 28" \
"https://your-instance.kiteworks.com/rest/folders/top"
check_version.py
headers = {
"Authorization": f"Bearer {access_token}",
"X-Accellion-Version": "28", # ← this is what you're looking for
}
What's next
Once you know your current version, return to the upgrade guide that matches your migration path.
Update your OAuth 2.0 flow and token handling to comply with the v28 authentication requirements.
A full walkthrough of the breaking changes in v28 and the code updates required to migrate your integration.
How to update file and folder ID references from integer IDs to UUIDs in your integration code.