REST API开发疑问：请求体是否可包含数据库主键？

Hey there! As someone new to REST APIs, it’s totally normal to second-guess these choices—let me break this down for you clearly.

First off: Yes, putting student IDs (your database primary keys) in the POST request body is absolutely acceptable and actually a common, sensible approach for your use case. REST doesn’t have hard rules that forbid this, especially when you’re creating a new resource (the player team) by linking to existing resources (students). The request body is exactly where you should carry this kind of relational data when creating something new.

A few quick tips to make your API even more solid:

• Keep your request body structure clean and explicit. For example, if you’re using JSON, format it like this:

  {
    "team_name": "Hoop Stars",
    "student_ids": [12, 45, 78, 91]
  }
  

  This makes it obvious what the team’s details are and which students are being added, which helps with readability and future maintenance.
• Validate those student IDs! On the backend, always check that each ID corresponds to a real student in your database. You don’t want to create a team with non-existent members.
• Don’t forget permissions: If your system has role-based access, make sure the user making the request has the right to use those student IDs (like a teacher creating a team, vs. a student trying to add others without permission).

One quick note: You might wonder if putting IDs in the URL would be better, but that’s not ideal here. Your POST endpoint should point to the collection of teams (like /api/teams), and cramming a list of student IDs into the URL would make it messy and go against REST’s focus on resource identification. The request body is the right home for this data.

All in all, your approach is totally on the right track—just keep those small best practices in mind, and you’ll have a solid API up and running in no time!

内容的提问来源于stack exchange，提问作者Harish