Sign-in and results
Initialize first, keep the returned session ID, then call the appropriate sign-in endpoint. Check the success field and message documented for that endpoint before allowing protected actions.
Each response belongs to one request. A successful initialization does not mean the customer’s license has been accepted. Read the sign-in response separately.
When calling the API yourself, handle both an HTTP failure and a valid JSON response that rejects access. A timeout is not a successful response and should not be shown as a ban without a server decision.
No V1 SDK method names are invented here. Use the source distributed with your existing V1 application or the endpoint examples in API Reference.

