@itentialopensource/adapter-thingspace 0.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/.eslintignore +6 -0
- package/.eslintrc.js +18 -0
- package/.gitlab/.gitkeep +0 -0
- package/.gitlab/issue_templates/.gitkeep +0 -0
- package/.gitlab/issue_templates/Default.md +17 -0
- package/.gitlab/issue_templates/bugReportTemplate.md +76 -0
- package/.gitlab/issue_templates/featureRequestTemplate.md +14 -0
- package/.jshintrc +0 -0
- package/AUTH.md +39 -0
- package/BROKER.md +199 -0
- package/CALLS.md +422 -0
- package/CHANGELOG.md +9 -0
- package/CODE_OF_CONDUCT.md +43 -0
- package/CONTRIBUTING.md +172 -0
- package/ENHANCE.md +69 -0
- package/LICENSE +201 -0
- package/PROPERTIES.md +641 -0
- package/README.md +337 -0
- package/SUMMARY.md +9 -0
- package/SYSTEMINFO.md +11 -0
- package/TROUBLESHOOT.md +47 -0
- package/adapter.js +5026 -0
- package/adapterBase.js +1787 -0
- package/entities/.generic/action.json +214 -0
- package/entities/.generic/schema.json +28 -0
- package/entities/.system/action.json +69 -0
- package/entities/.system/mockdatafiles/getToken-default.json +3 -0
- package/entities/.system/mockdatafiles/healthcheck-default.json +3 -0
- package/entities/.system/schema.json +19 -0
- package/entities/.system/schemaTokenReq_MFA_Step_1.json +19 -0
- package/entities/.system/schemaTokenReq_MFA_Step_2.json +32 -0
- package/entities/.system/schemaTokenResp_MFA_Step_1.json +27 -0
- package/entities/.system/schemaTokenResp_MFA_Step_2.json +27 -0
- package/entities/Accounts/action.json +67 -0
- package/entities/Accounts/schema.json +21 -0
- package/entities/Callbacks/action.json +65 -0
- package/entities/Callbacks/mockdatafiles/listCallbacksUsingGET-default.json +23 -0
- package/entities/Callbacks/schema.json +21 -0
- package/entities/Devices/action.json +464 -0
- package/entities/Devices/mockdatafiles/addUsingPOST-default.json +23 -0
- package/entities/Devices/mockdatafiles/connectionListHistoryUsingPOST-default.json +868 -0
- package/entities/Devices/mockdatafiles/deleteUsingPOST-default.json +32 -0
- package/entities/Devices/mockdatafiles/provisioningHistoryListUsingPOST-default.json +427 -0
- package/entities/Devices/mockdatafiles/usageListUsingPOST-default.json +369 -0
- package/entities/Devices/schema.json +41 -0
- package/entities/Groups/action.json +106 -0
- package/entities/Groups/mockdatafiles/getListUsingGET-default.json +68 -0
- package/entities/Groups/schema.json +23 -0
- package/entities/Plans/action.json +25 -0
- package/entities/Plans/mockdatafiles/getServicePlanListUsingGET-default.json +98 -0
- package/entities/Plans/schema.json +19 -0
- package/entities/Requests/action.json +25 -0
- package/entities/Requests/schema.json +19 -0
- package/entities/Session/action.json +64 -0
- package/entities/Session/schema.json +21 -0
- package/entities/Sms/action.json +65 -0
- package/entities/Sms/schema.json +21 -0
- package/error.json +190 -0
- package/package.json +85 -0
- package/pronghorn.json +3761 -0
- package/propertiesDecorators.json +14 -0
- package/propertiesSchema.json +1249 -0
- package/refs?service=git-upload-pack +0 -0
- package/report/adapterInfo.json +10 -0
- package/report/creationReport.json +485 -0
- package/report/m2m-all.json +4020 -0
- package/sampleProperties.json +195 -0
- package/test/integration/adapterTestBasicGet.js +83 -0
- package/test/integration/adapterTestConnectivity.js +93 -0
- package/test/integration/adapterTestIntegration.js +1957 -0
- package/test/unit/adapterBaseTestUnit.js +950 -0
- package/test/unit/adapterTestUnit.js +2631 -0
- package/utils/adapterInfo.js +206 -0
- package/utils/addAuth.js +94 -0
- package/utils/artifactize.js +146 -0
- package/utils/basicGet.js +50 -0
- package/utils/checkMigrate.js +63 -0
- package/utils/entitiesToDB.js +178 -0
- package/utils/findPath.js +74 -0
- package/utils/methodDocumentor.js +225 -0
- package/utils/modify.js +154 -0
- package/utils/packModificationScript.js +35 -0
- package/utils/patches2bundledDeps.js +90 -0
- package/utils/pre-commit.sh +32 -0
- package/utils/removeHooks.js +20 -0
- package/utils/setup.js +33 -0
- package/utils/tbScript.js +246 -0
- package/utils/tbUtils.js +490 -0
- package/utils/testRunner.js +298 -0
- package/utils/troubleshootingAdapter.js +195 -0
- package/workflows/README.md +3 -0
package/CALLS.md
ADDED
|
@@ -0,0 +1,422 @@
|
|
|
1
|
+
## Using this Adapter
|
|
2
|
+
|
|
3
|
+
The `adapter.js` file contains the calls the adapter makes available to the rest of the Itential Platform. The API detailed for these calls should be available through JSDOC. The following is a brief summary of the calls.
|
|
4
|
+
|
|
5
|
+
### Generic Adapter Calls
|
|
6
|
+
|
|
7
|
+
These are adapter methods that IAP or you might use. There are some other methods not shown here that might be used for internal adapter functionality.
|
|
8
|
+
|
|
9
|
+
<table border="1" class="bordered-table">
|
|
10
|
+
<tr>
|
|
11
|
+
<th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
|
|
12
|
+
<th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
|
|
13
|
+
<th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
|
|
14
|
+
</tr>
|
|
15
|
+
<tr>
|
|
16
|
+
<td style="padding:15px">connect()</td>
|
|
17
|
+
<td style="padding:15px">This call is run when the Adapter is first loaded by he Itential Platform. It validates the properties have been provided correctly.</td>
|
|
18
|
+
<td style="padding:15px">No</td>
|
|
19
|
+
</tr>
|
|
20
|
+
<tr>
|
|
21
|
+
<td style="padding:15px">healthCheck(callback)</td>
|
|
22
|
+
<td style="padding:15px">This call ensures that the adapter can communicate with Thingspace. The actual call that is used is defined in the adapter properties and .system entities action.json file.</td>
|
|
23
|
+
<td style="padding:15px">No</td>
|
|
24
|
+
</tr>
|
|
25
|
+
<tr>
|
|
26
|
+
<td style="padding:15px">refreshProperties(properties)</td>
|
|
27
|
+
<td style="padding:15px">This call provides the adapter the ability to accept property changes without having to restart the adapter.</td>
|
|
28
|
+
<td style="padding:15px">No</td>
|
|
29
|
+
</tr>
|
|
30
|
+
<tr>
|
|
31
|
+
<td style="padding:15px">encryptProperty(property, technique, callback)</td>
|
|
32
|
+
<td style="padding:15px">This call will take the provided property and technique, and return the property encrypted with the technique. This allows the property to be used in the adapterProps section for the credential password so that the password does not have to be in clear text. The adapter will decrypt the property as needed for communications with Thingspace.</td>
|
|
33
|
+
<td style="padding:15px">No</td>
|
|
34
|
+
</tr>
|
|
35
|
+
<tr>
|
|
36
|
+
<td style="padding:15px">iapUpdateAdapterConfiguration(configFile, changes, entity, type, action, callback)</td>
|
|
37
|
+
<td style="padding:15px">This call provides the ability to update the adapter configuration from IAP - includes actions, schema, mockdata and other configurations.</td>
|
|
38
|
+
<td style="padding:15px">Yes</td>
|
|
39
|
+
</tr>
|
|
40
|
+
<tr>
|
|
41
|
+
<td style="padding:15px">iapFindAdapterPath(apiPath, callback)</td>
|
|
42
|
+
<td style="padding:15px">This call provides the ability to see if a particular API path is supported by the adapter.</td>
|
|
43
|
+
<td style="padding:15px">Yes</td>
|
|
44
|
+
</tr>
|
|
45
|
+
<tr>
|
|
46
|
+
<td style="padding:15px">iapSuspendAdapter(mode, callback)</td>
|
|
47
|
+
<td style="padding:15px">This call provides the ability to suspend the adapter and either have requests rejected or put into a queue to be processed after the adapter is resumed.</td>
|
|
48
|
+
<td style="padding:15px">Yes</td>
|
|
49
|
+
</tr>
|
|
50
|
+
<tr>
|
|
51
|
+
<td style="padding:15px">iapUnsuspendAdapter(callback)</td>
|
|
52
|
+
<td style="padding:15px">This call provides the ability to resume a suspended adapter. Any requests in queue will be processed before new requests.</td>
|
|
53
|
+
<td style="padding:15px">Yes</td>
|
|
54
|
+
</tr>
|
|
55
|
+
<tr>
|
|
56
|
+
<td style="padding:15px">iapGetAdapterQueue(callback)</td>
|
|
57
|
+
<td style="padding:15px">This call will return the requests that are waiting in the queue if throttling is enabled.</td>
|
|
58
|
+
<td style="padding:15px">Yes</td>
|
|
59
|
+
</tr>
|
|
60
|
+
<tr>
|
|
61
|
+
<td style="padding:15px">iapTroubleshootAdapter(props, persistFlag, adapter, callback)</td>
|
|
62
|
+
<td style="padding:15px">This call can be used to check on the performance of the adapter - it checks connectivity, healthcheck and basic get calls.</td>
|
|
63
|
+
<td style="padding:15px">Yes</td>
|
|
64
|
+
</tr>
|
|
65
|
+
|
|
66
|
+
<tr>
|
|
67
|
+
<td style="padding:15px">iapRunAdapterHealthcheck(adapter, callback)</td>
|
|
68
|
+
<td style="padding:15px">This call will return the results of a healthcheck.</td>
|
|
69
|
+
<td style="padding:15px">Yes</td>
|
|
70
|
+
</tr>
|
|
71
|
+
<tr>
|
|
72
|
+
<td style="padding:15px">iapRunAdapterConnectivity(callback)</td>
|
|
73
|
+
<td style="padding:15px">This call will return the results of a connectivity check.</td>
|
|
74
|
+
<td style="padding:15px">Yes</td>
|
|
75
|
+
</tr>
|
|
76
|
+
<tr>
|
|
77
|
+
<td style="padding:15px">iapRunAdapterBasicGet(callback)</td>
|
|
78
|
+
<td style="padding:15px">This call will return the results of running basic get API calls.</td>
|
|
79
|
+
<td style="padding:15px">Yes</td>
|
|
80
|
+
</tr>
|
|
81
|
+
<tr>
|
|
82
|
+
<td style="padding:15px">iapMoveAdapterEntitiesToDB(callback)</td>
|
|
83
|
+
<td style="padding:15px">This call will push the adapter configuration from the entities directory into the Adapter or IAP Database.</td>
|
|
84
|
+
<td style="padding:15px">Yes</td>
|
|
85
|
+
</tr>
|
|
86
|
+
<tr>
|
|
87
|
+
<td style="padding:15px">genericAdapterRequest(uriPath, restMethod, queryData, requestBody, addlHeaders, callback)</td>
|
|
88
|
+
<td style="padding:15px">This call allows you to provide the path to have the adapter call. It is an easy way to incorporate paths that have not been built into the adapter yet.</td>
|
|
89
|
+
<td style="padding:15px">Yes</td>
|
|
90
|
+
</tr>
|
|
91
|
+
<tr>
|
|
92
|
+
<td style="padding:15px">genericAdapterRequestNoBasePath(uriPath, restMethod, queryData, requestBody, addlHeaders, callback)</td>
|
|
93
|
+
<td style="padding:15px">This call is the same as the genericAdapterRequest only it does not add a base_path or version to the call.</td>
|
|
94
|
+
<td style="padding:15px">Yes</td>
|
|
95
|
+
</tr>
|
|
96
|
+
<tr>
|
|
97
|
+
<td style="padding:15px">iapHasAdapterEntity(entityType, entityId, callback)</td>
|
|
98
|
+
<td style="padding:15px">This call verifies the adapter has the specific entity.</td>
|
|
99
|
+
<td style="padding:15px">No</td>
|
|
100
|
+
</tr>
|
|
101
|
+
<tr>
|
|
102
|
+
<td style="padding:15px">iapVerifyAdapterCapability(entityType, actionType, entityId, callback)</td>
|
|
103
|
+
<td style="padding:15px">This call verifies the adapter can perform the provided action on the specific entity.</td>
|
|
104
|
+
<td style="padding:15px">No</td>
|
|
105
|
+
</tr>
|
|
106
|
+
<tr>
|
|
107
|
+
<td style="padding:15px">iapUpdateAdapterEntityCache()</td>
|
|
108
|
+
<td style="padding:15px">This call will update the entity cache.</td>
|
|
109
|
+
<td style="padding:15px">No</td>
|
|
110
|
+
</tr>
|
|
111
|
+
</table>
|
|
112
|
+
<br>
|
|
113
|
+
|
|
114
|
+
### Adapter Broker Calls
|
|
115
|
+
|
|
116
|
+
These are adapter methods that are used to integrate to IAP Brokers. This adapter currently supports the following broker calls.
|
|
117
|
+
|
|
118
|
+
<table border="1" class="bordered-table">
|
|
119
|
+
<tr>
|
|
120
|
+
<th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
|
|
121
|
+
<th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
|
|
122
|
+
<th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
|
|
123
|
+
</tr>
|
|
124
|
+
<tr>
|
|
125
|
+
<td style="padding:15px">hasEntities(entityType, entityList, callback)</td>
|
|
126
|
+
<td style="padding:15px">This call is utilized by the IAP Device Broker to determine if the adapter has a specific entity and item of the entity.</td>
|
|
127
|
+
<td style="padding:15px">No</td>
|
|
128
|
+
</tr>
|
|
129
|
+
<tr>
|
|
130
|
+
<td style="padding:15px">getDevice(deviceName, callback)</td>
|
|
131
|
+
<td style="padding:15px">This call returns the details of the requested device.</td>
|
|
132
|
+
<td style="padding:15px">Yes</td>
|
|
133
|
+
</tr>
|
|
134
|
+
<tr>
|
|
135
|
+
<td style="padding:15px">getDevicesFiltered(options, callback)</td>
|
|
136
|
+
<td style="padding:15px">This call returns the list of devices that match the criteria provided in the options filter.</td>
|
|
137
|
+
<td style="padding:15px">Yes</td>
|
|
138
|
+
</tr>
|
|
139
|
+
<tr>
|
|
140
|
+
<td style="padding:15px">isAlive(deviceName, callback)</td>
|
|
141
|
+
<td style="padding:15px">This call returns whether the device status is active</td>
|
|
142
|
+
<td style="padding:15px">Yes</td>
|
|
143
|
+
</tr>
|
|
144
|
+
<tr>
|
|
145
|
+
<td style="padding:15px">getConfig(deviceName, format, callback)</td>
|
|
146
|
+
<td style="padding:15px">This call returns the configuration for the selected device.</td>
|
|
147
|
+
<td style="padding:15px">Yes</td>
|
|
148
|
+
</tr>
|
|
149
|
+
<tr>
|
|
150
|
+
<td style="padding:15px">iapGetDeviceCount(callback)</td>
|
|
151
|
+
<td style="padding:15px">This call returns the count of devices.</td>
|
|
152
|
+
<td style="padding:15px">Yes</td>
|
|
153
|
+
</tr>
|
|
154
|
+
</table>
|
|
155
|
+
<br>
|
|
156
|
+
|
|
157
|
+
|
|
158
|
+
### Specific Adapter Calls
|
|
159
|
+
|
|
160
|
+
Specific adapter calls are built based on the API of the Thingspace. The Adapter Builder creates the proper method comments for generating JS-DOC for the adapter. This is the best way to get information on the calls.
|
|
161
|
+
|
|
162
|
+
<table border="1" class="bordered-table">
|
|
163
|
+
<tr>
|
|
164
|
+
<th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Method Signature</span></th>
|
|
165
|
+
<th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Description</span></th>
|
|
166
|
+
<th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Path</span></th>
|
|
167
|
+
<th bgcolor="lightgrey" style="padding:15px"><span style="font-size:12.0pt">Workflow?</span></th>
|
|
168
|
+
</tr>
|
|
169
|
+
<tr>
|
|
170
|
+
<td style="padding:15px">getAccountUsingGET(aname, callback)</td>
|
|
171
|
+
<td style="padding:15px">Returns information about a specified account</td>
|
|
172
|
+
<td style="padding:15px">{base_path}/{version}/accounts/{pathv1}?{query}</td>
|
|
173
|
+
<td style="padding:15px">Yes</td>
|
|
174
|
+
</tr>
|
|
175
|
+
<tr>
|
|
176
|
+
<td style="padding:15px">getServicesAndStatesUsingGET(aname, callback)</td>
|
|
177
|
+
<td style="padding:15px">Returns a list and details of all custom services and states defined for a specified account.</td>
|
|
178
|
+
<td style="padding:15px">{base_path}/{version}/accounts/{pathv1}/statesandservices?{query}</td>
|
|
179
|
+
<td style="padding:15px">Yes</td>
|
|
180
|
+
</tr>
|
|
181
|
+
<tr>
|
|
182
|
+
<td style="padding:15px">getListUsingGET1(aname, next, callback)</td>
|
|
183
|
+
<td style="padding:15px">When HTTP status is 202, a URL will be returned in the Location header of the form /leads/{aname}?next={token}. This URL can be used to request the next set of leads.</td>
|
|
184
|
+
<td style="padding:15px">{base_path}/{version}/leads/{pathv1}?{query}</td>
|
|
185
|
+
<td style="padding:15px">Yes</td>
|
|
186
|
+
</tr>
|
|
187
|
+
<tr>
|
|
188
|
+
<td style="padding:15px">getRequestStatusUsingGET(aname, requestId, callback)</td>
|
|
189
|
+
<td style="padding:15px">Returns the current status of an asynchronous request that was made for a single device.</td>
|
|
190
|
+
<td style="padding:15px">{base_path}/{version}/accounts/{pathv1}/requests/{pathv2}/status?{query}</td>
|
|
191
|
+
<td style="padding:15px">Yes</td>
|
|
192
|
+
</tr>
|
|
193
|
+
<tr>
|
|
194
|
+
<td style="padding:15px">listCallbacksUsingGET(aname, callback)</td>
|
|
195
|
+
<td style="padding:15px">Returns the name and endpoint URL of all callback listening services registered for a given account.</td>
|
|
196
|
+
<td style="padding:15px">{base_path}/{version}/callbacks/{pathv1}?{query}</td>
|
|
197
|
+
<td style="padding:15px">Yes</td>
|
|
198
|
+
</tr>
|
|
199
|
+
<tr>
|
|
200
|
+
<td style="padding:15px">registerCallbackUsingPOST(aname, body, callback)</td>
|
|
201
|
+
<td style="padding:15px">You are responsible for creating and running a listening process on your server at that URL.</td>
|
|
202
|
+
<td style="padding:15px">{base_path}/{version}/callbacks/{pathv1}?{query}</td>
|
|
203
|
+
<td style="padding:15px">Yes</td>
|
|
204
|
+
</tr>
|
|
205
|
+
<tr>
|
|
206
|
+
<td style="padding:15px">unregisterCallbackUsingDELETE(aname, sname, callback)</td>
|
|
207
|
+
<td style="padding:15px">Stops the platform from sending callback messages for the specified account and service.</td>
|
|
208
|
+
<td style="padding:15px">{base_path}/{version}/callbacks/{pathv1}/name/{pathv2}?{query}</td>
|
|
209
|
+
<td style="padding:15px">Yes</td>
|
|
210
|
+
</tr>
|
|
211
|
+
<tr>
|
|
212
|
+
<td style="padding:15px">activeUsingPOST(body, callback)</td>
|
|
213
|
+
<td style="padding:15px">If the devices do not already exist in the account, this API resource adds them before activation.</td>
|
|
214
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/activate?{query}</td>
|
|
215
|
+
<td style="padding:15px">Yes</td>
|
|
216
|
+
</tr>
|
|
217
|
+
<tr>
|
|
218
|
+
<td style="padding:15px">addUsingPOST(body, callback)</td>
|
|
219
|
+
<td style="padding:15px">Use this API if you want to manage some device settings before you are ready to activate service for the devices.</td>
|
|
220
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/add?{query}</td>
|
|
221
|
+
<td style="padding:15px">Yes</td>
|
|
222
|
+
</tr>
|
|
223
|
+
<tr>
|
|
224
|
+
<td style="padding:15px">updateContactInfoUsingPUT(body, callback)</td>
|
|
225
|
+
<td style="padding:15px">Sends a CarrierService callback message for each device in the request when the contact information has been changed, or if there was a problem and the change could not be completed.</td>
|
|
226
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/contactinfo?{query}</td>
|
|
227
|
+
<td style="padding:15px">Yes</td>
|
|
228
|
+
</tr>
|
|
229
|
+
<tr>
|
|
230
|
+
<td style="padding:15px">updateCustomFieldsUsingPUT(body, callback)</td>
|
|
231
|
+
<td style="padding:15px">Sends a CarrierService callback message for each device in the request when the custom fields have been changed, or if there was a problem and the change could not be completed.</td>
|
|
232
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/customFields?{query}</td>
|
|
233
|
+
<td style="padding:15px">Yes</td>
|
|
234
|
+
</tr>
|
|
235
|
+
<tr>
|
|
236
|
+
<td style="padding:15px">deactiveUsingPOST(body, callback)</td>
|
|
237
|
+
<td style="padding:15px">Deactivating service for a device may result in an early termination fee (ETF) being charged to the account, depending on the terms of the contract with Verizon. If your contract allows ETF waivers and if you want to use one for a particular deactivation, set the etfWaiver value to True.</td>
|
|
238
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/deactivate?{query}</td>
|
|
239
|
+
<td style="padding:15px">Yes</td>
|
|
240
|
+
</tr>
|
|
241
|
+
<tr>
|
|
242
|
+
<td style="padding:15px">deleteUsingPOST(body, callback)</td>
|
|
243
|
+
<td style="padding:15px">Use this API to remove unneeded devices from an account</td>
|
|
244
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/delete?{query}</td>
|
|
245
|
+
<td style="padding:15px">Yes</td>
|
|
246
|
+
</tr>
|
|
247
|
+
<tr>
|
|
248
|
+
<td style="padding:15px">listUsingPOST(body, callback)</td>
|
|
249
|
+
<td style="padding:15px">Returns information about a specified device or a list of devices in an account.</td>
|
|
250
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/list?{query}</td>
|
|
251
|
+
<td style="padding:15px">Yes</td>
|
|
252
|
+
</tr>
|
|
253
|
+
<tr>
|
|
254
|
+
<td style="padding:15px">imeiIccidMismatchListUsingPOST(body, callback)</td>
|
|
255
|
+
<td style="padding:15px">Returns a list of all 4G devices with an ICCID that was not activated with the expected IMEI.</td>
|
|
256
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/list/imeiiccidmismatch?{query}</td>
|
|
257
|
+
<td style="padding:15px">Yes</td>
|
|
258
|
+
</tr>
|
|
259
|
+
<tr>
|
|
260
|
+
<td style="padding:15px">moveUsingPut(body, callback)</td>
|
|
261
|
+
<td style="padding:15px">Move active devices from one billing account to another within a customer profile.</td>
|
|
262
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/move?{query}</td>
|
|
263
|
+
<td style="padding:15px">Yes</td>
|
|
264
|
+
</tr>
|
|
265
|
+
<tr>
|
|
266
|
+
<td style="padding:15px">gotostateUsingPut(body, callback)</td>
|
|
267
|
+
<td style="padding:15px">Changes the provisioning state of one or more devices to a specified customer-defined service and state.</td>
|
|
268
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/gotostate?{query}</td>
|
|
269
|
+
<td style="padding:15px">Yes</td>
|
|
270
|
+
</tr>
|
|
271
|
+
<tr>
|
|
272
|
+
<td style="padding:15px">updateServicePlanUsingPUT(body, callback)</td>
|
|
273
|
+
<td style="padding:15px">Sets a new service plan for one or more devices.</td>
|
|
274
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/plan?{query}</td>
|
|
275
|
+
<td style="padding:15px">Yes</td>
|
|
276
|
+
</tr>
|
|
277
|
+
<tr>
|
|
278
|
+
<td style="padding:15px">suspendUsingPOST(body, callback)</td>
|
|
279
|
+
<td style="padding:15px">Suspends service for one or more devices.</td>
|
|
280
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/suspend?{query}</td>
|
|
281
|
+
<td style="padding:15px">Yes</td>
|
|
282
|
+
</tr>
|
|
283
|
+
<tr>
|
|
284
|
+
<td style="padding:15px">restoreUsingPOST(body, callback)</td>
|
|
285
|
+
<td style="padding:15px">Restore service to one or more suspended devices.</td>
|
|
286
|
+
<td style="padding:15px">{base_path}/{version}/devices/actions/restore?{query}</td>
|
|
287
|
+
<td style="padding:15px">Yes</td>
|
|
288
|
+
</tr>
|
|
289
|
+
<tr>
|
|
290
|
+
<td style="padding:15px">deviceAvailabilityListUsingPOST(body, callback)</td>
|
|
291
|
+
<td style="padding:15px">Checks whether specified devices are registered by the manufacturer with the Verizon network and are available to be activated.</td>
|
|
292
|
+
<td style="padding:15px">{base_path}/{version}/devices/availability/actions/list?{query}</td>
|
|
293
|
+
<td style="padding:15px">Yes</td>
|
|
294
|
+
</tr>
|
|
295
|
+
<tr>
|
|
296
|
+
<td style="padding:15px">connectionListHistoryUsingPOST(body, callback)</td>
|
|
297
|
+
<td style="padding:15px">Each response includes a maximum of 500 records. To obtain more records, you can call the API multiple times, adjusting the earliest value each time to start where the previous request finished.</td>
|
|
298
|
+
<td style="padding:15px">{base_path}/{version}/devices/connections/actions/listHistory?{query}</td>
|
|
299
|
+
<td style="padding:15px">Yes</td>
|
|
300
|
+
</tr>
|
|
301
|
+
<tr>
|
|
302
|
+
<td style="padding:15px">changeCostCenterUsingPUT(body, callback)</td>
|
|
303
|
+
<td style="padding:15px">Changes or removes the costCenterCode value for one or more devices.</td>
|
|
304
|
+
<td style="padding:15px">{base_path}/{version}/devices/costCenter?{query}</td>
|
|
305
|
+
<td style="padding:15px">Yes</td>
|
|
306
|
+
</tr>
|
|
307
|
+
<tr>
|
|
308
|
+
<td style="padding:15px">getExtendedDiagsUsingPOST(body, callback)</td>
|
|
309
|
+
<td style="padding:15px">Returns basic diagnostic information about a specified device, including connectivity, provisioning, and billing status.</td>
|
|
310
|
+
<td style="padding:15px">{base_path}/{version}/devices/extendeddiagnostics/actions/list?{query}</td>
|
|
311
|
+
<td style="padding:15px">Yes</td>
|
|
312
|
+
</tr>
|
|
313
|
+
<tr>
|
|
314
|
+
<td style="padding:15px">provisioningHistoryListUsingPOST(body, callback)</td>
|
|
315
|
+
<td style="padding:15px">Returns the provisioning history of a device during a specified time period.</td>
|
|
316
|
+
<td style="padding:15px">{base_path}/{version}/devices/history/actions/list?{query}</td>
|
|
317
|
+
<td style="padding:15px">Yes</td>
|
|
318
|
+
</tr>
|
|
319
|
+
<tr>
|
|
320
|
+
<td style="padding:15px">prlListUsingPOST(body, callback)</td>
|
|
321
|
+
<td style="padding:15px">4G and GSM devices do not have a PRL.</td>
|
|
322
|
+
<td style="padding:15px">{base_path}/{version}/devices/prl/actions/list?{query}</td>
|
|
323
|
+
<td style="padding:15px">Yes</td>
|
|
324
|
+
</tr>
|
|
325
|
+
<tr>
|
|
326
|
+
<td style="padding:15px">getDeviceSuspensionStatusUsingPOST(body, callback)</td>
|
|
327
|
+
<td style="padding:15px">Returns DeviceSuspensionStatus callback messages containing the current device state and information on how many days a device has been suspended and can continue to be suspended.</td>
|
|
328
|
+
<td style="padding:15px">{base_path}/{version}/devices/suspension/status?{query}</td>
|
|
329
|
+
<td style="padding:15px">Yes</td>
|
|
330
|
+
</tr>
|
|
331
|
+
<tr>
|
|
332
|
+
<td style="padding:15px">usageListUsingPOST(body, callback)</td>
|
|
333
|
+
<td style="padding:15px">Returns the network data usage history of a device during a specified time period.</td>
|
|
334
|
+
<td style="padding:15px">{base_path}/{version}/devices/usage/actions/list?{query}</td>
|
|
335
|
+
<td style="padding:15px">Yes</td>
|
|
336
|
+
</tr>
|
|
337
|
+
<tr>
|
|
338
|
+
<td style="padding:15px">aggregateUsingPOST(body, callback)</td>
|
|
339
|
+
<td style="padding:15px">The information is returned in a callback response, so you must register a URL for DeviceUsage callback messages using the POST /callbacks API.</td>
|
|
340
|
+
<td style="padding:15px">{base_path}/{version}/devices/usage/actions/list/aggregate?{query}</td>
|
|
341
|
+
<td style="padding:15px">Yes</td>
|
|
342
|
+
</tr>
|
|
343
|
+
<tr>
|
|
344
|
+
<td style="padding:15px">changeDeviceIdUsingPUT(serviceType, body, callback)</td>
|
|
345
|
+
<td style="padding:15px">Changes the identifier of a 3G or 4G device to match hardware changes made for a line of service.</td>
|
|
346
|
+
<td style="padding:15px">{base_path}/{version}/devices/{pathv1}/actions/deviceId?{query}</td>
|
|
347
|
+
<td style="padding:15px">Yes</td>
|
|
348
|
+
</tr>
|
|
349
|
+
<tr>
|
|
350
|
+
<td style="padding:15px">createDeviceGroupUsingPOST(body, callback)</td>
|
|
351
|
+
<td style="padding:15px">Creates a new device group and optionally adds a set of devices to that group.</td>
|
|
352
|
+
<td style="padding:15px">{base_path}/{version}/groups?{query}</td>
|
|
353
|
+
<td style="padding:15px">Yes</td>
|
|
354
|
+
</tr>
|
|
355
|
+
<tr>
|
|
356
|
+
<td style="padding:15px">getListUsingGET(aname, callback)</td>
|
|
357
|
+
<td style="padding:15px">Returns a list of device groups in an account</td>
|
|
358
|
+
<td style="padding:15px">{base_path}/{version}/groups/{pathv1}?{query}</td>
|
|
359
|
+
<td style="padding:15px">Yes</td>
|
|
360
|
+
</tr>
|
|
361
|
+
<tr>
|
|
362
|
+
<td style="padding:15px">getDeviceGroupInfoUsingGET(aname, gname, next, callback)</td>
|
|
363
|
+
<td style="padding:15px">When HTTP status is 202, a URL will be returned in the Location header of the form /groups/{aname}/name/{gname}/?next={token}. This URL can be used to request the next set of groups.</td>
|
|
364
|
+
<td style="padding:15px">{base_path}/{version}/groups/{pathv1}/name/{pathv2}?{query}</td>
|
|
365
|
+
<td style="padding:15px">Yes</td>
|
|
366
|
+
</tr>
|
|
367
|
+
<tr>
|
|
368
|
+
<td style="padding:15px">updateDeviceGroupUsingPUT(aname, gname, body, callback)</td>
|
|
369
|
+
<td style="padding:15px">Make changes to a device group, including changing the name and description, and adding or removing devices.</td>
|
|
370
|
+
<td style="padding:15px">{base_path}/{version}/groups/{pathv1}/name/{pathv2}?{query}</td>
|
|
371
|
+
<td style="padding:15px">Yes</td>
|
|
372
|
+
</tr>
|
|
373
|
+
<tr>
|
|
374
|
+
<td style="padding:15px">deleteDeviceGroupUsingDELETE(aname, gname, callback)</td>
|
|
375
|
+
<td style="padding:15px">Deletes a device group. Devices in the group are moved to the default device group and are not deleted from the account.</td>
|
|
376
|
+
<td style="padding:15px">{base_path}/{version}/groups/{pathv1}/name/{pathv2}?{query}</td>
|
|
377
|
+
<td style="padding:15px">Yes</td>
|
|
378
|
+
</tr>
|
|
379
|
+
<tr>
|
|
380
|
+
<td style="padding:15px">getServicePlanListUsingGET(aname, callback)</td>
|
|
381
|
+
<td style="padding:15px">Returns a list of all data service plans that are associated with a specified account.</td>
|
|
382
|
+
<td style="padding:15px">{base_path}/{version}/plans/{pathv1}?{query}</td>
|
|
383
|
+
<td style="padding:15px">Yes</td>
|
|
384
|
+
</tr>
|
|
385
|
+
<tr>
|
|
386
|
+
<td style="padding:15px">loginUsingPOST(body, callback)</td>
|
|
387
|
+
<td style="padding:15px">Initiates a Connectivity Management session and returns a session token required in subsequent API requests.</td>
|
|
388
|
+
<td style="padding:15px">{base_path}/{version}/session/login?{query}</td>
|
|
389
|
+
<td style="padding:15px">Yes</td>
|
|
390
|
+
</tr>
|
|
391
|
+
<tr>
|
|
392
|
+
<td style="padding:15px">logoutUsingPOST(callback)</td>
|
|
393
|
+
<td style="padding:15px">Ends a Connectivity Management session.</td>
|
|
394
|
+
<td style="padding:15px">{base_path}/{version}/session/logout?{query}</td>
|
|
395
|
+
<td style="padding:15px">Yes</td>
|
|
396
|
+
</tr>
|
|
397
|
+
<tr>
|
|
398
|
+
<td style="padding:15px">resetUsingPUT(body, callback)</td>
|
|
399
|
+
<td style="padding:15px">The new password is effective immediately. Passwords do not expire, but Verizon recommends changing your password every 90 days.</td>
|
|
400
|
+
<td style="padding:15px">{base_path}/{version}/session/password/actions/reset?{query}</td>
|
|
401
|
+
<td style="padding:15px">Yes</td>
|
|
402
|
+
</tr>
|
|
403
|
+
<tr>
|
|
404
|
+
<td style="padding:15px">sendSmsMessageUsingPOST(body, callback)</td>
|
|
405
|
+
<td style="padding:15px">The messages are queued on the ThingSpace Platform and sent as soon as possible, but they may be delayed due to traffic and routing considerations.</td>
|
|
406
|
+
<td style="padding:15px">{base_path}/{version}/sms?{query}</td>
|
|
407
|
+
<td style="padding:15px">Yes</td>
|
|
408
|
+
</tr>
|
|
409
|
+
<tr>
|
|
410
|
+
<td style="padding:15px">getSmsMessagesUsingGET(aname, next, callback)</td>
|
|
411
|
+
<td style="padding:15px">When HTTP status is 202, a URL will be returned in the Location header of the form /sms/{aname}/history?next={token}. This URL can be used to request the next set of messages.</td>
|
|
412
|
+
<td style="padding:15px">{base_path}/{version}/sms/{pathv1}/history?{query}</td>
|
|
413
|
+
<td style="padding:15px">Yes</td>
|
|
414
|
+
</tr>
|
|
415
|
+
<tr>
|
|
416
|
+
<td style="padding:15px">startSmsCallbackUsingPUT(aname, callback)</td>
|
|
417
|
+
<td style="padding:15px">Starts delivery of queued SMS messages for the specific account.</td>
|
|
418
|
+
<td style="padding:15px">{base_path}/{version}/sms/{pathv1}/startCallbacks?{query}</td>
|
|
419
|
+
<td style="padding:15px">Yes</td>
|
|
420
|
+
</tr>
|
|
421
|
+
</table>
|
|
422
|
+
<br>
|
package/CHANGELOG.md
ADDED
|
@@ -0,0 +1,43 @@
|
|
|
1
|
+
# Contributor Covenant Code of Conduct
|
|
2
|
+
|
|
3
|
+
## Our Pledge
|
|
4
|
+
|
|
5
|
+
In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race, religion, or sexual identity and orientation.
|
|
6
|
+
|
|
7
|
+
## Our Standards
|
|
8
|
+
|
|
9
|
+
Examples of behavior that contributes to creating a positive environment include:
|
|
10
|
+
|
|
11
|
+
- Using welcoming and inclusive language
|
|
12
|
+
- Being respectful of differing viewpoints and experiences
|
|
13
|
+
- Gracefully accepting constructive criticism
|
|
14
|
+
- Focusing on what is best for the community
|
|
15
|
+
- Showing empathy towards other community members
|
|
16
|
+
|
|
17
|
+
Examples of unacceptable behavior by participants include:
|
|
18
|
+
|
|
19
|
+
- The use of sexualized language or imagery and unwelcome sexual attention or advances
|
|
20
|
+
- Trolling, insulting/derogatory comments, and personal or political attacks
|
|
21
|
+
- Public or private harassment
|
|
22
|
+
- Publishing others' private information, such as a physical or electronic address, without explicit permission
|
|
23
|
+
- Other conduct which could reasonably be considered inappropriate in a professional setting
|
|
24
|
+
|
|
25
|
+
## Our Responsibilities
|
|
26
|
+
|
|
27
|
+
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
|
|
28
|
+
|
|
29
|
+
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
|
|
30
|
+
|
|
31
|
+
## Scope
|
|
32
|
+
|
|
33
|
+
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
|
|
34
|
+
|
|
35
|
+
## Enforcement
|
|
36
|
+
|
|
37
|
+
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at support@itential.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.
|
|
38
|
+
|
|
39
|
+
Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project's leadership.
|
|
40
|
+
|
|
41
|
+
## Attribution
|
|
42
|
+
|
|
43
|
+
This Code of Conduct is adapted from the <a href="http://contributor-covenant.org" target="_blank">Contributor Covenant</a>, version 1.4, available at <a href="http://contributor-covenant.org/version/1/4/" target="_blank">version</a>
|