Uses of Package
com.eqixiac.equinix.customerportal.model
Packages that use com.eqixiac.equinix.customerportal.model
Package
Description
Customer Portal client interfaces for the Equinix Java SDK.
Customer Portal model interfaces for the Equinix Java SDK.
-
Classes in com.eqixiac.equinix.customerportal.model used by com.eqixiac.equinix.customerportal.clientClassDescriptionAn installed-base asset retrieved from the Equinix Customer Portal Assets v1 API: a product or piece of equipment belonging to the organization that is installed in an Equinix IBX.Metadata for a file attachment in the Equinix Customer Portal (Attachments v1
attachment).The current user's acceptance of the Digital LOA private beta terms (diLOA v1 API).A billing account, as returned by the Billing v1 finance accounts API.A billing account, as returned by the Platform Billing Account v2 (BAS) API.A connection service available at an IBX, with its supported media types.A Digital Letter of Authorization (Digital LOA) document from the Equinix Customer Portal diLOA v1 API.A change record applied to a Digital LOA document, from the Equinix Customer Portal diLOA v1 API.Full details of a single email associated with a support case, as returned by the support v1 email details endpoint (EmailDetailsResponse).A customer organization the current user may use as a Digital LOA requestor (diLOA v1 API).A permitted IBX location for a customer, with its accounts and cages, as returned by the Customer Portal Lookup v2 colocation locations API (locations_details).An IBX or network notification in the Equinix Customer Portal (Notifications v1ibx-notification/network-notification).An order retrieved from the Equinix Customer Portal (Orders v2).A single order history record (order-header) returned by an order history search.One page of an order history search (order-history-response): thecontentrecords, the response-levellinksand thepagemetadata.A negotiation message on an order, proposing an alternative date and time for fulfilling the order request.Result of submitting a colocation order, carrying the generated order identifier.A patch panel available for cross-connect ordering.One entry of the result of submitting a pending storage shipment order (pending-storage-order-responseitem in the shipments v1 spec) - the API returns one entry per stored shipment submitted, identifying the created order and the storage, location and account it applies to.A location the current user may filter order history by: an IBX and its permitted cages.Whether the current user is permitted to use the Digital LOA application in its private beta phase (diLOA v1 API).Secure cabinet product availability for an IBX, describing the cabinet capacity and power configuration that may be ordered at a given location.A provider available as the A-side of a cross-connect order.A quote retrieved from the Equinix Customer Portal (Quotes v2).A generated report in the Report Center (Reports v1downloadable-reportfor the list view,reportfor the detail view).A scheduled report definition in the Report Center (Reports v1scheduledReport).An IBX where the current user may place shipment orders, with the cages (and, when requested withdetail=true, accounts and cabinets) the user has access to (locationin the shipments v1 spec).Result of submitting an inbound or outbound v1 shipment order (shipment-order-responsein the shipments v1 spec).Response returned after submitting a smart hands order, carrying the generated order number.An IBX and its cages where the current user is permitted to place smart hands orders.A supported smart hands order type, as returned by the reference types endpoint.A trouble ticket / support case retrieved by case or order number from the Equinix Customer Portal support v2 API (SingleCaseResponseV2).A Smart Hands support plan retrieved from the Equinix Customer Portal Support Plans v2 API (GET /colocations/v2/supportPlans).A trouble ticket retrieved from the Equinix Customer Portal Tickets v2 API.An IBX and its cages where the current user is permitted to place trouble ticket orders.A trouble ticket problem category, as returned by the reference types endpoint.A unified order / colocation notification event returned by the Customer Portal unified notifications v2 search API. -
Classes in com.eqixiac.equinix.customerportal.model used by com.eqixiac.equinix.customerportal.client.implementationClassDescriptionAn installed-base asset retrieved from the Equinix Customer Portal Assets v1 API: a product or piece of equipment belonging to the organization that is installed in an Equinix IBX.Metadata for a file attachment in the Equinix Customer Portal (Attachments v1
attachment).The current user's acceptance of the Digital LOA private beta terms (diLOA v1 API).A billing account, as returned by the Billing v1 finance accounts API.A billing account, as returned by the Platform Billing Account v2 (BAS) API.A connection service available at an IBX, with its supported media types.A Digital Letter of Authorization (Digital LOA) document from the Equinix Customer Portal diLOA v1 API.A change record applied to a Digital LOA document, from the Equinix Customer Portal diLOA v1 API.Full details of a single email associated with a support case, as returned by the support v1 email details endpoint (EmailDetailsResponse).A customer organization the current user may use as a Digital LOA requestor (diLOA v1 API).A permitted IBX location for a customer, with its accounts and cages, as returned by the Customer Portal Lookup v2 colocation locations API (locations_details).An IBX or network notification in the Equinix Customer Portal (Notifications v1ibx-notification/network-notification).An order retrieved from the Equinix Customer Portal (Orders v2).A single order history record (order-header) returned by an order history search.One page of an order history search (order-history-response): thecontentrecords, the response-levellinksand thepagemetadata.A negotiation message on an order, proposing an alternative date and time for fulfilling the order request.Result of submitting a colocation order, carrying the generated order identifier.A patch panel available for cross-connect ordering.One entry of the result of submitting a pending storage shipment order (pending-storage-order-responseitem in the shipments v1 spec) - the API returns one entry per stored shipment submitted, identifying the created order and the storage, location and account it applies to.A location the current user may filter order history by: an IBX and its permitted cages.Whether the current user is permitted to use the Digital LOA application in its private beta phase (diLOA v1 API).Secure cabinet product availability for an IBX, describing the cabinet capacity and power configuration that may be ordered at a given location.A provider available as the A-side of a cross-connect order.A quote retrieved from the Equinix Customer Portal (Quotes v2).A generated report in the Report Center (Reports v1downloadable-reportfor the list view,reportfor the detail view).A scheduled report definition in the Report Center (Reports v1scheduledReport).An IBX where the current user may place shipment orders, with the cages (and, when requested withdetail=true, accounts and cabinets) the user has access to (locationin the shipments v1 spec).Result of submitting an inbound or outbound v1 shipment order (shipment-order-responsein the shipments v1 spec).Response returned after submitting a smart hands order, carrying the generated order number.An IBX and its cages where the current user is permitted to place smart hands orders.A supported smart hands order type, as returned by the reference types endpoint.A trouble ticket / support case retrieved by case or order number from the Equinix Customer Portal support v2 API (SingleCaseResponseV2).A Smart Hands support plan retrieved from the Equinix Customer Portal Support Plans v2 API (GET /colocations/v2/supportPlans).A trouble ticket retrieved from the Equinix Customer Portal Tickets v2 API.An IBX and its cages where the current user is permitted to place trouble ticket orders.A trouble ticket problem category, as returned by the reference types endpoint.A unified order / colocation notification event returned by the Customer Portal unified notifications v2 search API. -
Classes in com.eqixiac.equinix.customerportal.model used by com.eqixiac.equinix.customerportal.client.internalClassDescriptionThe current user's acceptance of the Digital LOA private beta terms (diLOA v1 API).A connection service available at an IBX, with its supported media types.A Digital Letter of Authorization (Digital LOA) document from the Equinix Customer Portal diLOA v1 API.A change record applied to a Digital LOA document, from the Equinix Customer Portal diLOA v1 API.Full details of a single email associated with a support case, as returned by the support v1 email details endpoint (
EmailDetailsResponse).A customer organization the current user may use as a Digital LOA requestor (diLOA v1 API).A permitted IBX location for a customer, with its accounts and cages, as returned by the Customer Portal Lookup v2 colocation locations API (locations_details).An IBX or network notification in the Equinix Customer Portal (Notifications v1ibx-notification/network-notification).One page of an order history search (order-history-response): thecontentrecords, the response-levellinksand thepagemetadata.A negotiation message on an order, proposing an alternative date and time for fulfilling the order request.Result of submitting a colocation order, carrying the generated order identifier.A patch panel available for cross-connect ordering.One entry of the result of submitting a pending storage shipment order (pending-storage-order-responseitem in the shipments v1 spec) - the API returns one entry per stored shipment submitted, identifying the created order and the storage, location and account it applies to.A location the current user may filter order history by: an IBX and its permitted cages.Whether the current user is permitted to use the Digital LOA application in its private beta phase (diLOA v1 API).Secure cabinet product availability for an IBX, describing the cabinet capacity and power configuration that may be ordered at a given location.A provider available as the A-side of a cross-connect order.A generated report in the Report Center (Reports v1downloadable-reportfor the list view,reportfor the detail view).A scheduled report definition in the Report Center (Reports v1scheduledReport).An IBX where the current user may place shipment orders, with the cages (and, when requested withdetail=true, accounts and cabinets) the user has access to (locationin the shipments v1 spec).Result of submitting an inbound or outbound v1 shipment order (shipment-order-responsein the shipments v1 spec).Response returned after submitting a smart hands order, carrying the generated order number.An IBX and its cages where the current user is permitted to place smart hands orders.A supported smart hands order type, as returned by the reference types endpoint.A trouble ticket / support case retrieved by case or order number from the Equinix Customer Portal support v2 API (SingleCaseResponseV2).An IBX and its cages where the current user is permitted to place trouble ticket orders.A trouble ticket problem category, as returned by the reference types endpoint.A unified order / colocation notification event returned by the Customer Portal unified notifications v2 search API. -
Classes in com.eqixiac.equinix.customerportal.model used by com.eqixiac.equinix.customerportal.client.internal.implementationClassDescriptionAn installed-base asset retrieved from the Equinix Customer Portal Assets v1 API: a product or piece of equipment belonging to the organization that is installed in an Equinix IBX.Metadata for a file attachment in the Equinix Customer Portal (Attachments v1
attachment).The current user's acceptance of the Digital LOA private beta terms (diLOA v1 API).A billing account, as returned by the Billing v1 finance accounts API.A billing account, as returned by the Platform Billing Account v2 (BAS) API.A connection service available at an IBX, with its supported media types.A Digital Letter of Authorization (Digital LOA) document from the Equinix Customer Portal diLOA v1 API.A change record applied to a Digital LOA document, from the Equinix Customer Portal diLOA v1 API.Full details of a single email associated with a support case, as returned by the support v1 email details endpoint (EmailDetailsResponse).A customer organization the current user may use as a Digital LOA requestor (diLOA v1 API).A permitted IBX location for a customer, with its accounts and cages, as returned by the Customer Portal Lookup v2 colocation locations API (locations_details).An IBX or network notification in the Equinix Customer Portal (Notifications v1ibx-notification/network-notification).An order retrieved from the Equinix Customer Portal (Orders v2).One page of an order history search (order-history-response): thecontentrecords, the response-levellinksand thepagemetadata.A negotiation message on an order, proposing an alternative date and time for fulfilling the order request.Result of submitting a colocation order, carrying the generated order identifier.A patch panel available for cross-connect ordering.One entry of the result of submitting a pending storage shipment order (pending-storage-order-responseitem in the shipments v1 spec) - the API returns one entry per stored shipment submitted, identifying the created order and the storage, location and account it applies to.A location the current user may filter order history by: an IBX and its permitted cages.Whether the current user is permitted to use the Digital LOA application in its private beta phase (diLOA v1 API).Secure cabinet product availability for an IBX, describing the cabinet capacity and power configuration that may be ordered at a given location.A provider available as the A-side of a cross-connect order.A quote retrieved from the Equinix Customer Portal (Quotes v2).A generated report in the Report Center (Reports v1downloadable-reportfor the list view,reportfor the detail view).A scheduled report definition in the Report Center (Reports v1scheduledReport).An IBX where the current user may place shipment orders, with the cages (and, when requested withdetail=true, accounts and cabinets) the user has access to (locationin the shipments v1 spec).Result of submitting an inbound or outbound v1 shipment order (shipment-order-responsein the shipments v1 spec).Response returned after submitting a smart hands order, carrying the generated order number.An IBX and its cages where the current user is permitted to place smart hands orders.A supported smart hands order type, as returned by the reference types endpoint.A trouble ticket / support case retrieved by case or order number from the Equinix Customer Portal support v2 API (SingleCaseResponseV2).A Smart Hands support plan retrieved from the Equinix Customer Portal Support Plans v2 API (GET /colocations/v2/supportPlans).A trouble ticket retrieved from the Equinix Customer Portal Tickets v2 API.An IBX and its cages where the current user is permitted to place trouble ticket orders.A trouble ticket problem category, as returned by the reference types endpoint.A unified order / colocation notification event returned by the Customer Portal unified notifications v2 search API. -
Classes in com.eqixiac.equinix.customerportal.model used by com.eqixiac.equinix.customerportal.modelClassDescriptionA connection service available at an IBX, with its supported media types.Email content for an IBX/network notification event (Notifications v1
notification-email).A single order history record (order-header) returned by an order history search.A generated report in the Report Center (Reports v1downloadable-reportfor the list view,reportfor the detail view).An input parameter for a report (Reports v1parameter).An account associated with a cage in the smart hands location reference data.A cabinet within an account in the smart hands location reference data.A cage (or suite) within an IBX, including its types and the accounts it belongs to. -
Classes in com.eqixiac.equinix.customerportal.model used by com.eqixiac.equinix.customerportal.model.implementationClassDescriptionA single string-typed communications detail of a contact: a
type(such asPHONE,EMAILorMOBILE) and itsvalue. -
Classes in com.eqixiac.equinix.customerportal.model used by com.eqixiac.equinix.customerportal.model.jsonClassDescriptionAn installed-base asset retrieved from the Equinix Customer Portal Assets v1 API: a product or piece of equipment belonging to the organization that is installed in an Equinix IBX.The current user's acceptance of the Digital LOA private beta terms (diLOA v1 API).A billing account, as returned by the Billing v1 finance accounts API.A billing account, as returned by the Platform Billing Account v2 (BAS) API.A connection service available at an IBX, with its supported media types.A Digital Letter of Authorization (Digital LOA) document from the Equinix Customer Portal diLOA v1 API.A change record applied to a Digital LOA document, from the Equinix Customer Portal diLOA v1 API.Full details of a single email associated with a support case, as returned by the support v1 email details endpoint (
EmailDetailsResponse).A customer organization the current user may use as a Digital LOA requestor (diLOA v1 API).A permitted IBX location for a customer, with its accounts and cages, as returned by the Customer Portal Lookup v2 colocation locations API (locations_details).An IBX or network notification in the Equinix Customer Portal (Notifications v1ibx-notification/network-notification).Email content for an IBX/network notification event (Notifications v1notification-email).A single order history record (order-header) returned by an order history search.One page of an order history search (order-history-response): thecontentrecords, the response-levellinksand thepagemetadata.A negotiation message on an order, proposing an alternative date and time for fulfilling the order request.Result of submitting a colocation order, carrying the generated order identifier.A patch panel available for cross-connect ordering.One entry of the result of submitting a pending storage shipment order (pending-storage-order-responseitem in the shipments v1 spec) - the API returns one entry per stored shipment submitted, identifying the created order and the storage, location and account it applies to.A location the current user may filter order history by: an IBX and its permitted cages.Whether the current user is permitted to use the Digital LOA application in its private beta phase (diLOA v1 API).Secure cabinet product availability for an IBX, describing the cabinet capacity and power configuration that may be ordered at a given location.A provider available as the A-side of a cross-connect order.A generated report in the Report Center (Reports v1downloadable-reportfor the list view,reportfor the detail view).An input parameter for a report (Reports v1parameter).A scheduled report definition in the Report Center (Reports v1scheduledReport).An IBX where the current user may place shipment orders, with the cages (and, when requested withdetail=true, accounts and cabinets) the user has access to (locationin the shipments v1 spec).Result of submitting an inbound or outbound v1 shipment order (shipment-order-responsein the shipments v1 spec).Response returned after submitting a smart hands order, carrying the generated order number.An account associated with a cage in the smart hands location reference data.A cabinet within an account in the smart hands location reference data.A cage (or suite) within an IBX, including its types and the accounts it belongs to.An IBX and its cages where the current user is permitted to place smart hands orders.A supported smart hands order type, as returned by the reference types endpoint.A trouble ticket / support case retrieved by case or order number from the Equinix Customer Portal support v2 API (SingleCaseResponseV2).A Smart Hands support plan retrieved from the Equinix Customer Portal Support Plans v2 API (GET /colocations/v2/supportPlans).An IBX and its cages where the current user is permitted to place trouble ticket orders.A trouble ticket problem category, as returned by the reference types endpoint.A unified order / colocation notification event returned by the Customer Portal unified notifications v2 search API. -
Classes in com.eqixiac.equinix.customerportal.model used by com.eqixiac.equinix.customerportal.model.wrappersClassDescriptionMetadata for a file attachment in the Equinix Customer Portal (Attachments v1
attachment).An order retrieved from the Equinix Customer Portal (Orders v2).A quote retrieved from the Equinix Customer Portal (Quotes v2).A trouble ticket retrieved from the Equinix Customer Portal Tickets v2 API.