@rudra This issue is resolved now, thanks to smart api team.