sensorpro

Use this skill to **manage your Sensorpro email marketing account in OpenClaw**.

Official docs:
- Home: https://sensorpro.net/api/
- Contacts: https://sensorpro.net/api/contacts.html
- Campaigns + metrics: https://sensorpro.net/api/campaigns.html
- Relay Email: https://sensorpro.net/api/sendemail.html
- Imports: https://www.sensorpro.net/api/imports.html
- Account: https://sensorpro.net/api/account.html

## Setup (required)
Set these environment variables in your OpenClaw `.env` (or in the shell before running curl):

- `SENSORPRO_API_KEY` — API key for the `x-apikey` header
- `SENSORPRO_ORG` — organization code/name
- `SENSORPRO_USER` — API username (**must be an API user**)
- `SENSORPRO_PASS` — API user password

### How to get the API key
From the Sensorpro UI:
1) Go to **API → API keys**
2) Select **“Sensorpro rest API default key”**
3) Copy the key value into `SENSORPRO_API_KEY`
4) If your API key is IP-restricted, whitelist the **calling IP** (the machine running OpenClaw)

The key is passed as an HTTP header:
- `x-apikey: $SENSORPRO_API_KEY`

### How to create an API user
Sensorpro distinguishes between UI users and API users:
- **API users** have *no UI access* but **can** use the REST API.
- **Normal users** have UI access but typically **cannot** use the REST API.

Create a dedicated **API user** in Sensorpro and set:
- `SENSORPRO_USER` to that username
- `SENSORPRO_PASS` to that password

### Safe secret handling (important)
- Put secrets in `~/.openclaw/.env` (or your process manager), **not** in `SKILL.md`.
- Don’t commit `.env` to git.
- Rotate the API key if it’s ever pasted into a public place.

## Global gotchas
- **IP allowlisting**: Sensorpro REST API can be locked to whitelisted IPs.
- Every response includes `Result.TotalErrors`; treat `0` as success.
- **Signin token** (`Token`) must be used in the URL path for most endpoints.
- **Logoff**: server may require a body (HTTP 411 otherwise). Use `-d '{}'`.

## Quick workflow pattern (recommended)...