A little guidance.
Endless possibilities.

Sign in and open Dashboard. Choose Create a survey, enter a clear title and choose the workspace. Or visit Template library and use a relevant starting point.

In Build, add the questions you actually need. Use a short introduction to explain the purpose, expected effort and how responses will be used.

Choose your privacy mode before collecting answers. Add required questions sparingly and check every conditional path.

In Design & Branding, choose a theme and customise it. Add any translations in Languages, including the completion message.

Use Preview to check your current edits. Save draft to keep private work, or Save & publish when ready. Check Collect and its test/live setting before distributing a link.

Share through the appropriate link, invitation or QR code. Review Results, identify a useful action and communicate what you learned.

Use Dashboard for recent surveys, workspace totals and the response trend. The response chart covers the last 30 days and offers exact daily figures.

Open All surveys to search by title and continue editing. Each survey has its own Build, Design & Branding, Collect, Results, Manage and Languages tabs.

Use the main menu for account-wide tools: contacts, campaigns, analytics, branding, team settings and support, according to your permissions.

Collapse the main menu when you want more editing room. On small screens, open the menu drawer; field settings adapt to the available space.

Replace leading questions such as “How excellent was our service?” with “How would you rate the service?”

Split combined questions: speed and friendliness may deserve different answers. Specify a time period where it matters.

Keep answer choices distinct. Add a relevant “Not applicable” option where respondents may have no experience.

Put easy questions first, group related topics and leave optional comments near the end. Explain why sensitive information is needed.

Pilot the survey with someone outside your team. Watch for confusing labels, missing choices and unnecessary required fields.

Choose a field from Add fields or search the palette. Click to insert it, or drag it to an insertion line on the canvas.

Select a question to edit its label, help text, answer choices and applicable validation. Use the field type that matches the answer you need.

Use drag handles or the provided move controls to reorder fields. Use Outline to navigate a longer survey.

Use Undo and Redo for recent editing changes, and Collapse all or Expand all to control the canvas. Save your draft regularly.

Open Survey settings for the overall introduction, privacy and submission limit. Open Completion message for the final heading and thank-you text.

Use Required answer only where an answer is necessary. A required question that does not apply to someone can stop them completing the survey.

For choice fields, enter distinct options. Keep labels concise. Use selection limits on Multiple choice when a minimum or maximum number is needed.

For text, choose an appropriate maximum length. For numeric fields, set meaningful minimum and maximum values.

Where appropriate, randomise unordered choices to reduce ordering effects. Keep ordinal scales in their natural order.

Use answer scores only with a defined interpretation. Test the full survey, including blank optional answers and values at the boundaries.

Create the controlling question first, such as “Have you used our support service?” with Yes and No.

Select the follow-up field and configure Show when using the earlier question, the available operator and the answer to match.

Use End when only when a matching answer should end participation before that question. Write a clear survey introduction if eligibility is important.

Keep dependencies in order when moving or deleting fields. Test every possible branch in Preview, including missing optional answers.

For answer piping, use the supported earlier-question reference in a label, such as {{first_name}} when that is the actual question ID. Check the resulting wording in Preview.

Add a Section before its related questions. Give it a useful heading and, if needed, a short explanation.

Place questions inside the intended section using the builder controls. Questions in a section use the section’s page.

Set page positions in the applicable field settings and keep page order consistent when rearranging the survey.

Use Line separator sparingly to divide related blocks. Do not add a new section for every short question.

Preview the full flow on Desktop and Phone. Check that each page has a clear purpose and that required fields are easy to find.

Open Build → Survey settings and review the available privacy modes. Identified collection is suitable when responses need to relate to known participants.

Use anonymous collection when your questions should not identify the respondent. Avoid names, email addresses, identifying links and identifying free-text prompts.

Controlled-anonymous collection uses controlled participation while protecting the response identity in the designed workflow. Review the privacy explanation and invitation behaviour before rollout.

