Security protocols, API keys, JSON Web Tokens (JWT), and Role-Based Access Control (RBAC).

Authentication & Security

Security and client data confidentiality are paramount. All requests against protected Nexium Media APIs require cryptographic verification.

Authentication Mechanisms

API Keys: Used for server-to-server integration between client websites and our CRM. Keys begin with prefix nexium_live_ or nexium_test_.
Bearer JWT Tokens: Used for authenticated client portal and admin sessions.

Provide your API key or Bearer token via the Authorization header:

curl -X GET "https://api.nexiummedia.com/v1/campaigns" \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json"

Never transmit authorization tokens in URL query parameters. Query parameters are logged in load balancers and browser histories.

User permissions are evaluated using four hierarchical roles:

Client Viewer: Read-only access to campaign analytics, SEO audit reports, and invoices.
Client Manager: Can submit change requests and review staging mockups.
Agency Developer: Full engineering access to repositories, deployments, and staging servers.
Agency Admin: Full administrative governance, financial billing, and token generation rights.