---
title: "Send a Request with Try it · COUNT Partner API"
description: "Watch a signed Partner API request go out from the browser — credentials, a connected workspace, an endpoint from the reference, and the raw 200 that comes…"
canonical: "https://developers.getcount.com/tutorials/try-it"
source: "https://developers.getcount.com/tutorials/try-it"
---
Tutorials

# Send a request with Try it

Try it signs a real Partner API request from your browser against a workspace you connect — no server, no client library, and the raw response on screen so you can see exactly what your own code will receive.

4 steps · about 32 seconds · from pasting credentials to a live 200

## What you just saw

1. 1 Credentials never leave your tab The signature is computed in the browser, so the clientSecret reaches neither COUNT nor this docs site. Both values live in sessionStorage and are gone when the tab closes.
2. 2 The redirect URI is this page Connecting a workspace runs the real OAuth flow, so the Try it URL has to be registered in your app’s redirect URLs in COUNT Partners before Connect will work.
3. 3 The endpoint field completes against the reference Picking a route fills in its method and path parameters, so a malformed URL is not one of the things that can go wrong while you are debugging auth.
4. 4 Every header is on screen Try it drops the /partners prefix from the signed path for you and shows what it sent, so a 401 tells you which of the two auth layers failed rather than leaving you guessing.

## Where to go next

[Open Try it](https://developers.getcount.com/tools/try-it) [Signature generator](https://developers.getcount.com/tools/signature-generator) [Errors & troubleshooting](https://developers.getcount.com/getting-started/errors)