# Documentation > Get Orvelt on your website, choose the questions customers answer, and read what they say. - **Welcome to Orvelt** - [What is Orvelt?](/docs): Collect spoken or typed opinions through your website, QR codes, and links, ask each customer up to three questions, and verify they were really a customer. - [Quick start guide](/docs/quickstart): Put Orvelt's opinion form on your website, choose the questions customers answer, and read your first opinion in about 10 minutes. - **Using Orvelt** - Collect opinions - Add to your website - [Add Orvelt to your website](/docs/collect/website): Put Orvelt's opinion form on your own website, behind a Give feedback button or inside a page, with one copy-and-paste block. - [Shopify](/docs/collect/website/shopify): Put Orvelt's opinion form on any page of your Shopify store with a Custom Liquid section, no app or developer needed. - [Wix](/docs/collect/website/wix): Put Orvelt's opinion form on a Wix page with an Embed HTML element, and size it so the whole form shows. - [Squarespace](/docs/collect/website/squarespace): Put Orvelt's opinion form on a Squarespace page with a Code Block. - [WordPress](/docs/collect/website/wordpress): Put Orvelt's opinion form on a WordPress page or post with a Custom HTML block. - [Webflow](/docs/collect/website/webflow): Put Orvelt's opinion form on a Webflow page with a Code Embed element. - [Customize the form](/docs/collect/website/customize): Match the opinion form to your website's color, corners, and dark mode by adding a few lines to the block you pasted. - [Test the form](/docs/collect/website/test-the-form): Check the website form works end to end with a real submission, and fix the most common problems. - [Allowed origins](/docs/collect/website/allowed-origins): Choose which websites are allowed to show your opinion form, so it can't be copied onto sites you don't control. - [Voice opinions](/docs/collect/voice-opinions): Customers can speak their opinion instead of typing it, then check the text before submitting. - [QR codes](/docs/collect/qr-codes): Create a permanent QR code to print or a rotating QR code for a screen, so in-person customers can write a verified opinion in seconds. - [Personal links](/docs/collect/links): Email one customer a personal, one-time link to write a verified opinion, and track whether they opened it and responded. - [Subscribers](/docs/collect/subscribers): Invite customers to follow a project, import a list from a spreadsheet, and manage who's subscribed. - [What your customers see](/docs/collect/customer-experience): Walk through Orvelt from your customer's side, from finding your page to writing an opinion, answering your questions, and getting verified. - Research - Questions - [Create a question](/docs/research/questions/create): Write a question, preview how customers will answer it, and save it as a draft or set it active. - [Answer modes](/docs/research/questions/answer-modes): Choose between free text, single select, and multi select, and control how options look to customers. - [Public and private answers](/docs/research/questions/public-and-private): Decide who can read each question's answers. Public and private answers share the same monthly allowance. - [Archive, activate, and delete](/docs/research/questions/archive-and-limits): Keep your question library tidy over time, one question at a time or many at once, and stay within your plan's active-question limit. - [Writing good questions](/docs/research/questions/writing-good-questions): Practical guidance for questions customers answer quickly and honestly, with before-and-after examples. - [Goals](/docs/research/goals): Write down what your team needs to learn from customers, so Orvelt can fill your question library with questions that serve it. - [Tags and the Research Radar](/docs/research/tags-and-radar): Understand the eight research tags, choose which ones appear on the Research Radar, and read what customers lean toward. - [Priority and Auto priority](/docs/research/priority): Control how likely each question is to be picked, or let Orvelt adjust it automatically from your customers' answers. - [How questions are picked](/docs/research/how-questions-are-picked): Goals fill a question library, each customer gets the few questions that matter most, and every answer re-ranks what to ask next. - Opinions and answers - [Read opinions](/docs/feedback/opinions): Find, filter, and sort the opinions customers submitted, and open each one's thread. - [Reply to opinions](/docs/feedback/respond): Reply to a customer's opinion, see who can read your reply, and learn how to write replies that build trust. - [Read answers](/docs/feedback/answers): Search and filter every answer to your questions, see all of one customer's answers together, and download everything as CSV. - [Verification](/docs/feedback/verification): How Orvelt confirms an opinion came from a real customer, what each method proves, and how anyone can check a verification. - [Analytics](/docs/feedback/analytics): See who visits a project's page, people as well as AI agents and bots, and how many visitors go on to complete an opinion. - [Send feedback to other tools](/docs/feedback/connect-other-tools): Send a message to another system every time something happens in Orvelt, like a new opinion, so your other tools stay up to date automatically. - **AI** - [Connect Claude](/docs/ai): Add Orvelt to Claude on the web or Claude Desktop in about two minutes, then approve what Claude can read and change. - [Connect using MCP](/docs/ai/connect-coding-agents): Add Orvelt's Business MCP server to Claude Code, Codex, Cursor, VS Code, OpenCode, or Windsurf. - [What agents can do](/docs/ai/tools): Example prompts, every Business MCP tool and the access it needs, how access is limited, and fixes for common connection problems. - **Developers** - Developers - [Developer quickstart](/docs/developers): Create an API key, choose the TypeScript or Python SDK, and read your first opinions from your server. - [API keys](/docs/developers/api-keys): Create an API key for your developer or one of your systems, store it safely, and replace or delete it when needed. - [Authentication](/docs/developers/authentication): Authenticate with an organization API key, an OAuth app grant, or a Business browser session. - [Orvelt TypeScript SDK](/docs/developers/typescript-sdk): Install and configure the Orvelt TypeScript SDK, read typed results, handle errors, and upgrade the client. - [Orvelt Python SDK](/docs/developers/python-sdk): Install and configure the Orvelt Python SDK, read typed results, handle errors, and upgrade the client. - Questions API - [Create questions](/docs/developers/questions/create): Add the questions you want customers to answer, choose how they answer, and check that they are being asked. - [Auto priority](/docs/developers/questions/priority): Leave Auto priority on so answers decide what gets asked, pin a priority when you need to, and edit or retire questions without losing history. - [Question results](/docs/developers/questions/results): Review your question library, count the answers to each question, and follow how Orvelt re-ranks them. - Collection API - [Website embed](/docs/developers/collect/website-embed): Let customers write an opinion and answer your questions without leaving your site. One script tag, no API key, no backend. - [Embed options](/docs/developers/collect/embed-options): Every orveltEmbed option and method, styling hooks, and how visitor sessions expire and recover. - [Delivery links](/docs/developers/collect/delivery-links): Email each customer a personal opinion link when an order completes, remind those who have not answered, and see who responded. - [QR codes](/docs/developers/collect/qr-codes): Collect verified opinions at your counter, table, or screen, and keep a rotating code fresh on your own display. - [Subscribers](/docs/developers/collect/subscribers): Invite customers to follow your project, track how your audience grows, and find a subscriber when you need to. - Feedback API - [Sync opinions and answers](/docs/developers/feedback/sync): Copy new opinions and answers into your CRM, data warehouse, or support tool on a schedule. - [Replies](/docs/developers/feedback/reply): Build a queue of opinions waiting for a reply, and post replies from your own support tools. - [Webhooks](/docs/developers/feedback/webhooks): Have Orvelt call your server the moment a customer posts an opinion, answers a question, or verifies a purchase. - [Errors](/docs/developers/errors): What each Business API status means, how to recover, and how to stay under the rate limit. - [Pagination](/docs/developers/pagination): Page through collections and filter opinions and answers by date. - API reference - [Business API](/docs/api-reference): Every Business API endpoint and webhook event, generated from the API contract. - **OAuth** - [oauthConnections.operations](/docs/api-reference/endpoints/oauth/oauthConnections.operations): Requires an OAuth access token. Discovery is limited to the grant; execution rechecks current permissions. - **Billing** - [Get billing entitlements](/docs/api-reference/endpoints/billing/billing.entitlements): Get the organization's current plan, feature entitlements, and usage limits. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - **Projects** - [List projects](/docs/api-reference/endpoints/projects/projects.list): List the projects in the organization that the caller can access. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Create a project](/docs/api-reference/endpoints/projects/projects.create): Create a project with its own team. The creator is added to the project team. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Get a project](/docs/api-reference/endpoints/projects/project.get): Get one project by ID. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Update a project](/docs/api-reference/endpoints/projects/project.update): Update a project's name, slug, description, status, or settings. Archived projects can be restored. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Delete a project](/docs/api-reference/endpoints/projects/project.delete): Delete a project and its team. The root storefront project cannot be deleted. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Upload a project asset](/docs/api-reference/endpoints/projects/project.upload): Upload an image for a project and return its public URL. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Get project appearance](/docs/api-reference/endpoints/projects/project.appearance.get): Get the colors, theme, background, font, logo, and copy a project's customer pages use. Projects without a saved appearance return the defaults. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Reset project appearance](/docs/api-reference/endpoints/projects/project.appearance.reset): Remove a project's saved appearance so its customer pages use the defaults. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Update project appearance](/docs/api-reference/endpoints/projects/project.appearance.update): Replace a project's appearance. The logo and background image must be assets uploaded to the project, and the accent must stay readable in each color scheme the theme uses. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - **Goals** - [List goals](/docs/api-reference/endpoints/project-goals/project.goals.list): List a project's goals. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Create a goal](/docs/api-reference/endpoints/project-goals/project.goals.create): Add a goal to a project. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Update a goal](/docs/api-reference/endpoints/project-goals/project.goals.update): Update a project goal. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Delete a goal](/docs/api-reference/endpoints/project-goals/project.goals.delete): Remove a goal from a project. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - **Questions** - [List questions](/docs/api-reference/endpoints/project-questions/project.questions.list): List a project's guided questions. API-key permission: `questions` read. Business sessions and resource-authorized OAuth tokens are also supported. - [Create a question](/docs/api-reference/endpoints/project-questions/project.questions.create): Add a guided question to a project. API-key permission: `questions` create. Business sessions and resource-authorized OAuth tokens are also supported. - [Update a question](/docs/api-reference/endpoints/project-questions/project.questions.update): Change settings, activate, or archive a question version. API-key permission: `questions` update. Business sessions and resource-authorized OAuth tokens are also supported. - [Delete a question](/docs/api-reference/endpoints/project-questions/project.questions.delete): Remove a question from a project. API-key permission: `questions` delete. Business sessions and resource-authorized OAuth tokens are also supported. - [Create a question version](/docs/api-reference/endpoints/project-questions/project.questions.versions.create): Save new wording without changing the original question version. API-key permission: `questions` update. Business sessions and resource-authorized OAuth tokens are also supported. - **Tags** - [Get tags](/docs/api-reference/endpoints/project-tags/project.tags.get): Get the tags a project measures and their order. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Update tags](/docs/api-reference/endpoints/project-tags/project.tags.update): Choose and order the tags a project measures. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - **Delivery** - [List delivery links](/docs/api-reference/endpoints/project-delivery/project.link.list): List a project's delivery links and their status. API-key permission: `link` read. Business sessions and resource-authorized OAuth tokens are also supported. - [Create a delivery link](/docs/api-reference/endpoints/project-delivery/project.link.create): Create a pre-verified opinion link for one customer and optionally email it. Each project can email the same customer once every 48 hours. API-key permission: `link` create. Business sessions and resource-authorized OAuth tokens are also supported. - [Resend a delivery link](/docs/api-reference/endpoints/project-delivery/project.link.resend): Email an existing, unexpired delivery link to its customer again. The 48-hour email cooldown applies. API-key permission: `link` create. Business sessions and resource-authorized OAuth tokens are also supported. - [Get embedded form settings](/docs/api-reference/endpoints/project-delivery/project.embed.get): Get the project's embedded opinion form settings, including allowed origins. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Update embedded form settings](/docs/api-reference/endpoints/project-delivery/project.embed.update): Update the project's embedded opinion form settings. An empty origin list allows every website. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - **QR Codes** - [Display a rotating QR code](/docs/api-reference/endpoints/project-qr-codes/project.qr.display): Get the current link for the project's rotating QR code. Fetch it again when `validUntil` passes. API-key permission: `qr` read. Business sessions and resource-authorized OAuth tokens are also supported. - **Opinions** - [List opinions](/docs/api-reference/endpoints/project-opinions/project.opinions.list): List a project's opinions with search, reply-status, and date filters. API-key permission: `opinions` read. Business sessions and resource-authorized OAuth tokens are also supported. - [Respond to an opinion](/docs/api-reference/endpoints/project-opinions/project.opinions.reply): Post a public team response to an opinion. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - **Answers** - [List answers](/docs/api-reference/endpoints/project-answers/project.answers.list): List customers' answers to a project's questions. API-key permission: `answers` read. Business sessions and resource-authorized OAuth tokens are also supported. - **Subscribers** - [List subscribers](/docs/api-reference/endpoints/project-subscribers/project.subscribers.list): List a project's subscribers. API-key permission: `subscribers` read. Business sessions and resource-authorized OAuth tokens are also supported. - [Count subscribers](/docs/api-reference/endpoints/project-subscribers/project.subscribers.count): Count a project's subscribers. API-key permission: `subscribers` read. Business sessions and resource-authorized OAuth tokens are also supported. - [Invite subscribers](/docs/api-reference/endpoints/project-subscribers/project.subscribers.invite): Email invitations to subscribe to a project. API-key permission: `subscribers` invite. Business sessions and resource-authorized OAuth tokens are also supported. - **Knowledge Base** - [Get knowledge base](/docs/api-reference/endpoints/knowledge-base/kb.get): Get the organization's knowledge base items. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Add a knowledge base item](/docs/api-reference/endpoints/knowledge-base/kb.create): Add an item to the organization knowledge base. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Update a knowledge base item](/docs/api-reference/endpoints/knowledge-base/kb.update): Update an organization knowledge base item. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Delete a knowledge base item](/docs/api-reference/endpoints/knowledge-base/kb.delete): Delete an organization knowledge base item. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - **Webhooks** - [Open the webhook portal](/docs/api-reference/endpoints/webhooks/webhooks.portal): Get a short-lived link to the hosted webhook portal, where you can manage destinations and retry deliveries. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [Save a webhook destination](/docs/api-reference/endpoints/webhooks/webhooks.upsert): Create or update a webhook destination URL and the event topics it receives. Requires a Business session or a resource-authorized OAuth token and the applicable member access. API keys are not accepted. - [response.submitted](/docs/api-reference/endpoints/webhooks/response.submitted): A customer submitted a response. Each answer they gave arrives as `answer.created`. Payload version 1. `data` is a snapshot of the resource after the change. - [opinion.created](/docs/api-reference/endpoints/webhooks/opinion.created): A customer submitted an opinion for a response. Each answer arrives as `answer.created`. Payload version 5. `data` is a snapshot of the resource after the change. - [opinion.updated](/docs/api-reference/endpoints/webhooks/opinion.updated): A customer edited a submitted opinion's content. Payload version 5. `data` is a snapshot of the resource after the change. - [opinion.deleted](/docs/api-reference/endpoints/webhooks/opinion.deleted): A customer deleted a submitted opinion; its response and answers remain. Payload version 2. `data` is a snapshot of the resource after the change. - [answer.created](/docs/api-reference/endpoints/webhooks/answer.created): A customer answered a project question. Payload version 3. `data` is a snapshot of the resource after the change. - [answer.updated](/docs/api-reference/endpoints/webhooks/answer.updated): A customer changed their answer to a project question. Payload version 3. `data` is a snapshot of the resource after the change. - [comment.created](/docs/api-reference/endpoints/webhooks/comment.created): A customer commented on an opinion, or your team responded to one. Payload version 2. `data` is a snapshot of the resource after the change. - [comment.updated](/docs/api-reference/endpoints/webhooks/comment.updated): A comment or team response on an opinion was edited. Payload version 2. `data` is a snapshot of the resource after the change. - [comment.deleted](/docs/api-reference/endpoints/webhooks/comment.deleted): A customer deleted their comment on an opinion. Payload version 2. `data` is a snapshot of the resource after the change. - [verification.created](/docs/api-reference/endpoints/webhooks/verification.created): A purchase verification started: a delivery link, store QR code, or receipt. Payload version 2. `data` is a snapshot of the resource after the change. - [verification.verified](/docs/api-reference/endpoints/webhooks/verification.verified): A customer's purchase was verified. Payload version 2. `data` is a snapshot of the resource after the change. - [verification.failed](/docs/api-reference/endpoints/webhooks/verification.failed): A verification did not complete successfully. `status` identifies whether it was rejected, expired, or cancelled. Payload version 2. `data` is a snapshot of the resource after the change. - [link.created](/docs/api-reference/endpoints/webhooks/link.created): A delivery link was created for a customer. Payload version 3. `data` is a snapshot of the resource after the change. - [link.emailed](/docs/api-reference/endpoints/webhooks/link.emailed): A delivery link was emailed to its customer. Payload version 3. `data` is a snapshot of the resource after the change. - [link.clicked](/docs/api-reference/endpoints/webhooks/link.clicked): A customer opened their delivery link and started an opinion with it. Payload version 3. `data` is a snapshot of the resource after the change. - [link.submitted](/docs/api-reference/endpoints/webhooks/link.submitted): A customer submitted an opinion with their delivery link, which verifies it. The link cannot be used again. Payload version 3. `data` is a snapshot of the resource after the change. - [subscriber.created](/docs/api-reference/endpoints/webhooks/subscriber.created): A customer subscribed to a project, directly or by accepting an invitation. Payload version 1. `data` is a snapshot of the resource after the change. - [subscriber.deleted](/docs/api-reference/endpoints/webhooks/subscriber.deleted): A customer unsubscribed from a project, or your team removed them. Payload version 1. `data` is a snapshot of the resource after the change. - [project.created](/docs/api-reference/endpoints/webhooks/project.created): A project was created. Payload version 1. `data` is a snapshot of the resource after the change. - [project.updated](/docs/api-reference/endpoints/webhooks/project.updated): A project's name, slug, description, status, or settings changed. Payload version 1. `data` is a snapshot of the resource after the change. - [project.deleted](/docs/api-reference/endpoints/webhooks/project.deleted): A project was deleted. Payload version 1. `data` is a snapshot of the resource after the change. - [question.created](/docs/api-reference/endpoints/webhooks/question.created): A question was added to a project. Payload version 1. `data` is a snapshot of the resource after the change. - [question.updated](/docs/api-reference/endpoints/webhooks/question.updated): A project question was edited, activated, or archived. Payload version 1. `data` is a snapshot of the resource after the change. - [question.deleted](/docs/api-reference/endpoints/webhooks/question.deleted): A question was removed from a project. Payload version 1. `data` is a snapshot of the resource after the change. - [qr_code.created](/docs/api-reference/endpoints/webhooks/qr_code.created): An opinion QR code was created. Payload version 1. `data` is a snapshot of the resource after the change. - [qr_code.regenerated](/docs/api-reference/endpoints/webhooks/qr_code.regenerated): An opinion QR code was regenerated, invalidating printed copies. Payload version 1. `data` is a snapshot of the resource after the change. - [qr_code.revoked](/docs/api-reference/endpoints/webhooks/qr_code.revoked): An opinion QR code was revoked. Payload version 1. `data` is a snapshot of the resource after the change. - **Business and account** - Set up your business - [Create your business](/docs/setup/create-business): Sign up for Orvelt Business and complete the three-step setup that creates your organization, your public Storefront, and your first project. - [Storefront details](/docs/setup/storefront-details): Control how your business appears to customers on its public Storefront page, including name, logo, description, contact links, URL, and categories. - [Location and opening hours](/docs/setup/location-hours): Publish your address, time zone, accessibility information, and weekly opening hours, or mark your business as online only. - [Knowledge base](/docs/setup/knowledge-base): Give Orvelt trusted information about your business from webpages, notes, and files. - [Business terms](/docs/setup/business-terms): Help voice opinions spell your business, product, and staff names correctly. - Projects - [Create a project](/docs/projects/create): Add a new project with its own page, questions, and team, in under a minute, and choose whether it collects public reviews or private feedback. - [Project settings](/docs/projects/settings): Rename a project, change its web address, status, or visibility, find its IDs, archive or restore it, or delete it for good. - [Customize appearance](/docs/projects/appearance): Change the colors, theme, font, background, logo, and wording of a project's embedded form and public page. - [Project team](/docs/projects/team): Choose which members of your organization can work on each project, and remove access when someone moves on. - Organization and account - [Team and roles](/docs/organization/team-and-roles): Invite colleagues, choose their role and exactly what they can access, and change or remove access later. - [Billing and plans](/docs/organization/billing): Check your plan and usage, compare plans, change or cancel, and manage invoices, payment details, and your billing address. - [Your settings](/docs/organization/settings): Update your own profile, theme, and notification preferences in Orvelt Business. - [Security](/docs/organization/security): Protect your Orvelt Business sign-in with a verified email, a linked Google account, and passkeys. - [Fix access problems](/docs/organization/troubleshooting): What to do when you see Access Forbidden, a page is missing from your sidebar, or you can't find an organization or project. - [Vocabulary](/docs/vocabulary): Every word you'll see in Orvelt, explained in plain language, from "opinion" and "answer" to "rotating QR" and "Auto priority".