Request a Solution
const url = 'http://localhost:8000/api/solutions/requests/';const form = new FormData();form.append('message', 'example');form.append('attachments', 'file');
const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
options.body = form;
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url http://localhost:8000/api/solutions/requests/ \ --header 'Authorization: Bearer <token>' \ --header 'Content-Type: multipart/form-data' \ --form message=example \ --form attachments=@fileSubmit a free-text request (plus optional supporting files) for a Solution the catalog doesn’t yet offer. Emailed to the AiKYNETIX team; reply-to is the requesting coach. Multipart (message + attachments[]).
Authorizations
Section titled “Authorizations”Request Bodyrequired
Section titled “Request Bodyrequired”POST /api/solutions/requests/ — a coach’s “Request a Solution”
(a message + optional supporting files). Multipart.
object
What the coach would like a Solution to assess.
Up to 5 supporting files (clip / screenshot / spec sheet).
POST /api/solutions/requests/ — a coach’s “Request a Solution”
(a message + optional supporting files). Multipart.
object
What the coach would like a Solution to assess.
Up to 5 supporting files (clip / screenshot / spec sheet).
Examplegenerated
message=example&attachments=binaryPOST /api/solutions/requests/ — a coach’s “Request a Solution”
(a message + optional supporting files). Multipart.
object
What the coach would like a Solution to assess.
Up to 5 supporting files (clip / screenshot / spec sheet).
Examplegenerated
{ "message": "example", "attachments": [ "binary" ]}Responses
Section titled “Responses”object
Always true on a 202 — the request was queued for the team.
Examplegenerated
{ "submitted": true}object
Human-readable message, or a stable machine code for the cases a client branches on. The standard envelope for 400 (validation — a field-keyed object may appear instead), 401 (missing / invalid credentials), 403 (authenticated but not permitted), and 404 (absent — cross-team records are collapsed to 404 so the API never leaks the existence of another team’s data).
Examplegenerated
{ "detail": "example"}