Access logs

On the left navigation panel, under the Account menu, click on Access Logs to review user access.
The user access is provided w.r.t. API gateway. The front end UI of the platform is built on the same API gateway to which users fire API calls. The Access Logs display action by users for the account along with the response for the API call.
Basic table features
  • Search: by entering the email of the user or URL
  • Filtering/Sorting: the table allows filtering/sorting where applicable and resetting of the filters
  • Column selection: select the columns to be displayed
  • Pagination: select how many rows of data should be displayed & navigate multiple pages
The HTTP method & the URL indicate whether the user was viewing or making actions of a certain type on the platform. The HTTP methods are filterable between GET, POST, PUT, PATCH and DELETE.
The Status codes are summarised below.
Status Code
200 OK
When request succeeded for a GET or POST request
201 Created
When request has been fulfilled and resulted in a new resource being created (e.g. when a new user added to the account)
202 Accepted
When a request accepted for a POST that will be completed asynchronously
301 Moved Permanently
When a request is placed in a URI without final forward slash
400 Bad Request
When a request is wrongly format (e.g., incorrect request body)
401 Unauthorised
Missing credentials
403 Forbidden
Incorrect credentials
404 Not Found
When resources are not found
405 Method Not Allowed
When request uses wrong method (e.g., change_status action using GET)
409 Conflict
Indicates that the request could not be processed because of conflict in the request (e.g., object already created)
413 Payload Too Large
Indicates that the request entity (body) is larger than limits defined by server
415 Unsupported Media Type
When request uses wrong content type (e.g., application/xml)
429 Too Many Requests
When a user exceeds the maximum number of requests. Check the Throttling section for more information.
500 Internal Server Error
When there are unexpected server side conditions
503 Service Unavailable
Temporary unavailability of the service