The EmpowerID Web API is built on the principles of REST and is organized around the components (resource objects, like user accounts, EmpowerID people, Exchange mailboxes, workflows, etc.,) of the EmpowerID platform. The articles in this section provide "walkthrough" examples of calling the EmpowerID Web API to return information about those objects as well as performing CRUD operations around those same objects.
| Easy html macro |
|---|
| theme | {"label":"solarized_dark","value":"solarized_dark"} |
|---|
| contentByMode | {"html":"<!doctype html>\r\n<link href=\"https://cdn.jsdelivr.net/npm/bootstrap@5.0.2/dist/css/bootstrap.min.css\" rel=\"stylesheet\" integrity=\"sha384-EVSTQN3/azprG1Anm3QDgpJLIm9Nao0Yz1ztcQTwFspd3yD65VohhpuuCOmLASjC\" crossorigin=\"anonymous\">\r\n<link href=\"https://docs.empowerid.com/new_docs.css\" rel=\"stylesheet\">\r\n<script src=\"https://cdn.jsdelivr.net/npm/bootstrap@5.0.2/dist/js/bootstrap.bundle.min.js\" integrity=\"sha384-MrcW6ZMFYlzcLA8Nl+NtUVF0sA7MsXsP1UyJoMp4YLEuNSfAP+JcXn/tWtIaxVXM\" crossorigin=\"anonymous\"></script>\r\n \r\n<div class = \"bd-callout bd-callout-info\">\r\n <p>All external requests to the EmpowerID \r\n API require an OAuth 2.0 Bearer token (JWT) be present in the Authorization header.\r\n This requires a unique API Key, Client Secret, and Client ID, which can be generated\r\n by <a href=\"https://dotnetworkflow.jira.com/wiki/spaces/EDGV21/pages/1606353148/Register+an+OAuth+Application\">\r\n Registering an OAuth Application in EmpowerID</a>. After registering the applicaiton, use \r\n the EmpowerID API to <a href=\"https://dotnetworkflow.jira.com/wiki/spaces/EDGV21/pages/1606353279/Get+an+Access+Token\">\r\n Get an access token</a>.</p>\r\n</div>","javascript":"","css":""} |
|---|
|
|
