Skip to main content
POST
Add Selected Skill
Send a user ID and a skill ID, and this creates a record tying them together. That’s it. One rule: a user can’t select the same skill twice. Try it and you’ll get a 409. This is enforced at both the application level and in the database with a compound unique index, so even concurrent requests won’t create duplicates. No authentication needed.

Request Body

string
required
The user who’s selecting the skill.
string
required
The skill being selected.
string
required
The sub-skill category this skill belongs to. You can get this from the search endpoint.
string
required
The master skill category. Also available from search results.

Response

boolean
true when the record is created
string
A short confirmation message
object
The newly created record. Hold onto the selected_skill_id — you’ll need it if you want to delete this later.

Examples


Why does the 409 check happen twice?The route checks for an existing { user_id, skill_id } record before trying to insert. But just in case two requests land at exactly the same time, the database also has a compound unique index on those fields. The app-level check gives you the nicer error message. The DB-level index is the safety net.