<back to all web services
Location
Manage Logins Locations data points.
The following routes are available for this service:POST | /logins/location | Create Location. | |
---|
PUT | /logins/location | Update a Location for logins. | |
---|
DELETE | /logins/location/{locationId} | Remove specified Location. | |
---|
Location Parameters:Name | Parameter | Data Type | Required | Description |
---|
locationId | path | Guid | No | |
applicationId | body | Guid | No | |
location | body | string | No | |
locationType | body | Guid | No | |
datacenterId | body | Guid | No | |
datacenterCode | body | DatacenterLocations | No | Allowable Values- ACD
- GMU
- SPA
- LAS
- DEV
- VCD
- AWS
- GCP
- UAT
- AZU
- CNW
- AUV
- ATL
- EXT
|
DatacenterLocations Enum:ACD | |
GMU | |
SPA | |
LAS | |
DEV | |
VCD | |
AWS | |
GCP | |
UAT | |
AZU | |
CNW | |
AUV | |
ATL | |
EXT | |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
HTTP + XML
The following are sample HTTP requests and responses.
The placeholders shown need to be replaced with actual values.
POST /logins/location HTTP/1.1
Host: n3tapi.palmettovdc.com
Accept: application/xml
Content-Type: application/xml
Content-Length: length
<Location xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/N3TAPI.Services.DTO">
<applicationId>00000000-0000-0000-0000-000000000000</applicationId>
<datacenterCode>ACD</datacenterCode>
<datacenterId>00000000-0000-0000-0000-000000000000</datacenterId>
<location>String</location>
<locationId>00000000-0000-0000-0000-000000000000</locationId>
<locationType>00000000-0000-0000-0000-000000000000</locationType>
</Location>