---
title: "Submit Signup Profile"
method: POST
path: "/api/v1/auth/signup/profile"
tags: ["auth"]
---

# Submit Signup Profile

`POST /api/v1/auth/signup/profile`

Store the caller's questionnaire answers on their own account.

Rate Limited: 10 requests per minute per IP address.

Questionnaire-free clients never call this route. It remains ungated so an
older client already open during the rolling deploy can finish its optional
submission after the public signup toggle changes. The write annotates the
caller's own existing account and creates nothing; MAIA-4460 removes this
compatibility route after the rollout window closes.

## Request body

- SignupProfileRequest — Legacy questionnaire answers accepted during the compatibility window. Values are the chosen option's label, or the free text typed under "Other" — deliberately not a server-side enum. The option lists live in the client beside the form, and a copied list here would refuse exactly the answers "Other" exists to accept. Lengths and the list size are bounded so the surface cannot store arbitrary payloads. MAIA-4460 removes this schema with the retired endpoint and storage field.
  - `use_case` string, nullable
  - `property_types` string[]
  - `role` string, nullable

## Response `204`

Successful Response

## Other responses

- `422` — Validation Error

## Changes

- **2026-08-25** `b61a1454aad6` — 1 info
  - endpoint added

[Change history](https://skmtc.dev/maia-analytics/apis/maia-api/changes/api/v1/auth/signup/profile/post.md)

---

[API](https://skmtc.dev/maia-analytics/apis/maia-api.md) · [All operations](https://skmtc.dev/maia-analytics/apis/maia-api/llms.txt) · [OpenAPI document](https://skmtc.dev/maia-analytics/apis/maia-api/revisions/95495ef535bc?raw)