Authentication

Signal API V2 authenticates requests with an API key in HTTP headers.

Scope

This page documents only V2 behavior (/v2/...).

Authentication model

Protected endpoints read the API key from request headers.

Accepted header names:

Header	Required	Description
X-Api-Key	yes	Primary header used by V2 request parsing.
X_API_KEY	yes	Supported alternate header name.

Authorization: Bearer <token> is not used by V2 authentication.

Example authenticated request

curl -X POST "$SIGNAL_API_BASE_URL/post/search" \
	-H "X-Api-Key: $SIGNAL_API_KEY" \
	-H "Content-Type: application/json" \
	-d '{
		"project": "example_project",
		"size": 10
	}'

Recommended environment values:

export SIGNAL_API_BASE_URL="https://apiv2.signal.buzztech.it/v2"
export SIGNAL_API_KEY="<api_key>"

Permissions and tiers

V2 authorization is tier-based. Lower tier number means higher privileges.

Tier	Role	Capabilities
1	Administrator	Full control across the platform, including all project, job, post, and tagging operations.
2	Superuser	Can create and edit projects, manage project configuration, and perform advanced project-level operations.
3	Editor	Can edit posts and perform day-to-day content operations such as post updates and tagging workflows.
4	User	Can see projects and access standard read-oriented project and post views.

Access depends on your account tier and endpoint permissions.

Capability guide

• Tier 1 (Administrator): unrestricted access to all available API actions.
• Tier 2 (Superuser): broad management access focused on creating and maintaining projects.
• Tier 3 (Editor): operational access focused on editing and organizing collected content.
• Tier 4 (User): visibility access for project exploration and monitoring use cases.