REST Resources
-
/ -
/acknowledge-device-fingerprint -
/change-device-credentials -
/devices -
/devices /{device-id} /activate-modeled-device -
/devices /{device-id} /applicable-configlets -
/devices /{device-id} /apply-cli-configlet -
/devices /{device-id} /associated-softwares -
/devices /{device-id} /clone -
/devices /{device-id} /compute-configlet-parameter-values -
/devices /{device-id} /configlet -
/devices /{device-id} /configurations /expanded -
/devices /{device-id} /configurations /raw -
/devices /{device-id} /validate-cli-configlet -
/devices /{id} -
/devices /{id} /associated-scripts -
/devices /{id} /change-requests -
/devices /{id} /configurations -
/devices /{id} /configurations /expanded /match-content -
/devices /{id} /configurations /raw /match-content -
/devices /{id} /connection-status -
/devices /{id} /exec-resync -
/devices /{id} /exec-rpc -
/devices /{id} /managed-elements -
/devices /{id} /managed-status -
/devices /{id} /modify-device-target-ip -
/devices /{id} /view-customized-attributes -
/discover-devices -
/discoveryresult /{id} -
/get-syslog-events -
/stop-syslog-events -
/stop-syslog-events /{id}
/api/space/device-management/devices/{device-id}/activate-modeled-device
The following operations are supported on this resource:
| POST /devices/{device-id}/activate-modeled-device | Version 1 |
Sample Usage
This API makes an asynchronous method call, so you can, optionally, specify queue and schedule parameters:
POST /devices/{device-id}/activate-modeled-device?queue=<queue>&schedule=<schedule>
Note: The queue URL denoted by <queue> must have been created already.
-
Parameters:
Name Type URI Type Description Required device-id Integer Path Y queue Queue URL Query A fully qualified queue URL, where job progress notifications will be sent (See Asynchronous API Usage) N schedule cron-like-expression Query Schedule this API in the future, by specifying a cron-like-expression (See Job Scheduling) N
-
Content-Type Headers:
application/vnd.net.juniper.space.device-management.activate-modeled-device-device-init-request+xml;version=1;charset=UTF-8
application/vnd.net.juniper.space.device-management.activate-modeled-device-device-init-request+json;version=1;charset=UTF-8 -
Accept Headers:
application/vnd.net.juniper.space.job-management.task+xml;version=1
application/vnd.net.juniper.space.job-management.task+json;version=1
<activate-modeled-device-device-init-request>
<connection-profile href="/api/space/device-management/modeled-device-management/connection-profiles/{id}">
<name>String</name>
</connection-profile>
<static-ip>String</static-ip>
<subnet-id>String</subnet-id>
<gateway>String</gateway>
<serial-number-validation>Boolean</serial-number-validation>
<user-name>String</user-name>
<password>String</password>
<key-based>Boolean</key-based>
<serial-number>String</serial-number>
<Configuration-update-type>AUTOMATIC</Configuration-update-type>
</activate-modeled-device-device-init-request>
{
"activate-modeled-device-device-init-request" : {
"connection-profile" : {
"@href" :
"/api/space/device-management/modeled-device-management/connection-profiles/{id}"
,
"name" : "String"
} ,
"static-ip" : "String" ,
"subnet-id" : "String" ,
"gateway" : "String" ,
"serial-number-validation" : "Boolean" ,
"user-name" : "String" ,
"password" : "String" ,
"key-based" : "Boolean" ,
"serial-number" : "String" ,
"Configuration-update-type" : "AUTOMATIC"
}
}
Access Control
The following capabilities are required to access this API: ManageActivation
| POST /devices/{device-id}/activate-modeled-device | Version 1 |
Sample Usage
This API makes an asynchronous method call, so you can, optionally, specify queue and schedule parameters:
POST /devices/{device-id}/activate-modeled-device?queue=<queue>&schedule=<schedule>
Note: The queue URL denoted by <queue> must have been created already.
-
Parameters:
Name Type URI Type Description Required device-id Integer Path Y queue Queue URL Query A fully qualified queue URL, where job progress notifications will be sent (See Asynchronous API Usage) N schedule cron-like-expression Query Schedule this API in the future, by specifying a cron-like-expression (See Job Scheduling) N
-
Content-Type Headers:
application/vnd.net.juniper.space.device-management.activate-modeled-device-space-init-request+xml;version=1;charset=UTF-8
application/vnd.net.juniper.space.device-management.activate-modeled-device-space-init-request+json;version=1;charset=UTF-8 -
Accept Headers:
application/vnd.net.juniper.space.job-management.task+xml;version=1
application/vnd.net.juniper.space.job-management.task+json;version=1
<activate-modeled-device-space-init-request>
<host>String</host>
<user-name>String</user-name>
<password>String</password>
<key-based>Boolean</key-based>
<create-new-user>Boolean</create-new-user>
<new-user-name>String</new-user-name>
<new-user-password>String</new-user-password>
<new-user-key-based>Boolean</new-user-key-based>
<serial-number-validation>Boolean</serial-number-validation>
<serial-number>String</serial-number>
<configuration-update-type>AUTOMATIC</configuration-update-type>
</activate-modeled-device-space-init-request>
{
"activate-modeled-device-space-init-request" : {
"host" : "String" ,
"user-name" : "String" ,
"password" : "String" ,
"key-based" : "Boolean" ,
"create-new-user" : "Boolean" ,
"new-user-name" : "String" ,
"new-user-password" : "String" ,
"new-user-key-based" : "Boolean" ,
"serial-number-validation" : "Boolean" ,
"serial-number" : "String" ,
"configuration-update-type" : "AUTOMATIC"
}
}
Access Control
The following capabilities are required to access this API: ManageActivation