question

What steps are you following? It sounds like you don't have a valid api token. Maybe this will help - https://www.clover.com/help/create-an-api-token-hosted-checkout/.

I have gone through these documents. I used the Powershell script supplied in docs, and replaced the required fields I.e. MerchantID, PrivateKey and Email, resulting in the following error:

Invoke-RestMethod : The remote server returned an error: (401) Unauthorized.

At line:30 char:13

+ $response = Invoke-RestMethod 'https://dev1.dev.clover.com/invoicingc ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException

+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

I have been referencing the documentation, I used the Windows Powershell script for testing which was in the documentation, replacing the required fields from my dashboard / API Token interface (MerchID PrvtKey and email), resulting in the following error:

Invoke-RestMethod : The remote server returned an error: (401) Unauthorized.

At line:30 char:13

+ $response = Invoke-RestMethod 'https://dev1.dev.clover.com/invoicingc ...

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

+ CategoryInfo : InvalidOperation: (System.Net.HttpWebRequest:HttpWebRequest) [Invoke-RestMethod], WebException

+ FullyQualifiedErrorId : WebCmdletWebResponseException,Microsoft.PowerShell.Commands.InvokeRestMethodCommand

I am trying to hit the sandbox I believe. I created the API token in the sandbox account.

I tried to reply to this answer in the forum by clicking the link below, but I could only see your previously answered question 23 hrs. ago.

I go the script from:

https://docs.clover.com/docs/testing-your-hosted-checkout-integration-windows

I am trying to hit the sandbox I believe. I created the API token in the sandbox account.

I ran into this problem as well. When is the documentation going to be updated? And while you're at it, the "lastName" line in the PowerShell script has a bug in the termination of the quotes.

Type the following cmdlet and then hit Enter: "Restart-Service WinRM". It's time to test the connection, From the MID Server execute the following cmdlet into PowerShell and then hit Enter: "Test-WsMan <Target IP>" and This simple command tests whether the WinRM service is running on the remote Host. retro bowl college

To test Hosted Checkout with PowerShell, ensure your API key is correct and included in the headers. Authentication errors are common; verifying credentials is essential, just like ensuring solar panels energy are correctly installed.

It looks like you're running into authentication issues while testing the Hosted Checkout with PowerShell. A 401 Unauthorized error usually means that your credentials aren't being accepted. Make sure you're using the correct API keys and any required headers in your request.For a change of pace, if you enjoy online games, Pokerogue and Pokerogue Dex offer a great community and resources for poker enthusiasts!