API endpoint to get SMS history is:

http://40.124.26.81:98/api/sms/history?Count=2&Page=2&SortOrder=1&NumbersFilter=%2B919160116961

Count parameter is number of result per page. Page parameter is result page to return. Sort order 0-ASC, 1-DESC. NumbersFilter parameter is optional to filter SMS with user numbers, it is comma separated list of numbers.

Basic header needs to be included.

Hi Harshveer Singh,

We are getting Server error by using above mentioned url.
Can you please confirm this

Priya Dhamande Swapnil Pandhare Samir

Server is up now.

Hi Harshveer Singh,

We have verified SMS history on swagger.
Please find the attachment.
But observed that ISRead and ISdelivered flag is not updated even though sms is being read and delivered.
As per discussion with you we have another jira for this.
So we can continue with testing when those tickets will be fixed.
Till now assigning this ticket you, assign me back once those issues are fixed.

Thanks,
Jayshree

Priya Dhamande Swapnil Pandhare Samir Satya Hrishikesh Deshpande Sachin Hingole

Above mentioned points are fixed, should be available in next deployment.

Harshveer Singh : Is this deployed ?
because before 45 min we didn't had any deployment

Raj Hawaldar will assign us after deployment

Priya Dhamande Swapnil Pandhare Hrishikesh Deshpande Samir ShashiKant Mishra

Please use this env for testing: https://dmscomapistage.workterra.net

As Per discussion assigning this ticket to Priya Dhamande

Satya Samir Hrishikesh Deshpande

Hi Harshveer Singh,

As discusses, the SMS APi is having some issues.
Please assign to me once teh issue is resolved.

Swapnil Pandhare Samir

Api for history is working fine now. You can use AccountDID as CB1 and CB2

Environment: OneIM

API: /api/SMS/History

The API is tested for SMS history, worked out as expected with and without adding parameters.

So, marking Jira closed.

Harshveer Singh Swapnil Pandhare Samir