Get Effective Profile Route
Resolve and return the merged profile for a project across every applicable layer — hosted_default -> workspace -> user -> project -> session. Mirrors the get_effective_profile MCP tool. This is the one project-anchored route in this module — see the module docstring.
RT-TI-005 (wave 2) — project_id is vetted by the middleware, but session_id merges that session's layer into the result and db.get_effective_profile never checks the session belongs to the project. A project-scoped caller therefore gets a 403 for a session of any other project (or an unknown one); unscoped callers are unchanged.
get/projects/{project_id}/effective-profile
Request
- Base URL: https://usemeridian.us (the document declares no server; this is the origin it was published from)
- URL: https://usemeridian.us/projects/{project_id}/effective-profile
- Auth: none declared
Path parameters
project_idstring required
Query parameters
session_idstring nullable
user_scope_idstring nullable
workspace_scope_idstring
hosted_default_scope_idstring
Response
Successful Response
object required
Changes
No recorded changes to this operation across all 1 revision of this API.