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

Charthop scenario API

The scenario API from Charthop — 13 operation(s) for scenario.

Charthop scenario API is one of 87 APIs that Charthop publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 16 operations across 13 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version V1.0.0.

Requests are made against 2 base URLs: https://localhost, http://localhost.

16 operations 13 paths 19 schemas 1 DELETE3 GET1 PATCH11 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
V1.0.0
Base URL
https://api.charthop.com
Contact
Resource Areas
1

Paths & Operations 16

Across 13 paths, the API surfaces 16 operations — 1 DELETE, 3 GET, 1 PATCH, 11 POST. Each is listed below with its method, path, parameters, and response codes.

scenario 16
GET
/v1/org/{orgId}/scenario
Return all scenarios in the organization paginated
findScenarios 5 params → 200400401404
POST
/v1/org/{orgId}/scenario
Create a scenario
createScenario 3 params body → 201400401403404
POST
/v1/org/{orgId}/scenario/bulk/archive
Archive a set of scenarios
bulkArchiveScenarios 1 param body → 200400401403404
POST
/v1/org/{orgId}/scenario/bulk/delete
Delete a set of scenarios
bulkDeleteScenarios 1 param body → 200400401403404
POST
/v1/org/{orgId}/scenario/bulk/unarchive
Unarchive a set of scenarios
bulkUnarchiveScenarios 1 param body → 200400401403404
GET
/v1/org/{orgId}/scenario/{scenarioId}
Return a particular scenario by id
getScenario 2 params → 200400404
PATCH
/v1/org/{orgId}/scenario/{scenarioId}
Update an existing scenario
updateScenario 3 params body → 204400401403404
DELETE
/v1/org/{orgId}/scenario/{scenarioId}
Delete a scenario
deleteScenario 2 params → 204400401403404
GET
/v1/org/{orgId}/scenario/{scenarioId}/audit-log
Return past audit log events for a scenario, paginated
getScenarioAuditLog 5 params → 200400401404
POST
/v1/org/{orgId}/scenario/{scenarioId}/combine
Combine multiple scenarios into another scenario
combineScenarios 2 params body → 200400401403404
POST
/v1/org/{orgId}/scenario/{scenarioId}/dates
Adjust the dates of the changes in a scenario
adjustDatesScenario 2 params body → 200400401403404
POST
/v1/org/{orgId}/scenario/{scenarioId}/export/audit
Export a scenario's audit log
exportScenarioAuditLog 2 params body → 201400403404
POST
/v1/org/{orgId}/scenario/{scenarioId}/merge
Merge a scenario into the primary timeline
mergeScenario 3 params → 200400401403404
POST
/v1/org/{orgId}/scenario/{scenarioId}/recalculate-metadata
Manually recalculate a scenario's metadata
recalculateScenarioMetadata 2 params → 200400401404
POST
/v1/org/{orgId}/scenario/{scenarioId}/update-shared-view
Update a scenario view config
updateScenarioSharedView 2 params body → 400401403404
POST
/v1/org/{orgId}/scenario/{scenarioId}/update-shared-views
Upsert multiple scenario view configs in a single atomic request
updateScenarioSharedViews 2 params body → 400401403404

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are Scenario (37 properties), Process (29 properties), Event (22 properties), CreateScenario (13 properties). Each schema is shown below with its type and property counts.

UpdateScenario
object
11 properties
CreateScenario
object
13 properties 2 required
Money
object
3 properties 2 required
ScenarioBudgetImpact
object
6 properties 5 required
ShareAccess
object
4 properties 1 required
ResultsScenario
object
3 properties 1 required
ResultsAccess
object
2 properties 1 required
AccessAction
object
3 properties 1 required
Process
object
29 properties 9 required
ScenarioMetadata
object
9 properties 4 required
Attribution
object
6 properties
ResultsEvent
object
3 properties 1 required
Event
object
22 properties 6 required
CostImpact
object
3 properties 3 required
Scenario
object
37 properties 11 required
ScenarioSharedViewConfig
object
5 properties
CombineScenarioRequest
object
3 properties 1 required
AdjustScenarioDateRequest
object
2 properties
LogData
object
4 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

charthop-scenario-api-openapi.yml Raw ↑

Other APIs Charthop publishes across the network.

Charthop access API
Charthop action API
Charthop ai API
Charthop ai-credit-limit API
Charthop ai-hint API
Charthop ai-prompt API
Charthop app API
Charthop appConfig API
Charthop approval API
Charthop approval-delegate API
Charthop approval-request API
Charthop assessment API
Where this information came from

This is an independent, third-party profile of Charthop scenario 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.