Authentication

authenticate before making any requests to protected resources, you must authenticate using an email address and password to obtain an access token credentials to access api resources differ from user credentials for portal access excessive failed attempts will result in throttling post https //acme jomablue com/import/api/v1/auth/login properties property more email required the email address of the account with access to api resources password required the associated password example request example request body { "email" "myuser\@jomablue com", "password" "myverylongpassword" } example response example response body { "token" "eyj0exaioijkv1qilcjhbgcioijiuzi1nij9 " } token validity token validity is customisable for high risk applications, but has a default soft long lived setting of 1440 minutes at which point api requests will return 401 unauthorized the tokens expiry timestamp is encoded within the token if maintaining validity periods within your application is desired we highly recommend having an authentication workflow to request a new token if your current token becomes invalid and not simply rely on a manually obtained token and its lifetime jomablue reserves the right to revoke your token between feature releases if required the authentication endpoints will be immediately available so that you can obtain a new token rate limits this api is heavily rate limited to one request per hour due to the function of this being a method of obtaining data post event for archiving and the requests triggers a report generation process