Example of Current Implementation

Oct 13, 2025 by ludoplayers7.com 96 views

Introduction

Seeding users and organizations is a crucial step in testing and development processes. However, the current process of using backend APIs to create local server test accounts and organizations can be cumbersome and time-consuming. In this article, we will explore a better way to seed users and organizations using the Better-Auth API.

The Current Problem

Currently, there is no easy way to seed users or organizations using the Better-Auth API. This forces developers to use the backend APIs to create local server test accounts and organizations. However, these APIs can be difficult to use and require a lot of manual work.

Example of Current Implementation

The current implementation of seeding users and organizations using the backend APIs is shown below:

const response = await auth.api.signUpEmail({
  asResponse: true,
  body: {
    email,
    name,
    password,
  },
  headers: new Headers({}),
});

const body = await response.text();
const data: { user: { id: string } } = JSON.parse(body);
const headers = new Headers();
const header = response.headers.get('set-cookie');
const cookies = parseSetCookieHeader(header || '');
const signedCookie = cookies.get('better-auth.session_token')?.value;
headers.set('cookie', `better-auth.session_token=${signedCookie}`);

const userId = data.user.id;
const user = await updateUser(userId, 'fr', role);

const orgId = await auth.api
  .createOrganization({
    headers,
    body: {
      name: `${name}-org`,
      slug: `${name}-org`,
      userId: user.id,
    },
  })
  .then((i) => i?.id);

The Solution

We would like to have a way to seed users and organizations without having to mess with cookies and headers like we are doing right now. This would make the process of testing and development much easier and faster.

Alternatives Considered

None.

Additional Context

No additional context is provided.

Why is this Suited for GitHub?

This is suited for GitHub because it is a platform that allows developers to collaborate and share code. The Better-Auth API is a GitHub API, and seeding users and organizations is a crucial step in testing and development processes.

Benefits of the Solution

The benefits of the solution are:

Easier and faster testing and development process
Reduced manual work and errors
Improved collaboration and sharing of code

Implementation

The implementation of the solution would involve creating a new API endpoint that allows developers to seed users and organizations without having to mess with cookies and headers. This would involve the following steps:

Create a new API endpoint that allows developers to seed users and organizations.
Implement the logic to create users and organizations without having to mess with cookies and headers.
Test the API endpoint to ensure that it is working correctly.

Example of New API Endpoint

The new API endpoint to seed users and organizations could be implemented as follows:

const seedUser = async (req, res) => {
  const { email, name, password } = req.body;
  const user = await createUser(email, name, password);
  res.json(user);
};

const seedOrganization = async (req, res) => {
  const { name, slug, userId } = req.body;
  const organization = await createOrganization(name, slug, userId);
  res.json(organization);
};

Conclusion

In conclusion, seeding users and organizations is a crucial step in testing and development processes. However, the current process of using backend APIs to create local server test accounts and organizations can be cumbersome and time-consuming. We propose a new API endpoint that allows developers to seed users and organizations without having to mess with cookies and headers. This would make the process of testing and development much easier and faster.

Future Work

Future work could involve implementing the new API endpoint and testing it to ensure that it is working correctly. Additionally, we could consider adding more features to the API endpoint, such as the ability to seed multiple users and organizations at once.

References

Code Snippets

Current Implementation
New API Endpoint

API Endpoints

Seed User
Seed Organization

Current Implementation

const response = await auth.api.signUpEmail({
  asResponse: true,
  body: {
    email,
    name,
    password,
  },
  headers: new Headers({}),
});

const body = await response.text();
const data: { user: { id: string } } = JSON.parse(body);
const headers = new Headers();
const header = response.headers.get('set-cookie');
const cookies = parseSetCookieHeader(header || '');
const signedCookie = cookies.get('better-auth.session_token')?.value;
headers.set('cookie', `better-auth.session_token=${signedCookie}`);

const userId = data.user.id;
const user = await updateUser(userId, 'fr', role);

const orgId = await auth.api
  .createOrganization({
    headers,
    body: {
      name: `${name}-org`,
      slug: `${name}-org`,
      userId: user.id,
    },
  })
  .then((i) => i?.id);

New API Endpoint

const seedUser = async (req, res) => {
  const { email, name, password } = req.body;
  const user = await createUser(email, name, password);
  res.json(user);
};