If privacy changes are restricted after publication or collection, use the available copy workflow instead of trying to reinterpret existing responses.

Test the correct public or invitation link and confirm the introductory privacy message matches how you actually collect and use the data.

In Survey settings, set Maximum submissions. A value of 0 means unlimited within the applicable platform and plan allowances.

Use answer-based quotas where a specific group needs a cap. Choose the question, matching value and limit; keep a distinct quota key.

Save and publish the draft to apply quota changes. Review the displayed usage when updating an existing quota.

Counts start when a quota is first published and persist across versions. Changing its matching question or answer starts a new count; removing the quota removes that limit after publishing.

Test boundary behaviour before promoting the survey. A submission cap is not the same as a promise of one response per person.

Use Preview to review the current editing state, including unsaved changes supported by the active editor. Check text, layout, rules and language selection.

Choose Save draft to keep your edits privately. The saved-status message tells you whether draft changes still need publishing.

Choose Save & publish only when the draft is ready for respondents. Resolve any publish-readiness checks first.

Use Open survey to view the respondent-facing published survey. It is separate from an editing preview and may behave according to the current collection mode.

After publishing, verify the live link and selected language. Existing responses remain attached to the version originally answered.

Open Manage and use Reset draft to published when you want the draft to match the current published version again. Review the confirmation because draft edits will be discarded.

Open Published versions to inspect available versions. Restore a selected version to draft if you want to work from an earlier definition.

Preview the restored draft, edit if needed and publish when ready. A survey without a published version has no live definition to reset to.

Use Duplicate survey to create a separate starting point, or Save as template when a reusable structure belongs in your organisation’s library.

Use collection and archive actions deliberately. Closing collection stops new participation; archiving is an organisational lifecycle action. Existing results are not a substitute for a backup.

Open Design & Branding → Appearance. Filter the theme gallery by category, including gradients, solid colours, education, children and science.

Select a theme to preview it. Review the saved-theme label and the selected preview before applying anything.

Choose Keep my current page background if you only want the new palette. Apply theme updates the editing controls; Undo theme lets you reverse that theme application.

Refine Text colour, Survey panel and Accent colour. Accent colours style buttons, selections and the survey’s top border.

Check the preview on Desktop and Phone, then save the draft or publish when ready. Keep text readable against both the panel and surrounding page.

Choose a background type: a solid colour, gradient, pattern or your image. Use the gallery category filter to narrow the available styles.

For a custom gradient, choose the available colour stops and adjust its angle. Preview the balance around the survey panel.

For patterns, adjust the pattern colour and intensity. Use the size slider from 25% to 1000% and rotation from 0° to 360°.

For your own image, use an appropriate uploaded asset where your plan supports it. Avoid an image that becomes distracting or unreadable when cropped on a phone.

Keep the question panel distinct. Test both light and dark areas of the page and use subtle intensity for busy patterns.

Open Design & Branding and choose the logo or identity section. Select or upload the asset supported by your current plan.

Review the logo placement, size and layout controls. Use a clean image with enough surrounding space so it remains legible on mobile.

Choose a font, button style, width and corner treatment that support your brand. Avoid making the survey unusually narrow or visually crowded.

Use Files & logos to find the assets already associated with the survey. Use the organisation branding tools for shared identity settings where available.

Preview image and PDF content before publishing. Keep the file name and description meaningful to the person who will view it.

Open Languages and confirm the original survey language. Add the target language you want to support.

Translate the title, introduction, question labels, help text, choices, rows and other text presented by the editor. Include the completion heading and thank-you message.

Enable a language when it is ready. Disable it to keep the translation in the draft without offering it as an active respondent language.

Use the edit controls to maintain an existing language. Delete a translation only when you no longer need that language’s text.

Preview and publish the full language update using the shared toolbar. After editing the original questions, review each translation again for changed meaning or missing text.

Add and publish the languages your audience needs. A browser language can only match a translation that is available in that published survey.

