Changelog
Catalog of Available Services
GET /v1/service/activablelists the service profiles available for activation. By default, it uses the authenticated user’s organization. WithorganizationId, you can select a descendant organization if you have thesubpartner_viewpermission. Use the optionaltypeIdparameter to filter by service type.GET /v1/service/options/activablelists the options available for activation by the selected organization. Use the optionalserviceIdparameter to filter by profile. Each option’sserviceIdmatches the profileidreturned byGET /v1/service/activable.- api
- servizi
Branches for Customer Records
Main seats and branches
To create a new branch location with
POST /v1/customers/add, usetype: BRANCHandmainCustomerIdwith the ID of the main office. The fields already required to create a customer record remain necessary. With multi-site enabled, the locations must have the same VAT number.To connect existing customer records, use
PUT /v1/customers/update/{id}/{organizationId}/main-customer/branches, whereidis the headquarters:{ "secondaryCustomerIds": [102, 103] } The operation maintains the other branches already connected. The IDs must be distinguished and different from the main office; the customer records must belong to the same organization and do not have their own branches.
They are also documented:
GET /v1/customers/{id}/{organizationId}/branches: list of visible branches; returns 404 even if they are not present.POST /v1/customers/{id}/{organizationId}/main-customer/branches/check-duplicates: Preliminary control with the same body, without modification. Report duplicates, existing links and incompatibility.PUT /v1/customers/update/{id}/{organizationId}/main-customer/branches/replace: replacement of the whole list. Excluded locations are disconnected; a blank list attempts to disconnect them all.PUT /v1/customers/update/{id}/{organizationId}/main-customer: connection of a single branch, withidof the branch and body{"mainCustomerId": 101}.DELETE /v1/customers/update/{id}/{organizationId}/main-customer: removal of the link of the indicated branch, if permitted by multi-site rules.
Preliminary consultation and control require
customers_view; changes requirecustomers_edit. The answers of the customer records document now alsotypeand the canonical fieldmainCustomerId.- api
- anagrafiche
terminationUri in DSS Gateway Details
terminationUriin DSS gateway detailRequests
GET /v1/voip/dss/gtw/{gatewayId}andGET /v1/voip/dss/gtw/{gatewayId}/{organizationId}now display the optional fieldterminationUri, which identifies the SIP termination endpoint.At the moment the field is valued exclusively for the Elastic SIP Trunk; for other types may be absent or
null.- api
- voip
vatNumber for New Customer Records
vatNumberin the creation of the customer recordsThe request
POST /v1/customers/addexpoundsvatNumberas a canonical field for the customer’s VAT game.To ensure retrocompatibility,
pIvaandpivacontinue to be accepted in input as legacy aliases. For new integrations usevatNumber.- api
- anagrafiche
New EIS Documentation for Hive, Services, and the API
New EIS Documentation for Hive, Services, and the API
The new EIS documentation structure is available:
- EIS infrastructure and Partner models, Referral Partner and direct sale;
- Hive guides, online sales and operating flows;
- SIP Trunk, numbering, portability and integrations Voice AI;
- data connectivity, coverage and activation of circuits;
- quickstart, authentication and complete reference of APIs;
- SEO metadata, canon domain and official assets EIS.
- documentazione
- hive
- voip
- connettivita
- api
No changelog entries match your filters.