Create projects and API keys via API

[maxxte]

Describe the feature you'd like to request

While automatically setting different environments we would like to add observability in automatic way, this means to create project in langfuse and get secret and public keys, to pass them later to application

Describe the solution you'd like to see

Introduce new Projects endpoint POST with parameters (project name) to create new project
And endpoint for creating API keys, which will consume project name/id and respond with secret and public keys.

Additional information

No response

Contribute

• Yes, I can implement this and raise a PR

[marcklingen]

Thanks for raising this, I understand the need. Do you suggest to introduce user-level api keys that can be used to create projects and project-level api keys?

[marcklingen]

@maxxte

[maxxte]

@marcklingen, yes, I see this as the only way to control the possibility of creating projects, thank you and sorry for longer response

[marcklingen]

Thanks for the clarification! Does a default project/user solve the problem for you or do you need to create multiple projects while and api keys while the container is already running? @maxxte

[Harryalways317]

Default project should be fine

[mprudra]

This looks promising.
I want to run a central instance of Langfuse, and different devs can have multiple projects. Currently each user has to create a project, get api keys, set envs, pass callbacks. I want to make this as minimal as possible, we already have a concept of project internally to track LLM usage, may be we can use that to create corresponding Langfuse project for users, set envs and pass callback (we'll see about this, I've some way for this as well, not yet documented by Langchain, @marcklingen we had discussed this earlier in chat, by using Langchain Tracer).

[mprudra]

Adding to this, it's best to support create, delete and manage (manage authorization, etc.) APIs.

[Laurian]

Additionally to creating projects/keys, which I guess will be authorized via let's say MASTER_API_KEY, it would be great to be able to have a default admin user, think of having NEXT_PUBLIC_SIGN_UP_DISABLED=false and allowing sign in with admin and the MASTER_API_KEY as password.

[hburrichter]

Adding to this conversation, how about a master API key that can be used for all Langfuse projects? This may already solve the issue of not being able to create projects/keys via an API, for some users, including us.

Currently, we need to manually create each Langfuse project, generate the associated API key, copy them to our secret management tool and have extra business logic in our infrastructure and deployment scripts, that assigns the correct Langchain key to each containerized application.

All this would be instantly solved if we could use one master API key.