Celerium_MyITProcessAPI
Buy me a coffee
Whether you use this project, have learned something from it, or just like it, please consider supporting it by buying me a coffee, so I can dedicate more time on open-source projects like this :)
About The Project
The MyITProcessAPI offers users the ability to extract data from MyITProcess into third-party reporting tools and aims to abstract away the details of interacting with MyITProcess’s API endpoints in such a way that is consistent with PowerShell nomenclature. This gives system administrators and PowerShell developers a convenient and familiar way of using MyITProcess’s API to create documentation scripts, automation, and integrations.
- :book: Project documentation can be found on Github Pages
- :book: MyITProcess’s REST API documentation here.
MyITProcess features a REST API that makes use of common HTTPs GET actions. In order to maintain PowerShell best practices, only approved verbs are used.
- GET -> Get-
Additionally, PowerShell’s verb-noun
nomenclature is respected. Each noun is prefixed with MyITProcess
in an attempt to prevent naming problems.
For example, one might access the /clients
endpoint by running the following PowerShell command with the appropriate parameters:
Get-MyITProcessClients
Install
This module can be installed directly from the PowerShell Gallery with the following command:
Install-Module -Name MyITProcessAPI
- :information_source: This module supports PowerShell 5.0+ and should work in PowerShell Core.
- :information_source: If you are running an older version of PowerShell, or if PowerShellGet is unavailable, you can manually download the main branch and place the MyITProcessAPI folder into the (default)
C:\Program Files\WindowsPowerShell\Modules
folder.
Project documentation can be found on Github Pages
- A full list of functions can be retrieved by running
Get-Command -Module MyITProcessAPI
. - Help info and a list of parameters can be found by running
Get-Help <command name>
, such as:
Get-Help Get-MyITProcessClients
Get-Help Get-MyITProcessClients -Full
Initial Setup
After installing this module, you will need to configure both the base URI & API key that are used to talk with the MyITProcess API.
- Run
Add-MyITProcessBaseURI
- By default, MyITProcess’s
https://reporting.live.myitprocess.com/public-api/v1
URI is used. - If you have your own API gateway or proxy, you may put in your own custom URI by specifying the
-base_uri
parameter:Add-MyITProcessBaseURI -base_uri http://myapi.gateway.celerium.org
- By default, MyITProcess’s
- Run
Add-MyITProcessAPIKey -Api_Key 123456789
- It will prompt you to enter your API key if you do not specify them.
- MyITProcess API key are generated via the MyITProcess portal
- [optional] Run
Export-MyITProcessModuleSettings
- This will create a config file at
%UserProfile%\MyITProcessAPI
that holds the base uri & API key information. - Next time you run
Import-Module -Name MyITProcessAPI
, this configuration file will automatically be loaded. - :warning: Exporting module settings encrypts your API key in a format that can only be unencrypted by the user principal that encrypted the secret. It makes use of .NET DPAPI, which for Windows uses reversible encrypted tied to your user principal. This means that you cannot copy your configuration file to another computer or user account and expect it to work.
- :warning: However in Linux\Unix operating systems the secret keys are more obfuscated than encrypted so it is recommend to use a more secure & cross-platform storage method.
- This will create a config file at
Usage
Calling an API resource is as simple as running Get-MyITProcess<resourceName>
- The following is a table of supported functions and their corresponding API resources:
Category | EndpointUri | Method | Function |
---|---|---|---|
clients | /clients | GET | Get-MyITProcessClients |
findings | /findings | GET | Get-MyITProcessFindings |
initiatives | /initiatives | GET | Get-MyITProcessInitiatives |
meetings | /meetings | GET | Get-MyITProcessMeetings |
recommendations | /recommendations | GET | Get-MyITProcessRecommendations |
recommendations | /recommendations/{recommendationId}/configurations | GET | Get-MyITProcessRecommendations |
reviews | /reviews | GET | Get-MyITProcessReviews |
reviews | /reviews/categories/overdue | GET | Get-MyITProcessReviews |
users | /users | GET | Get-MyITProcessUsers |
Each Get-MyITProcess*
function will respond with the raw data that MyITProcess’s API provides.
- :warning: Returned data is mostly structured the same but can vary between commands.
page
- The current page numberpageSize
- The amount of data per page numbertotalCount
- The total number of objects founditems
- The actual information that was requested
Roadmap
- Add Changelog
- Add example scripts & automation
See the open issues for a full list of proposed features (and known issues).
Contributing
Contributions are what makes the open-source community such an amazing place to learn, inspire, and create. Any contributions you make are greatly appreciated.
If you have a suggestion that would make this better, please fork the repo and create a pull request. You can also simply open an issue with the tag “enhancement”. Don’t forget to give the project a star! Thanks again!
See the CONTRIBUTING guide for more information about contributing.
License
Distributed under the MIT License. See LICENSE
for more information.
Contact
Acknowledgments
Big thank you to the following people and services as they have provided me with lots of helpful information as I continue this project!