-
Notifications
You must be signed in to change notification settings - Fork 5
Closed
Labels
enhancementNew feature or requestNew feature or request
Description
Is your feature request related to a problem? Please describe
Currently, the credentials API requires both organization_id and project_id to be explicitly passed in requests. However, these values should already be derivable from the API key in the header. This design leads to confusion, especially since the API was initially built around a single superuser with API key access (coming from the default template). As we moved from environment-based keys to database-fetched keys , we transitioned to generating per-project API keys to simplify things. But the credentials endpoint hasn’t been updated accordingly.
Describe the solution you'd like
- The API should automatically infer organization_id and project_id from the API key rather than requiring them as parameters.
- The credentials endpoint should be updated to align with the per-project API key design.
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request
Type
Projects
Status
Closed