Test a matching language, a regional variant and an unsupported language. The original language is the fallback when no suitable translation is available.

A respondent’s explicit language choice takes priority over automatic preference matching. Remembered choices can also affect later visits.

In the translation editor, use Open in Google Translate for a source field. It opens the external translation page with the source and target languages.

Review the suggested translation and copy it back into the matching field. For long text, use Copy original and paste it on the translation page. Then save and publish through Arynox.

Publish the survey and open Collect. Check the collection state, privacy mode and test/live setting before sharing.

Copy the appropriate public link for an open survey. If your plan supports a custom short code, choose one that is memorable and review the final link.

Generate or download the QR code where available. Scan it on a real phone before printing or distributing it.

Put a short explanation next to the code: what the survey is for, how long it takes and who should answer. Include a readable link as an alternative.

For controlled or personal invitations, use the invitation workflow instead of replacing personal links with a public link.

Review the Test or Live indicator in the survey workspace. Use test collection while checking layout, rules and end-to-end behaviour.

Submit example responses through the appropriate test link and inspect what appears in Results. Keep track of test submissions before launch.

When ready, change the supported collection setting to live and verify the respondent link again.

Use Close collection when you want to stop accepting new responses. Reopen it through the available controls when appropriate.

If someone cannot submit, check closure, response limits, quotas, invitation validity and plan access before changing the questionnaire.

Open Contacts to add or edit individual records. Use clear names and valid email addresses.

For CSV imports, follow the columns shown by the import screen, including email, name and consent where requested. Inspect a small sample before importing a larger list.

Review existing records and duplicate handling. Do not assume importing a file grants permission to send invitations.

Use suppression controls when a contact should not receive campaign mail. Keep the invitation purpose aligned with what recipients expect.

Choose the intended recipients when building a campaign, then review the send list before starting it.

Open Campaigns and create or edit a campaign for the intended survey. Select the appropriate contacts and invitation settings.

Write a clear subject and message. Explain why the recipient is receiving the invitation and use the survey link provided by the campaign workflow.

Review the campaign, schedule or start it through the available controls, and check the confirmation.

Use reminders for eligible recipients where supported. Review who will receive them rather than repeatedly sending the original campaign to everyone.

Check Email delivery for queued, accepted, failed or suppressed messages. Resolve the underlying reason before retrying failures.

Open the survey’s Results tab. Review the relevant version and available filters before comparing numbers.

Look at distributions, not just a single average. A mixed set of very high and very low ratings can hide behind a moderate average.

Read comments alongside structured answers. Avoid treating a memorable comment as representative of everyone.

Inspect individual responses where your role permits it. Use internal notes for your team’s follow-up rather than rewriting the respondent’s answer.

Agree on an action, owner and review date. Consider a follow-up survey using comparable questions to see whether the change helped.

Apply the relevant survey, version and answer filters before reviewing or exporting. Confirm the visible scope in the results tools.

Use CSV for a portable tabular export. XLSX availability depends on the installation. Check column labels and date handling in your spreadsheet tool.

Save a useful report view where supported so your team can return to a consistent selection.

Use aggregate report sharing when a recipient needs summaries rather than access to your whole customer portal. Set an expiry where the sharing controls provide one.

Open a shared report as the recipient would and verify its scope before forwarding the link. Revoke or replace links when access should end.

Use the dedicated Net Promoter Score field for a recommendation question. Keep its standard 0–10 answer range.

For NPS interpretation, 9–10 are promoters, 7–8 are passives and 0–6 are detractors. NPS is the percentage of promoters minus the percentage of detractors.

Read the score with the number of responses and the audience in mind. Small or changing samples can move the result substantially.

Use an optional comment or a targeted follow-up to understand the reasons behind the number.

Compare like with like: question wording, audience, timing and collection method should remain consistent if you are tracking a trend.

Use the account selector to confirm you are working in the intended organisation. Survey and dashboard data follow that active context.

