Property
GET /v2/property/overview returns the property the bearer token is bound to. It checks no scope, so it answers any valid token: API or MCP, any scope set. Use it as a connectivity check before anything else.
| Method | Path | Scope |
|---|---|---|
| GET | /v2/property/overview | none |
curl https://api.snipform.io/v2/property/overview \ -H "Authorization: Bearer YOUR_TOKEN"{ "code": 200, "status": "OK", "data": { "id": "64f1c2a9e4b0a1b2c3d4e5f6", "name": "acme.com", "domain": "acme.com", "has_signals": true, "state": "active", "state_name": "Active", "counts": { "sessions": 48211, "forms": 3, "pages": 1 } }}Fields
Section titled “Fields”| Key | Type | Meaning |
|---|---|---|
id | string | The property id. Same value the dashboard shows in its URLs and the MCP endpoint uses in /mcp/{property} |
name | string | Display name. Often equals the domain |
domain | string | The registered base domain. The tracker and forms only accept requests whose referrer matches it |
has_signals | bool | true once the tracker has recorded at least one session. Until then every analytics endpoint answers 404 |
state | string | active, inactive or archived |
state_name | string | Human label for state: Active, Inactive, Archived |
counts.sessions | int | Total sessions recorded to date |
counts.forms | int | Forms on the property |
counts.pages | int | SnipContent pages on the property |
counts are lifetime counters maintained as data arrives, not a live query. For windowed numbers use Signals analytics.
Failure modes
Section titled “Failure modes”| HTTP | Meaning |
|---|---|
| 401 | Token missing, invalid, expired or revoked |
| 403 | Token is not scoped to a property. The token was not issued from a property’s API page |
| 404 | Token property no longer exists. The property was deleted after the token was created |