docs: document /api/artist/create endpoint

[sweetmantech]

Summary

• Documents the /api/artist/create API endpoint in OpenAPI spec
• Adds endpoint documentation for creating new artist accounts

Test plan

• Verify OpenAPI spec is valid
• Check Mintlify generates API reference page correctly

🤖 Generated with Claude Code

Summary by CodeRabbit

• New Features

  • Added POST /api/artists endpoint to create artist profiles, returning full profile data including onboarding, account metadata, socials, and optional organization linkage.

• Documentation

  • New API reference page for the Create Artist endpoint and navigation updated to include the new Artists create doc.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Warning

Rate limit exceeded

@sweetmantech has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 20 minutes and 51 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 40e495f and 9dc4f2a.

📒 Files selected for processing (1)

• api-reference/openapi.json

📝 Walkthrough

Walkthrough

Added a new OpenAPI endpoint POST /api/artists to create artists (optionally linked to an account or organization), plus public schemas for request, response, created-artist payload, and error; documentation page and navigation entry were added.

Changes

Cohort / File(s)	Summary
OpenAPI spec api-reference/openapi.json	Added POST /api/artists operation with request schema CreateArtistRequest and responses: 201 -> CreateArtistResponse (contains CreatedArtist), 400 validation error, 500 server error. Introduced schemas: CreateArtistRequest, CreateArtistResponse, CreatedArtist, CreateArtistError.
API docs page api-reference/artists/create.mdx	New documentation page for "Create Artist" describing POST /api/artists (YAML front matter added).
Navigation / site config docs.json	Added the new artists create page to the API Reference navigation (expanded Artists group) and removed a duplicated Chat group block.

Sequence Diagram(s)

sequenceDiagram
  participant Client
  participant API as API Server
  participant DB as Database

  Client->>API: POST /api/artists (CreateArtistRequest)
  API->>DB: INSERT artist record (with account_id / organization_id)
  DB-->>API: OK + created artist row (id, timestamps, metadata)
  API-->>Client: 201 Created (CreateArtistResponse with CreatedArtist)

Loading

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I hopped a path where artists grow,

POSTing dreams where names can go.
IDs and timestamps in a row,
A little hop — the API says "go!" 🎨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The PR title references '/api/artist/create' (singular), but the actual endpoint implemented is '/api/artists' (plural) with POST method, creating a mismatch with the documentation.	Update the PR title to accurately reflect the actual endpoint: 'docs: document POST /api/artists endpoint' or similar.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@api-reference/openapi.json`:
- Around line 323-370: The OpenAPI POST /api/artist description mentions
optional organization linkage but the CreateArtistRequest schema lacks an
organization_id field; either add an optional organization_id property to the
CreateArtistRequest schema so the request supports linking an artist to an
organization, or edit the /api/artist operation description to remove/clarify
the organization linkage and instead document the correct flow (e.g., that
organization linking is done via a separate endpoint such as
/api/organizations/artists); update CreateArtistRequest (symbol:
CreateArtistRequest) or the /api/artist operation description accordingly so the
contract and description are consistent.

🧹 Nitpick comments (3)

api-reference/openapi.json (3)

2965-2972: Array schemas missing items definition.

The account_info and account_socials array properties lack items definitions, which will cause issues with OpenAPI client generators and schema validators. Consider adding the item schema or referencing an existing schema.

📝 Suggested fix

          "account_info": {
            "type": "array",
+           "items": {
+             "type": "object"
+           },
            "description": "Account info records"
          },
          "account_socials": {
            "type": "array",
+           "items": {
+             "type": "object"
+           },
            "description": "Linked social media accounts"
          }

If these have a known structure, define proper schemas (e.g., reference existing ArtistSocial for account_socials).

---

2961-2964: Missing type for onboarding_data property.

The onboarding_data field lacks a type specification. For better client code generation and documentation clarity, consider specifying the expected type (e.g., object with additionalProperties: true for arbitrary JSON data).

📝 Suggested fix

          "onboarding_data": {
+           "type": "object",
+           "additionalProperties": true,
            "nullable": true,
            "description": "Onboarding data"
          },

---

2975-2999: Consider adding required array to error schema for consistency.

The CreateArtistError schema doesn't specify required fields, unlike other error schemas in this spec (e.g., ArtistsErrorResponse requires ["status", "message"]). Adding a required array improves client-side error handling predictability.

📝 Suggested fix

      "CreateArtistError": {
        "type": "object",
+       "required": ["status"],
        "properties": {
          "status": {

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 7aa3c06 and c236135.

📒 Files selected for processing (1)

• api-reference/openapi.json

🔇 Additional comments (2)

api-reference/openapi.json (2)

2859-2874: LGTM!

The CreateArtistRequest schema is well-defined with appropriate validation constraints (minLength: 1 for name, format: uuid for account_id) and clear descriptions.

---

2875-2883: LGTM!

The response schema follows the established pattern of wrapping the created entity in a named property.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}