If your role permits it, open Users & roles to invite colleagues and choose the appropriate role.

Give creators editing access and analysts the reporting access they need. Review custom role permissions where available.

Use workspaces to organise surveys by team or purpose. Keep names clear so people choose the right destination when creating a survey.

Review access when someone changes role or leaves. Use My Account for your own profile, password and sign-in security.

Open Subscription to inspect the active plan and available changes. Review the stated allowances and any limited-access duration.

Use Billing & invoices for billing details and available payment or invoice actions, according to your role.

If a feature is unavailable, check both your role and your plan. Upload, branding, QR and other capabilities may have separate allowances.

When access expires, follow the offered upgrade or plan-change path. Review the notice describing how your current plan behaves.

Contact support if a purchase or entitlement appears inconsistent. Include the relevant account and a clear description, without sending payment secrets.

Open Support to review current and older tickets in their sections. Open the relevant ticket before starting a duplicate conversation.

Read the newest answer at the top, then reply in the same ticket with the requested details.

Opening a ticket marks the displayed updates as viewed. Mark it unread manually if you want a reminder to return.

When updates are viewed or no qualifying updates remain, the unread notice should disappear. Completed and archived states follow the configured notification behaviour.

Open My Account → Support settings to choose sound preferences. Your browser may need an initial interaction before it can play a soft notification sound.

Open Integrations in the customer portal. Choose API keys, Webhooks or Custom domains.

Read your effective allowances in the Developer Centre. API permissions require both the key and the current customer agreement.

Create a separate expiring key for each server-side integration. Keep it out of browser code, public repositories and screenshots.

Use the API v1 guide for read and write examples. Saving through the API creates or edits a draft; publishing is a separate operation.

Set up response webhooks if you need your system to learn when a response arrives. Keep the private worker running and validate signatures.

Changes missing from the live survey: check the saved-status message, publish the intended draft and reopen the published link.

Wrong language: confirm that the translation is enabled and published. Check explicit or remembered language choices before testing browser preference detection.

Cannot submit: review required fields, validation, collection closure, invitation validity, quotas, submission limits and plan access.

Missing email: inspect the delivery state and recipient eligibility. Check suppression and spam folders; accepted by a mail server does not guarantee inbox placement.

Layout problem: compare the same published version and language on the affected screen size. Capture a clean screenshot and note browser, page and steps.

Unexpected unread notice: open the relevant ticket and read the latest reply. Check whether it was manually marked unread and whether another ticket still has updates.

Purpose: the introduction explains why you are asking, who should answer and how feedback will be used.

Questions: labels are neutral, options are complete and every required field is necessary. Test each conditional route.

Design: text is readable, images are appropriate and the page works on Desktop and Phone.

Languages: review every enabled translation, including answer choices and the completion message.

Collection: confirm the published version, privacy mode, test/live state, link or invitation, quotas and submission limit.

Follow-through: check that results appear as expected and decide who will review and act on them.

Open Build → Add fields and select Single choice.

Use for one main reason, one preference or a yes/no decision. Add the field, enter at least two unique options and decide whether an answer is required.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Multiple choice.

Use for interests, feature requests or all applicable reasons. Set minimum and maximum selections when a deliberate limit is useful.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Dropdown.

Use for a longer list of mutually exclusive choices. Add clear options and keep the initial prompt distinct from a real answer.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Short text.

Use for a brief label, a short suggestion or an identified reference where appropriate. Set a sensible character limit and add help text if a format is expected.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Long text.

Use for comments, stories and qualitative feedback. Keep the prompt focused and usually optional; review themes across comments rather than selecting only memorable examples.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Email or URL.

Choose Email or URL in the field settings. Use email for an identified follow-up and URL for a relevant website. The two formats validate differently.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Number.

Use for counts or measurements. Explain the unit and choose an appropriate minimum and maximum. Numeric input supports decimal values where applicable.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Date and time.

