[Nishit Shan]

in reply to: Carrier Lookup API #14368

Hello Andrey,

Do you want the API documentation should look like this :https://excellentnumbers.com/account.php?action=api-integration

[Nishit Shan]

in reply to: Carrier Lookup API #14359

Hello Andrey,

I found the task description too short, and I am not able to understand the task.Can you please describe it more.

[Nishit Shan]

in reply to: Search Improvnement #14350

Hello Andrey,

I will check “Carrier Lookup API” task and update you .I will also check the missed number improvement in the sideline of Carrier Lookup API task .
Just for info: I noticed search improvement task is still in planning mode on office dashboard page.

[Nishit Shan]

in reply to: Search Improvnement #14347

Hello Andrey,

“I have checked all the code on the API side but couldn’t find anything wrong that might cause the reserved number to be purchased. However, I did find a small typo mistake that could have caused a validation issue. I have fixed it, and I hope the issue will no longer occur.

[Nishit Shan]

in reply to: Search Improvnement #14343

Hello Andrey,

I have checked issue #14320 and found that the API code is correct. It also checks the reservation status before providing the list. Could you please reconfirm if it is the API that is forcibly purchasing the reserved number?

[Nishit Shan]

in reply to: Search Improvnement #14341

Hello Andrey,

Please check /app/Console/Commands and /app/Http/Controllers . Here you will find additional controller and command for the cron job.

[Nishit Shan]

in reply to: Search Improvnement #14339

Hello Andrey,

I have checked the pricing error and can confirm that it is working correctly. Please check this video: https://excellentnumbers.com/temp_vid/Screencast%20from%202025-09-01%2010-37-04.mp4

However, a description was needed to clarify why the price shows as zero, so I have enabled the description for better understanding.

[Nishit Shan]

in reply to: Search Improvnement #14338

Hello Andrey,

I have made my final changes for number search.
I will check the error about Pricing Repairs and fix.

“would you please advice us a path where you do the chron addition enhancments so we can assess why it takes so much time to improve search / purchasing functionality?” => I am not getting your exact , did you mean the folder structure of code where you can find the code or you are talking about something else ?

[Nishit Shan]

in reply to: Search Improvnement #14333

Hello Andrey,

There is nothing new to update you on. I am currently working on the cron job and I hope to complete it by tomorrow, so you can test it over the weekend..

[Nishit Shan]

in reply to: Search Improvnement #14329

Hello Andrey,

I think you were right, I messed up #14320 with Nanotel. I will check #14320 also and let you know my update.

[Nishit Shan]

in reply to: Search Improvnement #14327

Hello Andrey,

I am currently working on increasing the cron job efficiency and creating a separate function for each cron job. Apologies for the delay, but as you know, I was reviewing the API documentation for better clarity. Now I am implementing the cron jobs and their functionality, and I will update you once this is completed.

Regarding the reservation/purchase issues, could you please confirm if the reservations are being made using separate user IDs and stored in each user’s individual dashboard? If not, then I would need to assign a unique flag to every number being reserved by me. However, this approach may slow down the reservation process and could increase the chances of losing quality numbers. Since we are already working hard to secure such numbers, I would not recommend using the flag-based approach for reservations.

[Nishit Shan]

in reply to: Search Improvnement #14323

Hello Andrey,

“So, it’s possible that when you reserve a number, the purchase cron job might run at the same time, and the number gets purchased.” : This was my statement .

I am still reading the api documents , still not able to find any thing we can do using api . I am now considering to increase cron job and it’s individual function.

[Nishit Shan]

in reply to: Search Improvnement #14321

Hello Andrey,

If you remember, when I developed the number search and purchase functionality, I informed you that there is a cron job for reserving numbers and another cron job for purchasing all reserved numbers. So, it’s possible that when you reserve a number, the purchase cron job might run at the same time, and the number gets purchased.

[Nishit Shan]

in reply to: Search Improvnement #14316

Hello Andrey,

I have made changes for Master Port Out Pin only. I did not make any other code changes; I just hid the Master Port Out Pin because I think it was not described in the original task description, which is why I might not have done this earlier.

For Numbers search – any thoughts how we can enhance its func or updates on #14310?
->I am finding the solution and it will take time .

[Nishit Shan]

in reply to: Search Improvnement #14314

Hello Andrey,

I am still finding where the Master Port Out Pin is coming from on the registration form.

[Author]

Posts