Skip to content

Troubleshooting SIA API's

This document will provide instructions for how to troubleshoot logs to answer API related issues.

/authenticate

Prerequisites

Need to ask customer for the following: 1) Timestamp - must

401 error

Search the sia-service logs at the specific timestamp: There you can see reasons:

Results:

Incorrect password or username for user: [[username]]

bad credentials 

Customer not found for username: [[username]]

missing customerId in header 

customerEntity null retrieved for customerId [[invalidCustomerId]]

bad customerId provided

400 error

Search the sia-service logs at the specific timestamp: There you can see reasons:

Results:

400 BAD_REQUEST "Required header 'customerId' is not present."`
missing customerId in header

400 BAD_REQUEST "Required header 'customerId' is not present."

missing customerId in header

username: must not be blank;

username is missing in body 

password: must not be blank;

password is missing in body

/transaction-multisecure

Prerequisites

When customer/individual complains about API issue need to ask for the following: 1) Original request (body+headers) - Optional 2) Response status code - must 3) Timestamp - must

401 error

Search the sia-service logs at the specific timestamp.

Results:

Signature validation failed. JWT signature does not match locally computed signature. JWT validity cannot be asserted and should not be trusted.

bearer token is invalid 

customerEntity null retrieved for customerId [[customerId]]

bad customerId provided

400 error

Search the sia-service logs at the specific timestamp.

Results:

msisdn: msisdn cannot be empty;

msisdn is empty 

msisdn: numeric value out of bounds (<20 digits>.<0 digits> expected);

msisdn is not valid

cbUrl: cbUrl cannot be empty;

missing callback url 

cbUrl: must be a valid URL;

callback url must be valid

requestId: requestId cannot be empty;

requestId is missing or empty 

message: Message must not be empty. Maximum length is 220 characters or 110 characters if it contains special characters; message: must not be null;
message is missing, empty or too big

400 BAD_REQUEST "Failed to read HTTP message"

in this case, request body is mandatory. can be because of textInputType > enum size. or other parameters that we don't explicitly check

/transaction-touch

Prerequisites

When customer/individual complains about API issue need to ask for the following: 1) Original request (body+headers) - Optional 2) Response status code - must 3) Timestamp - must

401 error

Search the sia-service logs at the specific timestamp.

Results:

Signature validation failed. JWT signature does not match locally computed signature. JWT validity cannot be asserted and should not be trusted.
bearer token is invalid 
customerEntity null retrieved for customerId [[customerId]]
bad customerId provided

400 error

Search the sia-service logs at the specific timestamp

Results:

msisdn: msisdn cannot be empty;
msisdn is empty 
msisdn: numeric value out of bounds (<20 digits>.<0 digits> expected);
msisdn is not valid 
cbUrl: cbUrl cannot be empty;
missing callback url 
cbUrl: must be a valid URL;
callback url must be valid 
requestId: requestId cannot be empty;
requestId is missing or empty 
message: Message must not be empty. Maximum length is 220 characters or 110 characters if it contains special characters; message: must not be null;
message is missing, empty or too big 
400 BAD_REQUEST "Failed to read HTTP message"
in this case, request body is mandatory. caused by parameters that we don't explicitly check

/auth/silent

Prerequisites

When customer/individual complains about API issue need to ask for the following: 1) Original request (body+headers) - Optional 2) Response status code - must 3) Timestamp - must

401 error

Search the sia-service logs at the specific timestamp.

Results:

Signature validation failed. JWT signature does not match locally computed signature. JWT validity cannot be asserted and should not be trusted.
bearer token is invalid 
customerEntity null retrieved for customerId [[customerId]]
bad customerId provided

400 error

Search the sia-service logs at the specific timestamp.

Results:

msisdn: msisdn cannot be empty;
msisdn is empty 
msisdn: numeric value out of bounds (<20 digits>.<0 digits> expected);
msisdn is not valid 
cbUrl: cbUrl cannot be empty;
missing callback url 
cbUrl: must be a valid URL;
callback url must be valid 
requestId: requestId cannot be empty;
requestId is missing or empty

/auth-touch

Prerequisites

When customer/individual complains about API issue need to ask for the following: 1) Original request (body+headers) - Optional 2) Response status code - must 3) Timestamp - must

401 error

Search the sia-service logs at the specific timestamp.

Results:

Signature validation failed. JWT signature does not match locally computed signature. JWT validity cannot be asserted and should not be trusted.
bearer token is invalid 
customerEntity null retrieved for customerId [[customerId]]
bad customerId provided

400 error

Search the sia-service logs at the specific timestamp.

Results:

msisdn: msisdn cannot be empty;
msisdn is empty 
msisdn: numeric value out of bounds (<20 digits>.<0 digits> expected);
msisdn is not valid 
cbUrl: cbUrl cannot be empty;
missing callback url 
cbUrl: must be a valid URL;
callback url must be valid 
requestId: requestId cannot be empty;
requestId is missing or empty 
400 BAD_REQUEST "Failed to read HTTP message"
in this case, request body is mandatory. caused by parameters that we don't explicitly check 
templateID: templateID cannot be empty;
missing (or empty) templateId 
Message not found for template {{template}}
templateId doesn't exists in our DB