Authentication

All API requests require authentication via an API key.

Obtaining an API Key

1. Log in to the portal at eco.partnersignals.ai
2. Go to Settings → Integrations → API
3. Click Generate API Key
4. Copy the key — it is only shown once

Store your API key securely. Do not commit it to version control or include it in client-side code.

Using Your API Key

Pass your API key in the Authorization header as a Bearer token:

curl https://api.partnersignals.ai/v1/signals \
  -H "Authorization: Bearer ps_live_your_key_here"

API Key Scopes

When generating a key, select the scopes it needs:

Scope	Access
signals:read	Read signals and signal history
partners:read	Read partner roster and detail
attribution:read	Read attribution records and reports
attribution:write	Create and update attribution records
admin	Full access including team and settings management

Principle of least privilege: create separate keys per integration with only the scopes each integration needs.

Key Rotation

API keys do not expire automatically. Rotate keys:

• On team member offboarding
• If a key is accidentally exposed
• As part of your regular security rotation schedule

To rotate: generate a new key, update your integrations, then revoke the old key in the portal.

MCP Gateway Authentication

If you're connecting via the MCP Gateway (for AI agent integrations), use your API key in the MCP server config instead of a Bearer header. See MCP Gateway for setup details.

Errors

Code	Meaning
401 Unauthorized	Missing or invalid API key
403 Forbidden	Valid key but insufficient scope
429 Too Many Requests	Rate limit exceeded