Tweet
I've just been implementing interactive login via API, and noticed an inconsistency in the responses between that and the non-interactive (certificate-based) login. In the hope that it will save someone half an hour debugging somewhere along the line, the session token is returned as 'sessionToken' in the non-interactive version and 'token' in the interactive version. I knew it was 'token' in the keepAlive function, but assumed it would be consistent across both login functions - silly me :-)
Forgot
User Name
/
Password
?