Use when a time as well as a date matters. Explain the expected local context, because the field is not itself an appointment-booking system.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Rating.

Choose the scale maximum, from 2 through 10, and explain what the endpoints mean. Use the same wording and range when tracking results over time.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Net Promoter Score.

Use for likelihood to recommend, with 0 meaning not at all likely and 10 extremely likely. Follow up with an optional reason to make the number more useful.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Slider.

Use for a bounded perception or approximate amount. Set meaningful limits and explain the endpoints so people know what they are moving toward.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Matrix.

Add row labels and shared answer options. Use it when topics genuinely share the same scale, such as clarity, pace and usefulness. Review the phone layout.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Ranking.

Enter the items to rank. Respondents assign each option once across the rank positions. Use a short list when relative priority matters more than a separate score.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select File upload.

Use only when a file is necessary and the survey mode permits it. The respondent control supports PDF, PNG, JPEG and plain text; the installation controls the size limit.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Consent.

Write the statement clearly and provide the relevant information before asking for agreement. Decide deliberately whether agreement must be required.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Display content.

Use for instructions, a short privacy explanation or a transition between topics. Put the main information in the content text and keep it easy to skim.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Image or PDF content.

Choose an uploaded image or PDF from the supported content controls. Give it a useful title and place the related questions directly after it.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Section.

Insert a section before its questions, name the topic and add a short explanation if needed. Assign related fields to it and keep their page consistent.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Open Build → Add fields and select Line separator.

Use between short groups where a full section heading is unnecessary. Preview the spacing so the page remains cohesive.

Add any applicable help text, required-answer rule and validation. Preview the field in context, then save your draft.

Start with a Display content introduction explaining that the survey is about the recent visit or purchase.

Add Single choice for the relevant service or product, Rating for the experience and Long text for an optional improvement.

If using NPS, ask a recommendation question rather than reusing the satisfaction wording. Add a reason only if you plan to read it.

Use your brand palette, preview on a phone and share the published link or a tested QR code at the point of experience.

Review distributions and comments together. Pick one action to trial and repeat the same core questions after the change.

Explain who will review results and how they will be used. Choose the correct privacy mode before adding fields.

Use a short Matrix or several Ratings for topics such as clarity, workload and support. Keep the same scale throughout.

Add one optional Long text question about what would help. Do not require names or identifying details in an anonymous questionnaire.

Offer the languages your team needs and review the translated wording with fluent colleagues.

Report findings in a way that respects your stated privacy approach and tell the team what action will follow.

Use a clear introductory statement and simple labels. Choose an education theme or a subtle pattern with high-contrast text.

Ask a Rating about confidence or usefulness, Single choice about the most helpful activity and optional Long text for a suggestion.

Use Display content or an Image field to provide context when needed; keep the number of questions modest.

Check the actual phone layout and any shared-device workflow before distributing a link or QR code.

Use the feedback to change the next session and explain the improvement to participants.

Use Display content for the study explanation and Consent where appropriate to your process.

Add eligibility questions before relevant conditional follow-ups. Test both eligible and ineligible paths.

Use Media to show a concept, Rating or Matrix for comparable judgments and Ranking for a short set of priorities.

If using quotas, define the answer groups and limits before launch. Review translations for meaning, not just literal wording.

Keep a record of the published version and export the appropriate scope for analysis.

Ask which session the person attended using Dropdown or Single choice.

Use a consistent Rating for usefulness and a brief optional comment for the next event.

Show follow-ups only for relevant sessions where conditional logic makes the survey shorter.

Print a tested QR code or send a campaign to the appropriate consenting recipients. Set a clear collection window.

Review the results by the relevant session and share actionable feedback with the organisers.

Accent: the colour used for key survey controls. Asset: an uploaded image, PDF or brand file. Branching: showing or ending questions based on an earlier answer.

Campaign: an invitation or reminder workflow for a chosen audience. Collection: the process of accepting survey responses. Draft: your editable, unpublished working copy.

