Skip to Content
EIS

Changelog

Subscribe via RSS
  1. Catalog of Available Services

    GET /v1/service/activable lists the service profiles available for activation. By default, it uses the authenticated user’s organization. With organizationId, you can select a descendant organization if you have the subpartner_view permission. Use the optional typeId parameter to filter by service type.

    GET /v1/service/options/activable lists the options available for activation by the selected organization. Use the optional serviceId parameter to filter by profile. Each option’s serviceId matches the profile id returned by GET /v1/service/activable.

    • api
    • servizi
  2. Branches for Customer Records

    Main seats and branches

    To create a new branch location with POST /v1/customers/add, use type: BRANCH and mainCustomerId with 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, where id is 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, with id of 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 require customers_edit. The answers of the customer records document now also type and the canonical field mainCustomerId.

    • api
    • anagrafiche
  3. terminationUri in DSS Gateway Details

    terminationUri in DSS gateway detail

    Requests GET /v1/voip/dss/gtw/{gatewayId} and GET /v1/voip/dss/gtw/{gatewayId}/{organizationId} now display the optional field terminationUri, 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
  4. vatNumber for New Customer Records

    vatNumber in the creation of the customer records

    The request POST /v1/customers/add expounds vatNumber as a canonical field for the customer’s VAT game.

    To ensure retrocompatibility, pIva and piva continue to be accepted in input as legacy aliases. For new integrations use vatNumber.

    • api
    • anagrafiche
  5. 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