Creating the Member API Keys (Connectwise)

There are four steps to creating the Member API and then updating MSPCFO.

  1. Create a new security role
  2. Create a new API member with the new security role
  3. Create the keys for the new member
  4. Update MSPCFO

It should not take more than a few minutes.

1.  Create a new security role

In Connectwise, under System/Security Roles, click on the plus to create a new security role.

1.  Create a new security role

Select System to adjust the settings.

Select System to adjust the settings.

Change only Inquire level on the API reports to All - do not change anything else.

Change only Inquire level on the API reports to All - do not change anything else.

2.  Create new API member

Under System/Members, select the API Members tab and press the plus to create a new member.

2.  Create new API member

Add the information for the new member

Only one field matters on the page, but you are required to enter data throughout.  Once you establish the Security Role ID as the new MSPCFO role, you can enter any dummy information into the other required fields.  The other fields do not affect our ability to pull data or your system (we have been assured of this by CW).

Add the information for the new member

3.  Create the API Keys and store them

Select the new member and create API keys for that member

3.  Create the API Keys and store them

Create the keys

Create the keys

Name the key and press save

Name the key and press save

Record the keys

CW will only show you the private key on this screen and then the one after. If you do not record it now, it will be encrypted and you will not be able to access it again.

Record the keys

We now only need the URL for your CW server (even it is in the cloud) and your CW ID.  

4. Complete the update in MSPCFO

On any MSPCFO screen, click on your name at the top right of the screen to see the pull-down menu. Click on "Api Credentials"  button.

Copy and paste the Public Key and the Private Key into MSPCFO. Then Save the record.

0 Comments

Add your comment

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.