Current source preview reference
POST /v1/auth/ide/browser-invitations
Create ide browser invitation. Permissions, parameters, responses and examples.
Read pinned handler: apps/api/kodesec_api/auth.py:2736
Create ide browser invitation
Create ide browser invitation through POST /v1/auth/ide/browser-invitations. The parameters and declared response shapes below come from this exact source snapshot.
Source preview; no stable third-party integration promise. This page makes no request to a local installation.
Authority
Exact active IDE capability with browser:invite. Handler requires IDE authority; a browser session alone is insufficient.
Parameters and headers
No explicit path, query or header parameters are declared here. The authority boundary still applies.
Request body
JSON body · required · IdeBrowserInvitationRequest
| Field | Type | Presence |
|---|---|---|
purpose | string | Required |
Complete declared request schema
{
"additionalProperties": false,
"properties": {
"purpose": {
"enum": [
"integrated_dashboard",
"extra_browser"
],
"title": "Purpose",
"type": "string"
}
},
"required": [
"purpose"
],
"title": "IdeBrowserInvitationRequest",
"type": "object"
}Responses
| Status | Meaning and declared shape |
|---|---|
200 | Successful Response application/json · IdeBrowserInvitationResponse |
400 | Exact host, malformed request or URL credential refusal application/json · object |
401 | Missing or invalid membership application/json · object |
403 | Exact origin, CSRF or route authority refusal application/json · object |
422 | Validation Error application/json · HTTPValidationError |
429 | Authentication rate or connection limit application/json · object |
An empty or broad schema preserves the source contract. It is not a promise of an empty response.
Source-linked errors
Literal HTTP errors in this handler and same-file helper call graph, plus control middleware. Dynamic and cross-module failures may add other errors; source links are authoritative.
2 source error observations
Synthetic examples
These examples validate declared JSON shapes and formats. They contain no real installation data and do not prove runtime admission, cross-field validation, authority or successful work.
Request JSON
{
"purpose": "integrated_dashboard"
}Response 200 JSON
{
"bootstrap_token": "kbi1.AAAAAAAAAAAAAAAAAAAAAAAA.AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA",
"expires_at": "2026-01-01T00:00:00Z",
"invitation_id": "AAAAAAAAAAAAAAAAAAAAAAAA",
"issued_at": "2026-01-01T00:00:00Z",
"purpose": "integrated_dashboard"
}All referenced models remain in its components section. Browse control model definitions.