Create Multiple Links
post
/vision/api/linkData/import
Creates multiple links. The following properties are required for each item in the array in the request body:
Unified Assurance roles with the following Vision package permissions have access to this endpoint:
- carrier
- cid
- startSourceId
- startDeviceId
- startPort
- startEntityId
- endSourceId
- endEntityId
- endDeviceId
- endPort
- mbps
- ckt
- startPortFacingCkt
- endPortFacingCkt
- description
- metaData
Unified Assurance roles with the following Vision package permissions have access to this endpoint:
- Admin
- Api
Request
There are no request parameters for this operation.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
array
-
Array of:
object schema
The details of a Vision link object.
Nested Schema : schema
Type:
object
The details of a Vision link object.
Show Source
-
carrier: string
The link carrier.Example:
Carrier 1
-
cid: string
The link carrier ID.Example:
carrier1
-
ckt: string
The link CKT.Example:
ckt
-
description: string
The link description.Example:
Frisco to Redwood City data centers.
-
endDeviceId: integer
(int32)
The device ID for the link's ending point.Example:
321
-
endDeviceName: string
The device name for the link's ending point.Example:
device321
-
endDeviceZoneId: integer
(int64)
The zone ID for the link's ending point device.Example:
1
-
endEntityId: integer
(int64)
The entity ID for the link's ending point.Example:
21
-
endEntityName: string
The entity name for the link's ending point.Example:
entity21
-
endLat: number
(double)
The latitude for the link's ending point.Example:
37.52935524682725
-
endLon: number
(double)
The longitude for the link's ending point.Example:
-122.26580410343541
-
endMetaData: object
endMetaData
Additional Properties Allowed: additionalPropertiesMetadata for the link's ending point.
-
endPort: string
The port (interface) for the link's ending point.Example:
interface321
-
endPortFacingCkt: string
The circuit of the port (interface) for the link's ending point.Example:
ckt_interface321
-
endSeverity: integer
(int32)
The event severity for the link's ending point.Example:
5
-
endSourceId: integer
(int64)
The source ID for the link's ending point. Only 1, for the Assure1 database, is supported.Example:
1
-
endSourceName: string
The source name for the link's ending point. Only Assure1 is supported.Example:
Assure1
-
endX: integer
(int32)
The X value for a logical link's ending point.Example:
6548
-
endY: integer
(int32)
The Y value for a logical link's ending point.Example:
8976123
-
endZoneId: integer
(int64)
The zone ID for the link's ending point.Example:
1
-
id: integer
(int64)
The link ID.Example:
123
-
mbps: integer
(int32)
The link bandwidth, in megabits per second.Example:
800
-
startDeviceId: integer
(int32)
The device ID for the link's starting point.Example:
123
-
startDeviceName: string
The device name for the link's starting point.Example:
device123
-
startDeviceZoneId: integer
(int64)
The zone ID for the link's starting point device.Example:
1
-
startEntityId: integer
(int64)
The entity ID for the link's starting point.Example:
12
-
startEntityName: string
The entity name for the link's starting point.Example:
entity12
-
startLat: number
(double)
The latitude for the link's starting point.Example:
30.243128396829135
-
startLon: number
(double)
The longitude for the link's starting point.Example:
-97.72173882639726
-
startMetaData: object
startMetaData
Additional Properties Allowed: additionalPropertiesMetadata for the link's starting point.
-
startPort: string
The port (interface) for the link's starting point.Example:
interface123
-
startPortFacingCkt: string
The circuit of the port (interface) for the link's starting point.Example:
ckt_interface123
-
startSeverity: integer
(int32)
The event severity for the link's starting point.Example:
1
-
startSourceId: integer
(int64)
The source ID for the link's starting point. Only 1, for the Assure1 database, is supported.Example:
1
-
startSourceName: string
The source name for the link's starting point. Only Assure1 is supported.Example:
Assure1
-
startX: integer
(int32)
The X value for a logical link's starting point.Example:
1235
-
startY: integer
(int32)
The Y value for a logical link's starting point.Example:
545
-
startZoneId: integer
(int64)
The zone ID for the link's starting point.Example:
1
Nested Schema : endMetaData
Type:
object
Additional Properties Allowed
Show Source
Metadata for the link's ending point.
Example:
type: dDevice
Nested Schema : startMetaData
Type:
object
Additional Properties Allowed
Show Source
Metadata for the link's starting point.
Example:
type: dDevice
Nested Schema : additionalProperties
Type:
object
Nested Schema : additionalProperties
Type:
object
Response
Supported Media Types
- application/json
200 Response
OK
Root Schema : SuccessResponse
Type:
object
The success response details.
Show Source
-
csrfToken: string
The security token to prevent cross-site request forgery (CSRF).Example:
12345
-
message: string
The response message.Example:
The entities were added successfully.
-
reason: string
The reason phrase for the response.Example:
OK
-
status: integer
(int32)
The response status code.Example:
200
401 Response
Unauthorized Access
Root Schema : schema
Type:
object
The error response details.
Show Source
-
message: string
The error message.Example:
An internal server error occurred.
-
reason: string
The reason phrase for the response.Example:
INTERNAL SERVER ERROR
-
status: integer
(int32)
The response status code.Example:
500
422 Response
Unprocessable Entity. Usually due to not providing a required field.
Root Schema : schema
Type:
object
The error response details.
Show Source
-
message: string
The error message.Example:
An internal server error occurred.
-
reason: string
The reason phrase for the response.Example:
INTERNAL SERVER ERROR
-
status: integer
(int32)
The response status code.Example:
500
500 Response
An internal server error occurred while accessing the database or performing a database operation.
Root Schema : schema
Type:
object
The error response details.
Show Source
-
message: string
The error message.Example:
An internal server error occurred.
-
reason: string
The reason phrase for the response.Example:
INTERNAL SERVER ERROR
-
status: integer
(int32)
The response status code.Example:
500