const seedOrganization = async (req, res) => {
  const { name, slug, userId } = req.body;
  const organization = await createOrganization(name, slug, userId);
  res.json(organization);
};

Seed User

Endpoint: /users
Method: POST
Request Body: email, name, password
Response: user

Seed Organization

Endpoint: /organizations
Method: POST
Request Body: name, slug, userId
Response: organization
Frequently Asked Questions (FAQs) =====================================

Q: What is the current process of seeding users and organizations?

A: The current process of seeding users and organizations involves using the backend APIs to create local server test accounts and organizations. This can be cumbersome and time-consuming, and requires a lot of manual work.

Q: What is the proposed solution to seeding users and organizations?

A: The proposed solution is to create a new API endpoint that allows developers to seed users and organizations without having to mess with cookies and headers. This would make the process of testing and development much easier and faster.

Q: How would the new API endpoint work?

A: The new API endpoint would allow developers to seed users and organizations by sending a request to the API with the necessary information. The API would then create the user or organization and return the relevant data.

Q: What are the benefits of the proposed solution?

A: The benefits of the proposed solution are:

Easier and faster testing and development process
Reduced manual work and errors
Improved collaboration and sharing of code

Q: How would the new API endpoint be implemented?

A: The new API endpoint would be implemented by creating a new API endpoint that allows developers to seed users and organizations. This would involve writing the necessary code to create the user or organization and return the relevant data.

Q: What are the potential challenges of implementing the new API endpoint?

A: The potential challenges of implementing the new API endpoint are:

Ensuring that the API endpoint is secure and follows best practices for API design
Ensuring that the API endpoint is compatible with different programming languages and frameworks
Ensuring that the API endpoint is well-documented and easy to use

Q: How would the new API endpoint be tested?

A: The new API endpoint would be tested by sending requests to the API with different scenarios and verifying that the API returns the correct data. This would involve writing test cases and using a testing framework to ensure that the API is working correctly.

Q: What are the potential benefits of implementing the new API endpoint?

A: The potential benefits of implementing the new API endpoint are:

Improved testing and development process
Reduced manual work and errors
Improved collaboration and sharing of code

Q: How would the new API endpoint be maintained and updated?

A: The new API endpoint would be maintained and updated by following best practices for API maintenance and updating. This would involve regularly reviewing the API endpoint and making updates as necessary to ensure that it remains secure and functional.

Q: What are the potential risks of implementing the new API endpoint?

A: The potential risks of implementing the new API endpoint are:

Security risks if the API endpoint is not properly secured
Compatibility risks if the API endpoint is not compatible with different programming languages and frameworks
Maintenance risks if the API endpoint is not properly maintained and updated

Q: How would the new API endpoint be documented?

A: The new API endpoint would be documented by following best practices for API documentation. This would involve writing clear and concise documentation that explains how to use the API endpoint and what data it returns.

Q: What are the potential benefits of documenting the new API endpoint?

A: The potential benefits of documenting the new API endpoint are:

Improved understanding of how to use the API endpoint
Reduced errors and issues due to unclear documentation
Improved collaboration and sharing of code

Q: How would the new API endpoint be versioned?

A: The new API endpoint would be versioned by following best practices for API versioning. This would involve using a versioning scheme that allows for easy tracking and updating of the API endpoint.

Q: What are the potential benefits of versioning the new API endpoint?

A: The potential benefits of versioning the new API endpoint are:

Improved tracking and updating of the API endpoint
Reduced errors and issues due to unclear versioning
Improved collaboration and sharing of code

Q: How would the new API endpoint be deployed?

A: The new API endpoint would be deployed by following best practices for API deployment. This would involve using a deployment strategy that ensures the API endpoint is secure and functional.

Q: What are the potential benefits of deploying the new API endpoint?

A: The potential benefits of deploying the new API endpoint are:

Improved security and functionality of the API endpoint
Reduced errors and issues due to unclear deployment
Improved collaboration and sharing of code

Q: How would the new API endpoint be monitored and maintained?

A: The new API endpoint would be monitored and maintained by following best practices for API monitoring and maintenance. This would involve regularly reviewing the API endpoint and making updates as necessary to ensure that it remains secure and functional.

Q: What are the potential benefits of monitoring and maintaining the new API endpoint?

A: The potential benefits of monitoring and maintaining the new API endpoint are:

Improved security and functionality of the API endpoint
Reduced errors and issues due to unclear monitoring and maintenance
Improved collaboration and sharing of code