NanoTelecom Imrpovment Ideas

[Grant Lugniake]

#16701

What we’ve got and what can be done to make it better!

[Andrey]

#16708

Hello guys,
welcome to the “NanoTelecom Revision” forum discussion, we are looking forward to hear your expertised reviews and suggestions on the project potential and possible ways to enhance its efficency to nowadays market demand and reqirements.

Kind regadrs Andrey

[NanoM]

#16792

Hello, we are looking at some ways to link both EN and NT portals I just need an event webhook when a number is consumed there so Nano portal’s database can be kept in sync. Nano portal can react to that webhook from EN and provision the number in Telinta?

Cheers

[Nishit Shan]

#16796

Hello NanoM

Could you please explain your request in detail, specifically what you actually want from ExcellentNumbers (EN)?
We can create a webhook API on the NanoTelecom side and integrate it with EN so that whenever a new entry is created in EN, the same entry is automatically synced to NanoTelecom.

Please clarify the expected workflow and the type of data you want to sync so we can implement it accordingly.

[NanoM]

#16798

Hello Nishit,

thanks for picking this up. The receiving side already exists: the Nano portal will accept the events, so nothing needs to be built on the NanoTelecom side. What I need from EN is to send an event to the portal whenever a number’s status changes, starting with the moment a number is sold.

Events

* number.sold: an order containing the number is placed, whether through the storefront, the API or an admin order
* number.status_changed: the number’s EN status changes after that
* number.canceled: the sale is canceled or refunded
* One event per number (an order with 3 numbers sends 3 events), sent within a few seconds of the change rather than in a batch.

Fields (JSON)

* event_id (required): unique per event, kept the same on any resend
* event (required): one of the 3 above
* occurred_at (required): ISO 8601 with offset, for example 2026-11-10T17:24:36-05:00
* number (required): 10 digits
* order_id (required): EN’s order number, for example IN30186
* order_source (required): api, storefront or admin
* customer_id (required): EN’s own ID for the buyer, one that never changes
* customer_company (required): the buyer’s company name
* service (required): the plan sold with the number, for example “30 days call forwarding 500 minutes”
* en_status (required): the number’s EN status after the change, spelled as EN shows it
* supplier (required): who supplies the number to EN, or blank if no supplier holds it yet
* sku, customer_email, ring_to (10 digits) and price (optional)
The event must never carry the port-out PIN, a password or payment details.

Delivery

* An HTTPS POST with Content-Type: application/json to an address I’ll give you.
* Signed with a shared secret: headers X-EN-Timestamp (Unix seconds) and X-EN-Signature, the hex HMAC-SHA256 of the timestamp, a period and the raw body. Requests more than 5 minutes off are refused.
* The portal answers 200 once it has stored the event. Anything else, or no answer within 10 seconds, is a failure; please retry after 1, 5, 15 and 60 minutes, then hourly for 24 hours, with the same event_id and body.
* Please keep a log of each event, its answer and its retries so a lost event can be found and resent.

Example
{
“event_id”: “evt_8f3a91c2”,
“event”: “number.sold”,
“occurred_at”: “2026-11-10T17:24:36-05:00”,
“number”: “3093227777”,
“order_id”: “IN30186”,
“order_source”: “api”,
“customer_id”: “4182”,
“customer_company”: “NumberBarn”,
“service”: “30 days call forwarding 500 minutes”,
“en_status”: “Port Out Authorized”,
“supplier”: “Nano”,
“price”: “164.99”
}

A few questions before you start:

1.Can EN send number.sold from every way a number is sold: the storefront, the API and admin orders?
2.Does EN record which supplier each number comes from, so supplier can be filled in?
3.Which customer ID does EN keep for each buyer that never changes?
4.What date could EN send events to a test address, and then to the live one?

I’ll send the endpoint address and the shared secret separately once you confirm.

thanks

[Author]

Posts