CRM developer access
Canonical commercial records, intake review, pipeline workflows, search, tasks, and explainable attention queues.
- Owner
- Vision CRM
- Lifecycle
- preview
- Runtime
- restricted
- App entitlement
- crm
- Audience
- Active Vision CRM App profile
- Workspace
- CRM workspace required
Authority boundary
CRM owns its records, workflow rules, workspace membership, provenance, and record-level authorization.
Complete preview contract: Every operation and MCP capability in the approved definitions below is documented. The lifecycle and runtime labels describe stability and availability, not partial catalog coverage.
CRM API
- Owning App
- CRM
- Contract version
- 9.12.1
- Audience
- Active Vision CRM App profile
- Workspace binding
- CRM workspace required
Download the authoritative OpenAPI 3.1 definition
51 operations
Generated from Vision CRM Authenticated API 9.12.1
- GET/api/health
Process liveness
No bearer scope declaredFull operation reference → - GET/api/ready
Authenticated API database readiness
No bearer scope declaredFull operation reference → Contract and version metadata
No bearer scope declaredFull operation reference →Explainable CRM attention queue
Full operation reference →crm:today:readPaginated quarantined intake queue
Full operation reference →crm:intake:readSubmit a lead from a website form
Full operation reference →crm:intake:createQuarantined intake detail and provenance
Full operation reference →crm:intake:readBrowse canonical people
Full operation reference →crm:people:readRead a canonical person briefing
Full operation reference →crm:people:readBrowse canonical organizations
Full operation reference →crm:organizations:readRead a canonical organization briefing
Full operation reference →crm:organizations:readBrowse the authoritative commercial pipeline
Full operation reference →crm:opportunities:readRead authoritative opportunity detail
Full operation reference →crm:opportunities:readBrowse assigned CRM work
Full operation reference →crm:tasks:readRead one CRM task (panel record)
Full operation reference →crm:tasks:readSearch authorized canonical CRM records
Full operation reference →crm:search:readApply a controlled human CRM record command
Full operation reference →crm:opportunities:writecrm:organizations:writecrm:people:writecrm:tasks:writeApply an authorized, idempotent intake-review command
Full operation reference →crm:intake:reviewChronological activity timeline for a person
Full operation reference →crm:people:readPipeline funnel: occupancy, flow and dwell per stage
Full operation reference →crm:opportunities:readCRM Overview's cards: new leads, follow-ups due, replies waiting, won this month, open deals, deals by stage
Full operation reference →crm:today:readActors who can own work here, with current workload
Full operation reference →crm:today:readCRM's navigation, views and actions, filtered to this caller
Full operation reference →crm:today:readCRM's scheduling configuration: who it offers for booking
Full operation reference →crm:settings:readRead one service line (panel record)
Full operation reference →crm:settings:readRead one meeting length (panel record)
Full operation reference →crm:settings:readCRM's pipeline configuration: pipelines and the default pipeline's stages
Full operation reference →crm:pipeline:readChronological activity timeline for an opportunity
Full operation reference →crm:opportunities:readChronological activity timeline for an organization
Full operation reference →crm:organizations:readMark one of the caller's own My day inbox items done, or move it back to the inbox
Full operation reference →crm:today:readToday feed: replies owed, next steps, and follow-ups
Full operation reference →crm:today:readToday feed: CRM widgets
Full operation reference →crm:today:readPipeline overview: one row per pipeline with stage counts, open value and next step
Full operation reference →crm:opportunities:readCRM's access settings: who sees leads and deals, where new leads go, and each person's CRM switch
Full operation reference →crm:settings:readWhere imported rows can land, and the recent imports
Full operation reference →crm:people:writeStart a new import from one file: its name, row count and column matching
Full operation reference →crm:people:writeThe import's check, progress and result
Full operation reference →crm:people:writeRows not imported (before it runs: rows with problems), in file order, 500 at a time
Full operation reference →crm:people:writeCheck one chunk of up to 500 mapped rows and keep them until the import starts
Full operation reference →crm:people:writeRun the import as a job: contacts or leads, a stage for leads, and what to do with rows matching a contact
Full operation reference →crm:people:writeUndo the whole import: remove what it created and restore what it changed
Full operation reference →crm:people:writeTo-Do feed: the caller's open follow-ups and next steps
Full operation reference →crm:tasks:readFinish a follow-up or next step
Full operation reference →crm:tasks:writeCompanies and contacts together, for another app finding a client.
Full operation reference →crm:organizations:readOne company or contact as another app may bill or link it.
Full operation reference →crm:organizations:readOne deal as another app may invoice it.
Full operation reference →crm:opportunities:readPossible matches: CRM records that may be the same as another record, for a person to look at
Full operation reference →crm:settings:manageDecide a possible match: same, different, or undo
Full operation reference →crm:settings:manageDeals won lately, newest first, for an app that bills them.
Full operation reference →crm:opportunities:readThe caller's dated open work, for a date grid.
Full operation reference →crm:tasks:readColleagues' dated follow-ups, for a date grid, as each of them shares them.
Full operation reference →crm:tasks:read
Publication evidence
This page is generated from the approval registry. Contract checksums, source drift, security declarations, scopes, references, and operation identifiers are verified before publication. A production documentation deployment remains a separate approval and rollback gate.