Enabled language: a translation offered when it is part of the published survey. Field: a question, content item or layout element. Filter: a way to narrow the records or guide topics you see.

NPS: recommendation score based on a 0–10 question. Panel: the surface containing the survey questions. Preview: a way to inspect current work before publication.

Published version: the definition respondents answer. QR code: a scannable representation of a link. Quota: an accepted-response limit for a matching answer.

Required: an answer needed to proceed when the question applies. Section: a group of related fields. Suppression: preventing a contact from receiving outreach.

Theme: a coordinated appearance preset. Translation: language-specific text for the same survey. Workspace: an organisational grouping for your surveys.

Before you begin: you need a domain your organisation owns, access to its DNS settings, and a plan that includes custom domains. If someone else manages DNS, send them the exact records shown in your portal. You do not need to move your company website or email.

Open Integrations → Custom domains. Choose a dedicated address such as feedback.yourcompany.com. Enter it without https://, a slash, a port or a survey path. Click Add domain to generate your unique DNS instructions.

Sign in to the provider that manages your domain DNS. This may be your registrar, hosting company or another DNS provider. Open DNS settings, DNS records or Zone Editor. Select the zone for your company domain.

Add a TXT record. Copy the TXT record name and the entire TXT record value displayed by Arynox, including arynox-verification=. Do not use a token from an example or another customer. Leave TTL at its default and save.

Add a CNAME record. Copy the displayed CNAME record name and CNAME target. Enter the target as a hostname, without https://. If a proxy switch is offered, choose DNS only. Leave TTL at its default and save.

Check how your DNS provider handles names. For feedback.example.com in the example.com zone, some providers want feedback for the CNAME name and _arynox.feedback for the TXT name; others want the complete names. Check the saved names so example.com is not appended twice.

Return to Custom domains. Background checks detect the DNS records. When hosting automation is enabled, Arynox also configures hosting and requests HTTPS. Otherwise, contact support to complete hosting. You can click Verify DNS & HTTPS to check readiness and refresh the page to see progress.

Wait for Active. Waiting for DNS means ownership or CNAME routing has not passed. Waiting for secure connection means hosting or the HTTPS certificate is still being prepared. Setup needs attention means read the displayed message and contact support if it describes a hosting issue. Certificate issuance can take several checks; repeated clicks do not make it faster.

Click Use as default after activation. Open your survey → Collect, copy a new sharing link or download a new QR code, and test it before sending it to respondents. Previously distributed Arynox links still work; existing printed QR codes are not rewritten.

Keep both DNS records in place. Set the Active/Disabled switch to Disabled to block the custom address immediately. New links use the platform address. Enable it again, verify, and select Use as default. Delete disables the address immediately and queues hosting cleanup; existing links and QR codes stop working. Your surveys and responses are retained, and you can share the original Arynox address.

Open Integrations → API keys to see your current access, monthly usage, requests per minute and available permissions. Limits are shared across all workspace keys.

Create a named key with only the permissions your integration needs and an expiry of 1–365 days. Copy it immediately. A key cannot grant permissions its creator does not have; later role or plan restrictions also apply.

Send GET to https://YOUR-ARYNOX-HOST/api.php?v=1&path=workspaces with Authorization: Bearer YOUR_KEY. This requires workspace.read. Then GET path=surveys with surveys.read.

Use limit (1–100) and offset for lists. Follow pagination.next_offset until it is null. Use a separate key for each integration so it can be revoked independently.

Download the OpenAPI specification from the Developer Centre. Review recent API outcomes there when troubleshooting; request logs omit keys and response bodies.

Revoke an unused key immediately. An invalid or expired key returns 401; a disabled feature or missing permission returns 403; exhausted quotas return 429.

POST path=surveys with title and workspace_id. Optional mode selects anonymous, identified or controlled_anonymous at creation. An optional definition uses the same structure as the builder.

