Forum Replies Created
-
AuthorPosts
-
in reply to: Custom DID API Requests #14781
Hello Nishit thank you for your message, we may come back to #14762 Clause 3 as we have already spent this budget for it bu we will need it later.
Since we still wating for Redis updates and Refund Video from EN team,
would you please advice if we can start responsice work https://webmaklay.com/en-responsive/?If so we will move to responsive forup and will continew our communication there.
Before responsive work starts we will need to upload a copy of EN project to excellentnumbers.cv domain, please advice if you can do it or you need assistance on it?in reply to: Custom DID API Requests #14779Hello Nishit thank you for your #14778 message, i wish we could have a users managment tool as mentione in #14762 Clause 3 so site admin could controll each users connectiivities behaviour and see each user’s API usage so they can warn or restrict such agressive API members….
. In your: “I have also updated the API documents for the request format ” – are you saying you finished the job as it described in #14763?
in reply to: Custom DID API Requests #14777Thank you Nishit awaiting for your confirmation!
in reply to: Custom DID API Requests #14775Hello Nishit hope you are on Currier Lookup API task,
EN site admin will record us their video later and i will forward it to you.
Same for Redis our system team will check again howm to make it easear for you to use itLet us just keep moving furthre with all jobs, after finsihing Currier Lookup API will go to the next job and will get back to refund issue after EN provides us new video
in reply to: Custom DID API Requests #14773Hello Nishit,
For Currier API Lookup – okay please do 2 option will add some funds to your payout.Please do not forget that 300 requests per user per day should be ONLY for Currier Look Up API not for the Curriel Look Up on EN siteFor the refund issue: video requetsed, waiting
Regarding Redis: will ask again from system admin and get back to you.
Message from the mobile app developer:
we have updated couple users on Dave office page please find two members under Friends access tab and advice if you need more.in reply to: Custom DID API Requests #14765Hello Nishit thanks for your reply,
Your implementation plan for the Carrier Lookup API task sounds good!
Could you please confirm that you are not going to do #14762 Clause 3?For Redis question – since opur system admin installed Redis on your request we assume you have got a bit of knowlage on how to use this Redis application.
We have also mentioned to you in here – #14762 and then when you still was not sure i have contacted system admin and we advised you in here #14675 – not sure if you missed that.
Could you please let me know if it is still unclear for you and then how were you going to use Redis server and if you experience in it?
For #14762 Refund issue as i mentioned above: – the EN team have checked it and they reported back to me that it is still the same and it is not working correctly i will ask someone to send you an other video to investigate and get back to you soon.
in reply to: Custom DID API Requests #14762Hello Nishit,
FOR REFUND ISSUE
i have sent your refund video to EN team they are going to check this again and if you did not do anything on it i suspect they will send us back their errors again. What i have asked them was to send us more detail video on whats happening when they do refund. This is why En team whanted you to refund their order (ref #14735). Let us wait for their feed back they told me that they are going to check it carefully again.FOR NUMBER API CALLS
It has been recomended to the EN customer to check their API connectivity again and we also attached your video for them. On your video it shows that there is no number found on EN site but we belive it was a vaniti number so customers API searched it like 272 777 2277 but this number is actually 272 777 CARS and this is why there was a confusion about that. We will wait if any replies will be from the clients on your video and let you know if it happen.FOR CARRIER LOOKUP API
Yes please let us know what you are going to do.Once you done we will add more funds to your payout depending on your resolution the sum will vary from lowest to greatest:1. If you just remove Inteliquent provider from CARRIER API LOOKUP and leave only DATA 24/7 provider.
2. If you leave both providers but restrict CARRIER API LOOKUP daily calls to 300
3. If you create a setting tools for managing all above as we requested it in original Carrier lookup API job below:About Currer Lookup API Task:
Please note that Carrier Look Up API task had some othre task requirements which have not been accomplished but job paid.Please see these as we wanted Carrier Lookup API to have:
a) Managment Tools on Store Settings https://webmaklay.com/wp-content/uploads/2025/11/Carrier-Lookup-Tab.jpg
– it has not been done – https://webmaklay.com/wp-content/uploads/2025/11/Store-Settings.jpg
b) managment Tools on Customer Group https://webmaklay.com/wp-content/uploads/2025/11/Customers-Group-Task.jpg
– it has not been done – https://webmaklay.com/wp-content/uploads/2025/11/Whole-Sale-Group.jpg
– https://webmaklay.com/wp-content/uploads/2025/11/Customers-Group.jpgif we would have all these above we would not get this problem now as EN site admin would deal with it without brining us all these complains.
So please finsih it all up (clasue 3 above) and we should’t get back to it again and again.
—————————————————
Please aslo Nishit we still not getting from you about Redis server whether you going to use it or not for our large amout odf data eddition – PLEASE LET US KNOW.
in reply to: Custom DID API Requests #14755Hello Nishit thank you for your reports and videos attached i have seen them and advised both customers and EN team to check your repairs.
I also asked them to send us their video IF the problem is still persist hoping that it works from their side.
Also in your message you are saying : “I am understanding the exact point where the customer is facing the issue” could you please provide more details on this if this has been fixed now or if they do something wring then what exactly they need to do.
Please let me know if you can reduce API calls for Carrier Lookup API as we need to find a budget and pay you for this extra work.
Just to remind you that Intelliquent complain about too many requests from Customers API for Currier Look up and we need to either limit their connectivity to ~300 per day or only allow them to check their carrier information from Data 24/7 only and remove Inteliquent.
Please let me know what are you going to do we will assign some budget to this works.
in reply to: Custom DID API Requests #14752Hi Nishit unfortunately i can not wait, please fix everything today, i do not know what to say to angry customer…
i will try to ask them to wait for tomorrowin reply to: Custom DID API Requests #14750Hi Nishit why it is so hard to just say that your are still working on it, we can not even see your testings, did you see https://webmaklay.com/wp-content/uploads/2025/11/API-ERR.jpg did api people can not use your “completed” work and waiting for your refund fix for a loong time. They have problems with their clients who forcing them to refund their payments and EN site admin can not send them their refunds because of this https://webmaklay.com/wp-content/uploads/2025/11/refund.mp4
they are VERY ungry with all this jobs got paid upfont and still not working plus continues errors and complains from customers.
It is very serious man we can not hold them wating for nothing for such a long time
in reply to: Custom DID API Requests #14748Hi Nishit customers a very unhappy with this looong time not hapening anything, we can not even see you doing anything, they want me to cancell all the jobs and process refund, sorry mate we can not work that way
in reply to: Custom DID API Requests #14747Hi Nishit any updates?
in reply to: Custom DID API Requests #14746Hi Nishit we have got plenty jobs to do we need all these below complete asap:
Please see priorities:1. Please Confirm IF Refund Issue Fixed
2. Error #14745
3. – for post #14703 => It is using Inteliquent API – for Carrier Look Up API could you please ONLY allow data 24/7 fetching and disable inteliquent will add extra funds to this small task as it is an addition to Carrier Lookup APIPLEASE IMPORTNAT EN build in carrier look up leave as it is with both providers inteliquent and Data 24/7 but ONLY for Carrier Look Up API disable Inteliquent and ONLY leave data 24/7 – this is why we would like you to keep more parameters in to API settings page so EN site admins could control this area without your involvement. If you could add Carrier API settings options to allow site admin to control which provider to use by switching in and off Inteliquent and Data 24/7 then let us know EN team will add more funds to this enhancement.
Alternatively please add 300 checks limit per day to Curreir Look Up API only – this will be an extra pay to this payout.
in reply to: Custom DID API Requests #14745Hello Nishit if you finished with Refund issue could you please check this complain from the customer who says that your Custom DID API does not work please see attached screen https://webmaklay.com/wp-content/uploads/2025/11/API-ERR.jpg
in reply to: Custom DID API Requests #14743Hello Nishit how is all going any updates on refund fixing? Is it repaired now and can we process refunds to our customers?
-
AuthorPosts