3 The bulk API allows a client to add/modify/patch/delete multiple vertexes and/or edges within a single request. This request will be treated as an atomic transaction in that all operations within the bulk request will either fail or succeed together. This is often useful when attempting to add an entire subgraph.
5 The following example shows how a client could create 2 vertexes (pserver and vserver) and link them with an edge. In the JSON body, the order in which vertex and edge operations are defined within the `objects` and `relationships` arrays is not important. The bulk API will handle the operations requested in a logical order to preserve data integrity.
7 URL: https://<host>:9520/services/inventory/v11/bulk
18 "vserver-name":"vserver1",
19 "prov-status":"Provisioned",
20 "vserver-id":"Vserver-AMT-002-HSGW",
21 "vserver-name2":"Vs2-HSGW-OTT",
22 "vserver-selflink":"AMT VserverLink",
23 "is-closed-loop-disabled":false
32 "ptnii-equip-name":"ps1993",
33 "hostname":"pserver1",
34 "equip-type":"server",
36 "equip-model":"DL380p-nd",
38 "fqdn":"pserver1.lab.com",
39 "ipv4-oam-address":"199.1.138.60"
48 "type":"tosca.relationships.HostedOn",
52 "contains-other-v": "NONE",
53 "delete-other-v": "NONE",
55 "prevent-delete": "IN"
72 "url": "services/inventory/v11/vserver/1024143488",
75 "vserver-name":"vserver1",
76 "prov-status":"Provisioned",
77 "vserver-id":"Vserver-AMT-002-HSGW",
78 "vserver-name2":"Vs2-HSGW-OTT",
79 "vserver-selflink":"AMT VserverLink",
80 "is-closed-loop-disabled":false
91 "url": "services/inventory/v11/pserver/1228865600",
93 "ptnii-equip-name":"ps1993",
94 "hostname":"pserver1",
95 "equip-type":"server",
97 "equip-model":"DL380p-nd",
99 "fqdn":"pserver1.lab.com",
100 "ipv4-oam-address":"199.1.138.60"
111 "id": "kbrs40-gxqy68-108id-kbmurk",
112 "type": "tosca.relationships.HostedOn",
113 "url": "services/inventory/relationships/v11/tosca.relationships.HostedOn/kbrs40-gxqy68-108id-kbmurk",
114 "source": "services/inventory/v11/vserver/1024143488",
115 "target": "services/inventory/v11/pserver/1228865600",
118 "prevent-delete": "IN",
119 "delete-other-v": "NONE",
120 "contains-other-v": "NONE"
128 Code: 400 (BAD REQUEST)
129 Content: Error message describing the bad request failure.
130 Situation: Invalid Payload or schema error.
132 Code: 403 (FORBIDDEN)
133 Content: Error message describing the Authorization failure.
134 Situation: Authorization failure.
136 Code: 415 (UNSUPPORTED MEDIA TYPE)
137 Situation: Unsupported content type .
139 Code: 500 (Internal Server Error)
140 Content: Error message describing the failure.
141 Situation: Any scenario not covered by the above error codes.