Tokens

Think of a token as your digital key to the Pulsetic API. It's how you prove you're authorized to access and use the powerful monitoring tools within. Without it, the API won't know it's you.

Tokens are essential for security. They replace the need to send your username and password every time you make a request, keeping your credentials safe.

How Tokens Work

Pulsetic uses API tokens to securely manage access to your monitoring data and account features.

When you want to connect to Pulsetic's API, you'll include your unique token in what's called an "authorization" header—this is like showing your ID card to gain entry. The system then checks this token to verify you're authorized to access the information or perform actions you're requesting.

These tokens act as your digital permission slip. Each one is programmed with specific access rights that control exactly what you can and can't do through the API. Whether you're pulling reports or adjusting settings, nearly every API request will require a valid token for authentication.

For security, tokens are much safer than using passwords directly. Think of them like temporary access cards that can be canceled at any time. If a token gets compromised or you no longer need it, you can simply revoke that specific token without affecting your main account credentials. This gives you both security and flexibility in managing integrations.

By using this token system, Pulsetic ensures your data remains protected while still giving you programmatic access to all the monitoring tools and information you need.

Real-world Application

You have a screen showing your website's speed. Instead of using your main Pulsetic password, you make a special key (token) for that screen. This key only lets it see the data, not change anything. If the screen's key gets stolen, you just turn that key off, and your main account stays safe. This way, you keep your data safe while still using Pulsetic's tools in other places.

Using Your Token

Include your token in the Authorization header of your HTTP requests.

Example: Authorization: your_api_token_here

Use this header with all API calls that require authentication.