How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Super.ai profile API

User profile operations for viewing and updating account information.Profile endpoints allow authenticated users to view and update their own account information and preferences. These endpoints operate on the currently authenticated user (determined from the JWT token) and do not require specifying a user ID.**Account information includes:**- **Personal Details**: First name, last name, email- **Organization**: Associated organization and role- **Status**: Account status and permissions- **Metadata**: Created/updated timestamps**Use these endpoints to:**- Retrieve current user information for display- Update personal details (name, preferences)- View organization membership and role- Access account metadataProfile endpoints provide self-service account management capabilities, reducing the need for administrative intervention for routine updates.**Note:** All profile endpoints are protected and automatically scope to the authenticated user. Email and organization changes require admin privileges.

Super.ai profile API is one of 19 APIs that Super.ai publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Profile. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

This API exposes 2 operations across 1 path, and defines 13 schemas. It is described by OpenAPI 3.2.0, at version 0.1.0.

Requests are made against a single base URL, https://flows.super.ai/api.

2 operations 1 paths 13 schemas 1 GET1 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1.0
Base URL
https://flows.super.ai/api
Authentication
HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 2

Super.ai profile API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerAuth). An API key is passed in the header as X-API-Key (APIKeyAuth).

  • BearerAuth — JWT Bearer token authentication. Include your access token in the Authorization header as: Bearer YOURACCESSTOKEN Example: Authorization: Bearer eyJhbGciOiJIUz…
  • APIKeyAuth — API key authentication. Include your API key in the X-API-Key header as: X-API-Key YOURAPIKEY Example: X-API-Key: saf1234567890

Paths & Operations 2

Across 1 path, the API surfaces 2 operations — 1 GET, 1 PATCH. Each is listed below with its method, path, parameters, and response codes.

profile 2

User profile operations for viewing and updating account information. Profile endpoints allow authenticated users to view and update their own account information and preferences.…

GET
/api/profile/me
Get current user profile
get_current_user_api_profile_me_get → 200404401500
PATCH
/api/profile/me
Update current user profile
update_current_user_api_profile_me_patch body → 200404401422500

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are UserProfileResponse (15 properties), User (13 properties), UserSettings (7 properties), UserSettingsUpdateRequest (7 properties). Each schema is shown below with its type and property counts.

UserProfileResponse
object
User profile response with organization name included.
15 properties 12 required
HubTagFilter
object
2 properties
UserSettings
object
7 properties
LandingPageConfig
object
Landing page configuration for workers. This model encapsulates the landing page redirect behavior including the configuration type and optional target flow ID.
2 properties
UserStatus
string
UserSettingsUpdateRequest
object
7 properties
WorkerLandingPageConfig
string
Configuration for worker landing page redirect.
HubViewPreference
string
UserRole
string
User
object
User model
13 properties 4 required
UserUpdateRequest
object
Request model for updating the authenticated user's profile information. All fields are optional. Only provided fields will be updated, allowing partial update…
4 properties
ErrorResponse
object
Standard API error response structure. All error responses from the API follow this format, ensuring consistent error handling for API consumers. Example: { "e…
2 properties 1 required
ErrorDetail
object
Standard error detail structure. This model matches the error format returned by the centralized exception handlers in app/api/errors/handlers.py.
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

superai-profile-api-openapi.yml Raw ↑

Other APIs Super.ai publishes across the network.

Super.ai auth API
Super.ai files API
Super.ai flow-executions API
Super.ai flows API
Super.ai human-review-tasks API
Super.ai integrations API
Super.ai models API
Super.ai organizations API
Super.ai plugins API
Super.ai service-accounts API
Super.ai sso API
Super.ai task-data API
Where this information came from

This is an independent, third-party profile of Super.ai profile API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.