For each request, you will need a session Id, which is obtained via a Login request.

After using a login-request to obtain a session-id, the API can be used to search, open tickets, request Analytics and statistics information, and more.

The following sections of the document will walk you through sending and receiving the various types of requests supported by the API.

For more information and answers, please consult our Nanorep on our website.

Note:All implementation of the Nanorep API requires the placement of the Nanorep logo, or the text 'powered by Nanorep' in a clear location next to the user UI, unless specifically authorized in writing by Nanorep.

Logging in – Creating a Session

The Login-Request provides you with a new unique session-id which is required for sending queries to the system. Any attempt to use an invalid session-id will result in a 400 BAD REQUEST response from the server, which is common with session expiration occurring after an idle timeout, so implementers should be prepared to handle these errors and send a new Login-Request before resuming sending queries.

if non-zero, login is successful. Otherwise, Message will contain info regarding the failure.

sessionIdleTimeout

Specifies the maximum time in seconds a session can stay idle before it is expired on the service. When a session is expired you will be required to send a new login request to obtain a new session-id.

Note: Using an expired session-id will result in an error code 400 response,after which you can send a new login-request