For every POST or PATCH, send Content-Type: application/json and a unique Idempotency-Key of 8–100 letters, numbers, dots, underscores, colons or hyphens. Retry an uncertain request with the same key and identical body.

GET path=surveys/ID to read the current revision and draft. PATCH the same path with revision and a full definition or a new title. A complete definition replaces the draft, so retain fields and translations you want to keep.

Translations, appearance and completion messages live inside the definition. Use a builder-created draft as your reference and preserve its structure; the API applies the application’s validators.

POST path=surveys/ID/publish with the latest revision and surveys.publish permission. This runs publishing checks and live-survey limits and creates a new immutable version.

POST path=surveys/ID/close with revision to stop collection. Publishing does not change the separate Test/Live collection setting; check it in Collect before sending a link to real respondents.

On 409 revision_conflict, reread the survey and reconcile changes. On 409 idempotency_conflict, do not reuse that key for a different operation.

GET path=surveys/ID/responses with responses.read. Optional from and to values are YYYY-MM-DD; version_id restricts a published version. Follow pagination.

GET path=surveys/ID/summary with reports.read for the filtered total and up to 366 most recent daily buckets. Retained test responses are included; these counts are not the billing allowance.

GET path=surveys/ID/links for the preferred branded URL and the original Arynox URL. Controlled-anonymous surveys still require individual invitations.

GET path=contacts to read contacts. POST path=contacts with email, optional name, and boolean consent/suppressed fields to create one. Consent defaults to false.

When first granting consent, supply consent_note explaining the permission. PATCH path=contacts/ID to change details. The API cannot re-enable an already suppressed contact.

GET path=usage to see effective API access and monthly consumption, or path=webhooks to inspect response-event delivery states. The latter also requires webhook access.

Apply the database upgrade through the administrator portal. Existing plans keep their original read-only API and response-webhook access. New plans default to integrations disabled until you choose otherwise.

Open Settings → Domains & integrations. Set the domain CNAME target and domain/webhook switches. The existing API platform switch remains under Portal settings.

Edit a plan and open its Features section. Configure API, custom domains, webhooks, domain allowance, per-minute/monthly API limits and permitted API operations. A domain or monthly limit of 0 means unlimited; requests per minute must be at least 1.

Open a customer organisation and find Customer integration agreement. Every feature, limit and API permission group offers Use plan setting, showing the inherited value. Choose Custom limit to enter an individual allowance, or Custom permissions to choose operations.

Review Effective access after saving. Disabling API access blocks existing keys; disabling domains prevents their respondent routing. Configurations remain stored. Lower domain limits retain access only for the earliest registered domains within the new limit.

For automatic hosting, save the cPanel API server hostname, account username, relative survey public folder and API token in Settings → Domains & integrations. Test the saved connection, then enable automation. Your existing worker handles pending connections; enabling automation sets the built-in domain job to every five minutes. Manual hosting remains available.

Check the Developer Centre’s recent requests and the scheduled job history. Enterprise is a commercial agreement, not a bypass of platform switches or tenant isolation.

For a hosting move, finish pending DNS recovery first. Back up the database, files, storage and application key. Prepare the new platform DNS and HTTPS, then set Platform public URL in Domains & integrations. Blank uses the installation configuration. Update the worker path on the destination.

Save the new cPanel connection with automation off. Account home folder is optional and defaults to /home/username; Public folder is relative to that home. Test, then enable. Keep the connection-target hostname where possible and point its DNS to the new host; changing its name requires customers to update their CNAME.

Open Custom domains in the main admin menu to see all customer domains. Each row provides Active/Disabled, Verify and Delete with hostname confirmation. Platform connection configuration stays under Settings → Domains & integrations.

Both dashboards show verified, disabled, pending, attention and cleanup counts. Customer dashboards show only their own domains. Deleting a customer organisation queues its domain cleanup even after its access is suspended. Deleting an individual team member does not remove domains belonging to a still-owned organisation.