Forum Replies Created
-
AuthorPosts
-
in reply to: Custom DID API Requests #14732
Hello Andrey,
Sorry for the delay. I am still unable to identify the exact cause of the issue, but I’m actively working on it. I think I will need to process the entire flow step by step — from placing an order to issuing a refund — to fully understand where the problem occurs.
I would appreciate your/admin’s help. Could you please record a video showing the complete process, from ordering to refunding? This will help me follow the exact steps and verify the code accordingly.
in reply to: Custom DID API Requests #14730Hello Andrey,
hanks, I’ve got the access.
Please confirm whether you have an Apple Developer account for uploading the app to the App Store.
If you already have one, please share the details. If not, please create an account and provide the credentials.I am currently investigating the refund issue.
in reply to: Custom DID API Requests #14727Hello Andrey,
Yes , wait for minutes.
in reply to: Custom DID API Requests #14721Hello Andrey,
Waiting for your reply on post #14717 .
in reply to: Custom DID API Requests #14717Hello Andrey,
Please share the registered mobile number with firbase and be with us for the otp .
in reply to: Custom DID API Requests #14712Hello Andrey,
I have added the custom DID Number Detail API to the API Integration page under the name ‘DID Number Detail’. The user can now start testing it.
for post #14703 => It is using Inteliquent API .
I may need you tomorrow for quick responses, as the mobile app developer needs to log in to Firebase. Since two-factor authentication is enabled, I will require the registered mobile number used for Firebase and the OTP you receive during the login process.
in reply to: Custom DID API Requests #14709Hello Andrey,
Thanks for your more input on refund issue , i will follow your input in process for fixing it.
in reply to: Custom DID API Requests #14706Hello Anderey,
I was reviewing the responsive design task, exploring how it can be implemented and understanding the related processes. I am also still waiting for confirmation regarding the custom DID API task.
As for the refund issue, I will check again, identify the root cause, and work on fixing it.
in reply to: Messenger App #14699Hello Andrey,
Message from mobile app developer:
The work is expected to be completed by next week, or earlier if no additional issues arise.in reply to: Messenger App #14697Hello Andrey,
Let me check with the mobile app developer, and then I’ll inform you.
in reply to: Custom DID API Requests #14694Hello Andrey,
Please check below url and response data and confirm if this is you/admin want for the customer.
Request url:
https://excellentnumbers.net/api/getNumberDID/authkey/101404eb7bd17597357.93981693/Did/(256)%20281-1111Response:
{
“status”: “success”,
“message”: “Numbers Fetched”,
“data”: {
“product_name”: “(256) 281-1111”,
“product_code”: “pn2562811111”,
“availablity”: “Reserved!”,
“price”: “599.9900”,
“calculate_price”: “599.9900”,
“product_condition”: “New”,
“brandname”: null
}
}in reply to: Custom DID API Requests #14692Hello Andrey,
Regarding the API bug, I can see that it’s working. For the getProduct and inventoryUpdate APIs, they are being called with the wrong structure. Please ask them to click on “Get Code” to view the complete URL. I can’t display the entire payload in the URL listing — they need to click on “Get Code” to see the full API URL, which includes the required productId.
in reply to: Custom DID API Requests #14690Hello Andrey,
Sorry, but I need to be completely sure before starting, because I have to review the existing resources. All the other APIs related to getnumbers in Excellent Numbers are connected with the database, whereas the DID number comes from the Telinta API. So I need to confirm everything before beginning the development.
Although I have already started working on the API, and if everything goes well, I should be able to complete the development within this week.
Regarding the other API issue you mentioned, I will check it. But just to inform you— I was not working on that file. Even while working on the DID API, there will be no need to modify that file anyway.
in reply to: Custom DID API Requests #14685Hello Andrey,
Yes, I have implemented the DID API in the VoIP website. That’s why I mentioned that the DID number is not part of the Excellent number — it belongs to the VoIP customer. So I want you to please confirm this with the admin as well, because I am developing the API on the VoIP side.
in reply to: Custom DID API Requests #14683Hello Andrey,
I need a clarification , i am bit confuse:
The DID number isn’t part of Inteliquent. Shouldn’t I call their API to get the result from Inteliquent? Please confirm this from your side as well so we are both on the same page.
Also, can you please provide the payment breakdown? I need to share this information with my finance team.
-
AuthorPosts