How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Visier Plan Administration API

Manage collaboration projects in your plans, including actions such as consolidating and reopening subplans.

Visier Plan Administration API is one of 51 APIs that Visier publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Plan Administration. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 2 operations across 2 paths, and defines 26 schemas. It is described by OpenAPI 3.2.0, at version 22222222.99201.3040.

Requests are made against the base URL https://{vanity_name}.api.visier.io.

2 operations 2 paths 26 schemas 2 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
22222222.99201.3040
Base URL
https://{vanity_name}.api.visier.io
Authentication
API Key, API Key, HTTP Bearer, OAuth 2.0
Resource Areas
1

Authentication & Security 4

Visier Plan Administration API declares 4 security schemes for authenticating requests. An API key is passed in the cookie as VisierASIDToken (CookieAuth). An API key is passed in the header as apikey (ApiKeyAuth). It accepts HTTP bearer tokens (BearerAuth). It supports OAuth 2.0 (OAuth2Auth) using the authorizationCode and password flows, exposing 2 scopes. By default, every request must be authenticated.

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 2 PATCH. Each is listed below with its method, path, parameters, and response codes.

PlanAdministration 2

Manage collaboration projects in your plans, including actions such as consolidating and reopening subplans.

PATCH
/v1/planning/data/plans/{planId}
Partially update a plan
PlanAdministration_PlanAction 1 param body → 200400403404500
PATCH
/v1/planning/data/plans/{planId}/scenarios/{scenarioId}
Partially update a plan scenario
PlanAdministration_PatchPlan 2 params body → 200500400404

Schemas 26

The contract defines 26 schemas that model the data the API accepts and returns. The most detailed are planning.PlanScenarioPatchRequest (7 properties), Status (5 properties), planning.PlanPatchActionResult (4 properties), planning.AssignSubplanActionPayload (4 properties). Each schema is shown below with its type and property counts.

planning.PlanUserShareEntry
object
2 properties
planning.ErrorSummary
object
The error details of the unsuccessful action.
2 properties
planning.SubmitActionPayload
object
The details of submitting a subplan.
1 property
PlanPatchReopenActionRequest
object
2 properties 2 required
planning.StartCollaborationActionPayload
object
The details of starting a collaboration project.
2 properties
PlanPatchAssignSubplanActionRequest
object
2 properties 2 required
planning.EndCollaborationActionPayload
object
The details of ending a collaboration project.
1 property
planning.ShareActionResult
object
Per-user outcome detail for a Share action.
1 property
planning.ConsolidateActionPayload
object
The details of consolidating a subplan.
2 properties
planning.PlanPatchRequest
object
A plan-level action request. Parallel to PlanScenarioPatchRequest but operates on a plan (no scenario). Designed to host further plan-level actions over time.…
1 property
planning.PlanPatchResponse
object
Response envelope for the plan-level action route.
1 property
planning.PlanScenarioPatchActionResult
object
The result of the action taken on the main plan or subplan.
3 properties
planning.FailedShareEntry
object
2 properties
planning.ShareActionPayload
object
The desired sharing state for a plan. shares is the complete set of individual user shares (full-replace): users not listed lose their individual access.
3 properties
planning.PlanScenarioPatchResponse
object
The result of the action taken on the subplan if reopening, or the main plan if consolidating.
1 property
PlanPatchStartCollaborationActionRequest
object
2 properties 2 required
planning.DimensionMember
object
A dimension member that identifies a position along one dimension in a plan's segmentation.
2 properties 2 required
Status
object
The response structure for errors.
5 properties
planning.ReopenActionPayload
object
The details of reopening a subplan.
2 properties
planning.PlanPatchActionResult
object
4 properties
PlanPatchConsolidateActionRequest
object
2 properties 2 required
planning.AssignSubplanActionPayload
object
The details of creating a subplan identified by dimension members.
4 properties 3 required
PlanPatchEndCollaborationActionRequest
object
2 properties 2 required
planning.PlanScenarioPatchRequest
object
If consolidating subplans, starting collaboration, or ending collaboration, this is the main plan to update. Otherwise, this is the subplan to update.
7 properties
PlanPatchSubmitActionRequest
object
2 properties 2 required
planning.AssignSubplansActionPayload
object
The details of creating a list subplans.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

visier-planadministration-api-openapi.yml Raw ↑

Other APIs Visier publishes across the network.

Visier Query MCP Server
Visier Analytic Objects V2 API
Visier Basic Authentication API
Visier Benchmarks API
Visier Concepts V2 API
Visier Consolidated Analytics API
Visier Data And Job Handling API
Visier Data Export Connectors API API
Visier Data Intake API
Visier Data Model API
Visier Data Query API
Visier Data Upload API
Where this information came from

This is an independent, third-party profile of Visier Plan Administration API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.