Django Rest API project architecture/design - What would a good design for my API be?

Question

I'm new to Django and APIs in general and I want to create a Django based API using Django Rest Framework.

The API must have the following:

API with employees CRUD:

 - GET: /employees/ (employee list)
 - POST: /employees/ (employee create)
 - UPDATE /employees/ID/ (employee update)
 - DELETE /employees/ID/ (employee delete)
 - GET /employees/ID/ (employee detail)

API with reports:

 - GET /reports/employees/salary/ (salary report)
 - GET /reports/employees/age/ (age report)

Endpoint to employee list:

curl -H "Content-Type: application/json" localhost:8000/employees/

Endpoint to age range report:

curl -H 'Content-Type: application/json' localhost:8000/reports/employees/age/

Endpoint to salary range report:

curl -H 'Content-Type: application/json' localhost:8000/reports/employees/salary/

It must persist data in a database and use authentication to access.

How do I structure this project in terms of apps, folders, etc?

So far I've figured I'd have something like this:

root
├───backend (folder)
│   │   manage.py
│   │
│   ├───api (app)
│   ├───django_project
│   ├───employees (app)
│   ├───reports (app)
│   └───users (app)
└───client
        my_client.py --> will consume the api

Or maybe something like this?:

root
├───backend (folder)
│   │   manage.py
│   │
│   ├───api (app)
│   ├───applications (folder)
│   │   ├───employees (app)
│   │   ├───reports (app)
│   │   └───users (app)
│   └───django_project
│           settings.py
│
└───client (folder)
        my_client.py

Obs: Just ignore the missing files for now. It's not a real project.

My question is: Is either of these a good design and/or way to structure my project? Why or why not?

Basically, what do I turn into apps? How to best organize my project?

I was reading this but I still have questions.

P.s.: Also, If anyone has any other good source for best practices on Django APIs design, please let me know.

Thank you in advance.