feat: add support for NetBox 4.5+ v2 API tokens

NetBox 4.5 introduced v2 API tokens (nbt_ prefix) that require
Bearer authorization instead of Token. Auto-detect token version
by prefix and use the appropriate authorization header keyword.

- nbt_* tokens -> Authorization: Bearer <token>
- legacy tokens -> Authorization: Token <token> (backward compatible)

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: Daniil Svetlov

README.md

@@ -88,6 +88,8 @@ In order to updated data in NetBox you need a NetBox API token.
   * auth
   * secrets
   * users
+* Both v1 (legacy) and v2 tokens (NetBox 4.5+, `nbt_` prefix) are supported.
+  The correct authorization header (`Token` or `Bearer`) is detected automatically.
 
 A short description can be found [here](https://docs.netbox.dev/en/stable/integrations/rest-api/#authentication)
 

module/netbox/connection.py

@@ -152,8 +152,10 @@ def create_session(self) -> requests.Session:
         requests.Session: session handler of new NetBox session
         """
 
+        token = self.settings.api_token
+        keyword = "Bearer" if token.startswith("nbt_") else "Token"
         header = {
-            "Authorization": f"Token {self.settings.api_token}",
+            "Authorization": f"{keyword} {token}",
             "User-Agent": f"netbox-sync/{__version__}",
             "Content-Type": "application/json"
         }

settings-example.ini

@@ -45,6 +45,7 @@
 
 ; Requires an NetBox API token with full permissions on all objects except 'auth',
 ; 'secrets' and 'users'
+; Both v1 (legacy) and v2 (NetBox 4.5+, nbt_ prefix) tokens are supported.
 api_token = XYZ
 
 ; Requires a hostname or IP which points to your NetBox instance