> ## Documentation Index > Fetch the complete documentation index at: https://docs.narrative.io/llms.txt > Use this file to discover all available pages before exploring further. # Updates a view > Updates a view ## OpenAPI ````yaml https://docs-cdn.narrative.io/api-reference/main/openapi.json put /v2/views/{view_id} openapi: 3.1.1 info: contact: email: support@narrative.io name: Narrative Support url: https://www.narrative.io termsOfService: https://www.narrative.io/legal/terms-of-service x-logo: url: >- https://cdn.narrative.io/images/company-logos/prod/narrative-logo-text-white.svg backgroundColor: rgb(9, 34, 166) altText: Narrative Logo description: >- The [Narrative Data Collaboration Platform](https://app.narrative.io) API is organized around REST. Our API has predictable resource-oriented URLs, accepts form-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs. The current version is a pre-release beta. It may result in unexpected behavior and there may be breaking changes in future releases up to the 1.0 release. title: Narrative Data Collaboration Platform API version: 2.4.x servers: - url: https://api-dev.narrative.io - url: https://api.narrative.io security: [] tags: - name: Access Rules description: >- Access rules let data providers control who can purchase their data and the terms of purchase. The `access-rules` API allows you to manage access rules for your datasets. Related guides: - [What is an access rule?](https://kb.narrative.io/access-rules) - name: Agent Conversations description: >- Build LLM-driven workflows that can call MCP tools, ask the caller for input, and return structured answers. A conversation pins a model, a system prompt, and a tool catalog. Each run sends the model a user message (or a batch of tool outputs from a previously-paused run); the model decides whether to answer directly, call a server-side tool (resolved by the platform via Model Context Protocol), or call a client-side tool (which pauses the run with `requires_action` and waits for the caller to reply). Related guides: - [Agent Conversations Reference](https://docs.narrative.io/reference/architecture/agent-conversations) - [Error catalog](https://docs.narrative.io/reference/architecture/agent-conversations/errors/conversation-not-found) - name: MCP Connections description: >- Connect external (non-Narrative) MCP servers so agent runs can call their tools with the calling user's own OAuth authorization. A connection is created interactively: `POST /mcp-connections` runs OAuth discovery and Dynamic Client Registration against the server and returns a consent URL; the user authorizes in a browser; the authorization server redirects to `GET /mcp-connections/callback`, which finishes the token exchange and marks the connection `connected`. Tokens are stored encrypted and used server-side — they are never returned by the API. Once connected, reference the connection by id from an agent run's `mcp_servers[].connection_id`. - name: App Invites description: >- App invites allow applications to create one-time, shareable links on behalf of their users. These links enable users to invite third parties who do not have a Narrative account to perform actions within the application. For example, a Narrative user can send an invite link to a third party who then completes a Pinterest OAuth flow and creates a connector profile in the inviter's account, allowing the inviter to deliver audience data to the third party's Pinterest account without the third party needing a Narrative account. This API is intended to be used by applications (via app client credentials) to create and manage invites on behalf of their users, which can then be shared with invitees. - name: Apps description: >- Apps are applications bundled with a UI that can perform various actions on behalf of a user utilizing the Narrative API. Related guides: - [Building a Narrative Native App](https://www.narrative.io/knowledge-base/how-to-guides/building-a-narrative-native-app) - name: Access Tokens description: API Access Token management - name: Attributes description: >- An attribute models a standardized data point available for sale on the Narrative marketplace. Narrative automatically turns data points from provider datasets into attributes so that buyers can purchase well-formed, standardized data from any supplier on the marketplace. - name: Auth description: >- API token is a crucial step for developers to securely authenticate requests to the Narrative API Related guides: - [How to Create an API Token](https://www.narrative.io/knowledge-base/how-to-guides/understanding-narratives-apis/create-an-api-token) - name: Authentication description: User login and registration - name: Billings description: Used by Narrative internally to bill customers - name: Companies description: A collection of employees - name: Company Marketing Information description: Useful information related to companies - name: Compute Pools description: >- Compute pools represent compute resources (e.g. Snowflake warehouses) provisioned within a data plane. Companies can manage and share compute pools, assign them to jobs, and set a default compute pool on data planes. - name: Connections description: Associations between connectors and datasets - name: Data Shops description: |- Self-hosted website to sell your data Related guides: - [Setting up your datashop](https://www.narrative.io/knowledge-base/how-to-guides/shop-builder/settting-up-your-data-shop) - name: Data Streams description: >- The `data-stream` API endpoints allows one to create and update data-streams. Additionally the endpoints allow finding data-streams using free text search. A few of the endpoints are behind authorization. Update endpoint allows a client to post an edited data-stream document as is, without having to change its shape. The API ensures that only certain fields are allowed to be modified. Attempts to modify fields not up for client modifications are ignored. Related guides: - [What is a data stream?](https://kb.narrative.io/what-is-a-data-stream) - name: Contracts description: Contracts related APIs - name: Datasets description: >- Any kind of data, in any schema, can be pushed into the Narrative Data Collaboration Platform as a dataset exactly as it is stored in your own system. The `datasets` API allows you to manage your datasets. - name: Destinations description: >- Destinations associate a subscription to a profile. Optionally, ad-hoc quick settings can be configured to a destination. Those quick settings have to match the format defined on the app manifest. - name: Installations description: Installations of Applications for a profile - name: Jobs description: >- Jobs represent an operation done on a given data plane. All jobs today are tied to a query that represents a forecast or a materialized view. The jobs API provides an interface for interacting with the jobs table, which stores various operations involving reading or writing data. This API allows users to retrieve detailed information about specific jobs, including cost forecasts, data forecasts, NQL forecasts and materialized views. - name: Mappings description: >- A mapping is a transformation from a dataset to an attribute. Defining a mapping between a dataset and an attribute makes the dataset eligible to participate in subscriptions where a buyer is purchasing the target attribute. - name: Model Inference description: Model Inference - name: Models description: >- Machine learning models for training and inference. Models can be stored in HuggingFace or Narrative repositories and have configurable collaborator permissions for training and inference access. The `models` API allows you to list, retrieve, and update models accessible to your company. - name: NQL description: >- Narrative Query Language (NQL) is a specialized, SQL-inspired language designed to query and manipulate data within the Narrative platform. While it looks and feels much like standard SQL, it offers extended functionality and syntax that let you leverage platform-specific features—such as referencing datasets by their IDs, creating materialized views, or generating forecasts—without having to manage the complexities of different query engines behind the scenes. NQL queries can ultimately compile down to multiple underlying engines (e.g., Snowflake, Spark) to execute your requests efficiently in the Narrative ecosystem. - name: Payment Methods description: Payment methods used to purchase data - name: Products description: Internal routes used to offer datastream as products - name: Profiles description: >- App profiles are associated with an installation. They represent a reference to a configuration that the app can use to save confidential information outside of Narrative's control. Profiles are currently used to configure settings for connector apps. - name: Resources description: >- Narrative gives you access to managed resources, like your own AWS S3 bucket, so that you can effortlessly buy and sell data on the platform. The `resources` API allows you to manage your resources. - name: Schema Inference description: >- The `schema-inference` API analyzes submitted files to automatically infer and return their structure as a dataset schema. - name: Schema Presets description: >- The `schema-presets` API allows you to list the available schema presets, get detailed information about a specific one and manage its life cycle. You can create a schema preset from scratch or create one based on an existing one, administrators can create platform wide available (public) schema preset. - name: Subscriptions description: >- In the Narrative Data Collaboration Platform a subscription represents a set of rules dictating the commercial terms related to the licensing of data. The `subscriptions` API allows you to set and get information about `subscription` objects owned by the authenticated account. - name: Uploads description: >- The `uploads` API allows you to send files to Narrative and use them to perform tasks like creating a list or adding data to a dataset. - name: Usage description: >- The `usage` API enables the recording of usage events associated with a product. - name: Workflows description: >- The `workflows` API allows you to create, schedule, trigger, and archive workflows. Workflows are defined using a serverlessworkflow YAML specification. paths: /v2/views/{view_id}: put: tags: - Views summary: Updates a view description: Updates a view parameters: - $ref: '#/components/parameters/ViewId' requestBody: required: true content: application/json: schema: $ref: '#/components/schemas/UpdateViewRequest' responses: '200': description: OK content: application/json: schema: $ref: '#/components/schemas/ViewsResponse' security: - BearerAuth: [] components: parameters: ViewId: in: path name: view_id schema: type: string format: uuid required: true description: View identifier. schemas: UpdateViewRequest: type: object properties: name: $ref: '#/components/schemas/ViewName' display_name: $ref: '#/components/schemas/DisplayName' tags: $ref: '#/components/schemas/Tags' collaborators: $ref: '#/components/schemas/Collaborators' nql: type: string example: name: updated name tags: - tag3 ViewsResponse: oneOf: - $ref: '#/components/schemas/OwnedViewResponse' - $ref: '#/components/schemas/SharedViewResponse' ViewName: type: string description: >- It should be unique. Must be <= 256 characters and consist of only alphanumeric characters and underscores. DisplayName: type: string description: Optional. Display Name must be non-empty and less than 1000 chars. Tags: type: array items: type: string description: Optional. Each tag must be less than 256 chars. Collaborators: type: object description: Describes who can view or query a resource properties: view: $ref: '#/components/schemas/View' query: $ref: '#/components/schemas/Query' required: - view - query OwnedViewResponse: type: object properties: id: $ref: '#/components/schemas/ViewId' name: $ref: '#/components/schemas/ViewName' display_name: $ref: '#/components/schemas/DisplayName' tags: $ref: '#/components/schemas/Tags' collaborators: $ref: '#/components/schemas/Collaborators' owner: $ref: '#/components/schemas/shared_Owner' is_owned: $ref: '#/components/schemas/shared_IsOwned' metadata: $ref: '#/components/schemas/shared_Metadata' nql: type: string schema: $ref: '#/components/schemas/Schema' required: - id - name - collaborators - owner - metadata - nql example: name: view1 id: 7409b999-2a9a-40cd-89dc-8430d85e0391 display_name: Query One owner: company_id: 456 company_name: ExampleCorp company_slug: examplecorp tags: - tag1 - tag2 collaborators: query: type: inclusion company_ids: - 789 view: type: all is_owned: true metadata: created_at: '2024-04-12T19:57:05.012908' created_by_user_id: 321 updated_at: '2024-04-12T20:03:48.031825' updated_by_user_id: 321 nql: SELECT age FROM narrative.rosetta_stone schema: type: object properties: age: display_name: age type: double required: - id SharedViewResponse: type: object properties: id: $ref: '#/components/schemas/ViewId' name: $ref: '#/components/schemas/ViewName' display_name: $ref: '#/components/schemas/DisplayName' tags: $ref: '#/components/schemas/Tags' owner: $ref: '#/components/schemas/shared_Owner' is_owned: $ref: '#/components/schemas/shared_IsOwned' nql: type: string schema: $ref: '#/components/schemas/Schema' required: - id - name - owner - nql example: name: view1 id: 7409b999-2a9a-40cd-89dc-8430d85e0391 display_name: View One owner: company_id: 456 company_name: ExampleCorp company_slug: examplecorp tags: - tag1 - tag2 is_owned: false nql: SELECT age FROM narrative.rosetta_stone schema: type: object properties: age: display_name: age type: double required: - id View: description: Describes who can view a resource oneOf: - $ref: '#/components/schemas/All' - $ref: '#/components/schemas/None' - $ref: '#/components/schemas/Anonymous' - $ref: '#/components/schemas/Inclusion' - $ref: '#/components/schemas/Exclusion' discriminator: propertyName: type Query: description: Describes who can query a resource oneOf: - $ref: '#/components/schemas/All' - $ref: '#/components/schemas/None' - $ref: '#/components/schemas/Inclusion' - $ref: '#/components/schemas/Exclusion' discriminator: propertyName: type ViewId: type: string format: uuid shared_Owner: type: object description: Information about the owner of the view properties: company_id: $ref: '#/components/schemas/CompanyId' company_name: $ref: '#/components/schemas/CompanyName' company_slug: $ref: '#/components/schemas/CompanySlug' required: - company_id - company_name shared_IsOwned: type: boolean description: Whether the requestor owns the view. shared_Metadata: type: object description: Metadata about when and by whom a view was created/updated properties: created_by_user_id: $ref: '#/components/schemas/UserId' created_at: description: ISO-8601 timestamp indicating when the view was created. type: string updated_by_user_id: $ref: '#/components/schemas/UserId' updated_at: description: ISO-8601 timestamp indicating when the view was last updated. type: string required: - created_by_user_id - created_at - updated_by_user_id - updated_at Schema: type: object description: NQL schema for the view. additionalProperties: true All: type: object description: This resource is accessible by anyone. properties: type: type: string enum: - all required: - type None: type: object description: This resource is private to the owning company. properties: type: type: string enum: - none required: - type Anonymous: type: object description: This resource is visible to non-authenticated users. properties: type: type: string enum: - anonymous required: - type Inclusion: type: object description: This resource is accessible by all companies specified in `company_ids`. properties: type: type: string enum: - inclusion company_ids: type: array description: The companies to which the constraint applies. items: type: integer required: - type - company_ids Exclusion: type: object description: >- This resource is accessible by all companies _except_ those specified in `company_ids`. properties: type: type: string enum: - exclusion company_ids: type: array description: The companies to which the constraint applies. items: type: integer required: - type - company_ids CompanyId: type: integer format: int64 description: The id of an existing company example: 345 CompanyName: type: string description: Name of the company. CompanySlug: type: string description: Unique slug assigned to company. UserId: type: integer format: int64 description: The id of an existing user example: 345 securitySchemes: BearerAuth: type: http scheme: bearer ````