Enviance Compliance API declares
2 security schemes
for authenticating requests.
It defines a basic scheme (Basic).
An API key is passed in the header as Authorization (EnvianceAuth).
Basic — Forces authentication with credentials via an api gateway
EnvianceAuth — Enviance \ . Obtain SessionId by POST /ver2/AuthenticationService.svc/sessions first
Paths & Operations 7
Across 3 paths, the API surfaces 7 operations — 2 DELETE, 2 GET, 2 PATCH, 1 POST. Each is listed below with its method, path, parameters, and response codes.
Compliance 7
POST
/ver2/ComplianceService.svc/locations
Creates a new Location object in the Compliance Model, optionally by copying the structure from another Location to the new Location. Supported object types are Division, Facility (Program), Unit (El…
Updates (and potentially moves) an existing Location object in the Compliance Model. Specifying a new parent path moves the Location underneath another parent Location. Updating the Custom Field Temp…
The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are Enviance.RestServices.Ver2.ComplianceModel.LocationInfo (33 properties), Enviance.RestServices.Ver2.ComplianceModel.RegulatoryIdentificationInfo (15 properties), Enviance.RestServices.Ver2.ComplianceModel.GeoLocation (14 properties), Enviance.RestServices.Ver2.ComplianceModel.Address (8 properties). Each schema is shown below with its type and property counts.
