SeggWat LogoSeggWat
Dashboard

API Overview

Get started with the SeggWat API, including base URLs and authentication methods.

Base URLs

Environment Base URL
Production https://seggwat.com/api/v1
Staging https://seggwat.oxidt.com/api/v1

Authentication

SeggWat uses Organization Access Tokens (OAT) to authenticate API requests. These tokens grant access to all projects within your organization.

Creating an API Token

  1. Log in to the SeggWat Dashboard
  2. Navigate to Settings from the sidebar
  3. Click on API Tokens tab
  4. Click Create New Token
  5. (Optional) Add a label to identify the token (e.g., "Production Server", "CI/CD Pipeline")
  6. Copy the generated token immediately - it will only be shown once

Using the API Token

Include your token in the X-API-Key header for all authenticated requests:

http
X-API-Key: oat_xxxxxxxxxxxxxxxxxxxxx
curl -X GET "https://seggwat.com/api/v1/projects/{project_id}/feedback" \
  -H "X-API-Key: oat_xxxxxxxxxxxxxxxxxxxxx" \
  -H "Content-Type: application/json"

Token Format

Organization Access Tokens follow the format:

  • Prefix: oat_ (Organization Access Token)
  • Key: 43 URL-safe random characters

Example: oat_a1b2c3d4e5f6g7h8i9j0k1l2m3n4o5p6q7r8s9t0u1v

Managing Tokens

From the API Tokens settings page, you can:

Action Description
Create Generate a new token with an optional label
View See token prefix, label, creation date, and last used timestamp
Revoke Disable a token (soft-delete, keeps history)
Delete Permanently remove a token

Security Best Practices

Error Responses

Status Code Description
401 Unauthorized Missing, invalid, or revoked API token
403 Forbidden Token valid but lacks permission for the requested resource

Content Types

The SeggWat API always accepts JSON in request bodies and returns JSON in response bodies. Always include the Content-Type: application/json header in requests.

Navigation