Documentation

Genie Snap Documentation

It's a snap!

We all deserve tools that work for us—not against us. Whether you're running a business or managing personal tasks, you need automation that's fast, flexible, affordable, and refreshingly simple.

You should be able to collect data, and payments without being locked into expensive, bloated software. You should be able to build solutions and evolve them—without watching everything collapse like a house of cards. And you should be able to do all this without draining your wallet or the planet.

Enter Genie Snap!

A quick, responsive, easy to use, and inexpensive product to automate your business and personal needs. Just like that the initial forms are generated in a snap.

This is your launchpad for effortless automation. It's quick, responsive, easy to use, and designed to keep costs—and energy consumption—low. Whether you're starting fresh or making changes, it adapts with you. From form generation to submission management, you are empowered to create client self-service flows for orders, payments, and more. No code. No chaos. Just clarity. Start with Quickstart. Build your first form. Let clients and teammates submit, pay, sign, and respond. Then review, assign, approve, reject, request more info, or reopen—all with a few clicks.

Reduce costs and complexity, and level the playing field for everyone. It's a snap.

Go to Form Wizard Documentation

Quickstart

First, use one of the three form generation services.
Second, the form opens with an editor to customize elements, appearance, lists, rules, and other parts.
Third, when finished editing, select 'Save' and the form will appear in your Dashboard Forms list.
Fourth, open the Form from Dashboard Forms, fill and submit to create a record in your Dashboard Submission list.

Guidance: The forms can also be opened from the Dashboard Submission list, links sent through email, links placed on sites and from the Portal utility.

Generate and Use Forms

Generate Form

Guidance: When each form generates, the form editor generates with it allowing human in the loop customization. The form and the form editor is always accessible from the Dashboard Forms list.

1. File-to-Form Generation

Guidance: Each 'File-to-Form' is a standard docx, doc, rtf, or pdf file that has been tagged.

Select the menu from the right-side of the drop zone for a list of predefined files.
Select the file to generate, and the form opens in a separate browser tab in Edit mode.
Or, download the file to examine how variables are applied to generate the forms.
Follow these examples creating a new file, or use a file you already have. Tag, and then drop the file into the zone to generate a form.

2. Text-to-Form Generation

Guidance: Use 'Text-to-Form' to write text directly into the input area, or type into notepad and then copy and paste into the input area.

Select the example menu to insert into the Text-to-Form input area.
Write tagged text, or write text and let the Genie automatically tag the text.
Select 'Generate Form', and the form opens in a separate browser tab in Edit mode.
Use the examples to learn how to learn how text is tagged.

Guidance:

Use predefined, edit predefined, or provide custom instructions. Do what works for you.
Form access is granted to any authenticated user and may be limited by the deployment option.

Form Deployment and Opening Options

Option 1: Open from Dashboard Forms by selecting the form's name whether active or inactive.

Option 2: Open from Dashboard New Submission Dropdown by selecting the form's name. Forms only appear in New Submission list when activated from Dashboard Forms.

Option 3: Open from Portals that have been configured from Dashboard Portals.

Option 4: Open from Email Link, or Site Link by sending the link through email or placing the link on a site for clients to select.

Form Submission Persona Modes

Persona 1: Edit Mode generates a document with edit mode watermark and will not submit a Submission to the Dashboard. This is useful for testing form interaction.

Persona 2: Unverified Email Address generates a document with unverified email watermark and will submit a Submission to the Dashboard. This lets the user know that they need to verify their email address.

Persona 3: Normal Mode and Verified Email Address generates a document without watermark and will submit a Submission to the Dashboard.

SaaS Subscription

Enter and confirm your email address to start using immediately with a free subscription. With the free subscription, host up to 20 Forms and store up to 50 Submissions. When more Forms and Submissions are needed, upgrade to a paid tier.

Guidance:

Delete unused Forms and Submissions if applicable to your business when needing to avoid upgrade.
Form and Submission limits are assessed independently. Tripping the Form limit restricts additional Forms from being added to your workspace. Tripping the Submission limit restricts any additional submissions from being saved to your workspace. If both have met their limit, then additional Forms and Submissions are restricted.
Upgrade or downgrade tiers as needed. If choosing to downgrade, keep in mind that you will not be able to add additional Forms, Submissions, or both, if your Forms or Submissions exceed your chosen tier's limit, depending on which limits are tripped. You will be able to continue to access your records, view, and perform other activities.

Free Tier: 20 Form and 50 Submission Limit.

Paid Tier $30.00 USD Per Month: 50 Forms and 500 Form Submission Storage Limit.

Paid Tier $60.00 USD Per Month: 500 Forms and 1000 Form Submission Storage Limit.

Paid Tier $120.00 USD Per Month: 1000 Form Forms and 2000 Form Submission Storage Limit.

Dedicated License

If SaaS Subscriptions do not meet your needs due to compliance, security, volume, or other factors, contact us to discuss Dedicated License eligibility. Installation on premises and dedicated cloud evironments is also available.

Annual License: Requires software download and license to install on your premises or cloud environment.

Dashboard

The Dashboard is the initial landing area for team members. When a user lands in the Dashboard, information is collated for that user. The user is then provided with a view of all related submissions, tasks, todos, and notifications. User access to the Dashboard is controlled by team membership. End user access to the forms does not require team membership, and any authenticated user can use the forms.

Menu Items down the left-side of the page allows the user to work in each of those areas.

Snapshots provide top 10 items. The remainder of the information is available by selecting that section from the menu item.

New Submission is available at the top of each page, and allows team members to submit same as clients. Forms will display in this list when activated from Dashboard Forms.

Filter Submissions is available from the top of each page. Members enter search parameters and are then navigated to the submission list.

Profile users can enter their last name, first name, and address by selecting the icon from the top right corner of the screen and select profile. Please communicate this with your team members as this will include the user's name in the lists instead of just the user's email address.

Forms

Forms are initially generated using 'Ready Made Forms', 'Generate Form From File' or 'Generate Form from Text' generation services. These services are available from the home page, or by selecting 'Generate Form' link that is located immediately above the Forms list on the Dashboard Forms page. Select the Save button from the form that was opened with the generation service to place it in Forms list. The form is then available to open and fill by using any of the following:

From the Forms list by selecting the name, whether active or inactive.

From the Submission List when the form is active.

From Link send through email or setup on a web page. Get the form's link by going to the Dashboard Forms list record, then select and get the 'Form URL'.

From Genie Snap Portal see portals section for more details. Portals can be arranged with related forms making it easy for clients to select the form that is needed.

Need More Forms

Select Generate Form and then select from 'Ready Made Forms', 'Generate Form from File' or 'Generate Form from Text' generation services. When saved, the form is added to form's list.

Need to Import a Form

Select HTML File Upload to import a form that originated from Download Form.

Form Record

Record Select Checkbox is used only for 'Bulk Delete'.

Name was entered when the form was saved or was updated from the editor by selecting . Selecting the name opens the form allowing submission whether the Form is active or inactive.

Description was applied when the form was saved or was updated from the editor by selecting Description. Use the description to provide clear meaning to your form.

Record Owner and Team is initially set to the user that generated and saved the form to their default team. The team can be changed from the editor by selecting .

Note: A Default Team, '_Default Team' is created when a user is created. The Default Team's name and description cannot be edited nor deleted, and your username cannot be deleted from the Default Team's Team Members. You can add, edit and delete additional Default Team's Team Members on your Default Team. However, you may only edit your Name and Role on the Default Team or any Team that you own.

Guidance: A Team is assigned to each Form. One Team can go across all Forms, or there could be specific Teams for one or more Forms. For example, a Finance Team may be assigned to financial type Forms. There could be departments or other groupings that are needed to associate Teams to Form types. You can always delete Teams, create other Teams, and reassign Teams to Forms. Fewer teams generally make more sense. The system also limits the maximum number of Teams to 100.

Active controls whether this form displays in 'New Submission'. Selecting active from the list will activate / deactivate as well as setting to active from within the editor .

Operations

Copy Form is used to make a copy of the form and add it to the list. The copy can then be edited to meet the new requirements.

Delete Form will remove the form from the list but does not delete submissions created from this form.

Download Form can be used in any Dashboard by selecting 'HTML File Upload' and upload into the form list.

Download Integration Contract is used to integrate and create submissions from other sources.

Edit Form opens the form in edit mode.

Edit Record is used to make changes to the Name, Description, Active status, change Team, and get the Form's link.

In-App Payments

Guidance: Any form can be setup to collect in-app payments from your clients. All that is required is for Team Owners to setup a Stripe Connected Account from their Teams Dashboard. Then set any Team connected Form to collect specific or variable amount payments. When clients submit, they are routed to Stripe Checkout to make payment. When client payments succeed, funds are deposited into the Team Owner's Stripe connected account.

First, setup Stripe Connected Account - This is to be used by the Team Owner. The user must select the Wallet icon from any Team of which they are the Team Owner. The user is then routed to Stripe's Connected Account setup - see Stripe's documentation for further instructions. Once completed, the user is routed back to the Team Dashboard to confirm.

Second, set Forms to Collect Payments - Forms are connected to Teams and therefore any Forms connected to any Team Owner's Teams are eligible to collect payment. Navigate to Forms and select Form Edit. Then go to the 2nd icon on the Form Editor's menu and select 'In App' payment:

Select 'Collect Payments From Clients'.
Enter specific amount or {{elementId}} for 'Form Charge Amount'.
Enter specific description or {{elementId}} for 'Charge Description'.
Open 'Save Edits' menu and select checkbox 'Replace existing file and make new version of file being replaced.', and then select 'Save'.

Collect Form Payment:

Client selects submit.
Stripe's payment checkout page is displayed with the 'Form Charge Amount' and 'Charge Description' displayed on Stripe checkout.
On Successful Payment funds are deposited in the Team Owner's account and the client is routed back to the HTML From.
On Cancel or Failure the payment is cancelled or abandoned depending on whether client selects back which navigates back to form, or closes the browser before completing payment.

Submissions

Submissions are generated when clients submit from a form or an integration service - see Download Integration Contract in the Forms section. When a submission is created, it is automatically set to open, and a task is created. The submission will display with 'new' in the list until that submission is selected.

The submissions are assigned to the team that the form specifies. This allows any Team Members that open the Submission List to work with the records in their view.

Submission Record

Record Select Checkbox is used for 'Bulk Download' and 'Bulk Delete'.

Form is the form from which the form submission originated.

Team is the team that the submission is assigned and this was set by the form's team membership.

Requestor the client that submitted the form.

Date Columns Open occurs when the submission is created, or when the submission is reopened. Once a submission is set to Completed, the Opened date will be empty. Pending will remove the date from In Progress. In Progress date is set for any task that is started.

Description Use to describe the submission. Select to update description.

Comments Comments are cumulative. The submission displays the last comment, and selecting from the status displays the status and comment history. Select Comment to add a comment.

Status Status is cumulative. The submission displays the last status and selecting displays the status and comment history. Status is automatically updated as actions occur.

Operations

Submission Details Work with document, attachments, and other information submitted by requestor and team members with all versions.

Open Shortcut opens the form with the most recent submission and allows updates. A version history is stored for form input data, and generated documents are stored for each submission.

Create and Manage Tasks allows team members to assign task, approval, request information, pend, close, and reopen submissions.

Reassign to Different Team allows team members to reassign the submission to a different team.

Delete Submission removes all the submission data from the system.

Tasks

Tasks are used to assign work to submissions. Tasks also display in the calendar.

Assign a submission to a team member.
Request approval from team member or client.
Request additional information from a team member or client.
Pend, open, or close a submission.
Send for signature.

Task Record

Form the type of form that the submission was created.

Description is the submission description.

Team is the team that was assigned to the submission which either defaulted to the form team or submission reassigned team.

Requestor the client that submitted or updated submission.

Created is the date the task was created.

Due is the date a user sets when creating the task.

Statement is text that is either system generated or or manually entered by the person that created the task.

Assigned is the user the task is assigned.

Completed is the date that is automatically recorded when the task is completed.

Response is a user's response that is applied using .

Operations

Submission Details Work with document, attachments, and other information submitted by requestor and team members with all versions.

Edit Task allows user to review task and update with a response.

Todo List

Todo list is used to set personal tasks. Todos also display in the calendar

Todo Record

Form the type of form that submission was created.

Description is the submission description.

Team is the team that was assigned to the submission which either defaulted to the form's team or submission reassigned team.

Requestor the client that submitted or updated submission.

Created is the date the task was created.

Due is the date a user sets when creating the task.

Statement is text that is either system generated or or manually entered by the person that created the task.

Assigned is the user the task is assigned.

Completed is the date that is automatically recorded when the task is completed.

Response is a user's response that is applied using .

Operations

Submission Details Work with document, attachments, and other information submitted by requestor and team members with all versions.

Edit Task allows user to review task and update with a response. Not available for Todo.

Open Details Work with document, attachments, and other information submitted by requestor and team members with all versions. Not available for Todo.

Notifications

Notifications are automatically set by the system when a task or todo is due or near due.

Notification Record

Created is the date the notification was created.

Due is the task or todo due date.

Status is either Due or Late.

Type is either Task or Todo.

Title is displayed for those items having a title.

Description for the Task is what is set on the response and for the Todo is the Todo's description.

Note is applied by selecting .

c:\users\allen\source\repos\richardyawn\webgenieclient\webgenieclient\genieform\htmlform.cs

Operations

Delete Notification delete the notification, but if the Task or Todo is still due, the notification will generate on next cycle.

Edit Notification review the notification and apply notes.

Edit Task go to the Task related to this notification.

Calendar

The calendar displays tasks that are assigned to you and your team, and displays the todos you have set for yourself. The calendar is accessible by selecting from the main menu, or by selecting the date located near the top right corner.

Teams

Note: A Default Team, '_Default Team' is created when a user is created. The Default Team's name and description cannot be edited nor deleted, and your username cannot be deleted from the Default Team's Team Members. You can add, edit, and delete additional Default Team's Team Members on your Default Team. However, you may only edit your Name and Role on the Default Team or any Team that you own.

Guidance: A Team is assigned to each Form. One Team can go across all Forms, or there could be more than one Team for additional Forms. For example, a Finance Team may be assigned to financial type Forms. There could be departments or other groupings that are needed as a named Team to assign to other Form types. You can always delete Teams, create other Teams, and reassign Teams to Forms; however, with a little thought, there is usually a limited number of Teams. The system also limits the maximum number of Teams to 100.

Create Team

Teams are assigned to Forms, and the Team Member permissions then provide access to the Submission, Task and Form functions. Thoroughly consider before adding a new team. When a new team is added, try to align the team's name by function or department. This way the name is easily recognized by its purpose.

Team

Each Team record displays the Name, Description, total Team Members, Date Created and Updated. The Welcome Member email may be edited along with the Name and Description on all but the Default team. Edit and Delete are only available to Team Member's with Team Manage permission and Delete is not available for Default teams.

- Transfer Owner Icon - This displays only to team owners in the top right corner of the team edit dialog.
- Name - Team name is disabled for Default teams.
- Description - Team description is disabled for Default teams.
- Welcome Member Email Subject - Email subject is used when a Team Member is added to the team. The subject is limited to 100 characters. Right-click in the subject's input area to select tags.
- Welcome Member Email Body - Email body is used when a Team Member is added to the team. The body is limited to 2000 characters. Right-click in the body's input area to select tags.

Members

Each Team may have up to 100 Team Members. Assign each Team Member's Name, Role and Permissions.

- Email Address - This is set when the member is created and cannot be edited.
- First and Last Name - Enter name each time a member is added to a team.
- Role - Role is a free-form field used to describe the member's function
- Permissions
- - Form Manage - Member can create, edit and delete Forms. Members in this role can do Form Design.
- - Form Design - Member can edit the Form's appearance, properties and behavior.
- - Team Manage - Member can create, edit and delete Teams. Members in this role can Manage Team Members
- - Team Member Manage - Member can add, edit and delete Team Members.
- - Submission Manage - Member can update, delete, perform tasks, and add notes to client form submissions.
- - Task Manage - Member can configure tasks that are used by members when working with submissions.
- - Task Assign - Member can assign tasks to submissions.
- - Billing Manage - Member can select plan and setup payment information.
- - Billing View - Member can view plan and payment information.

Transfer Team Ownership

To transfer ownership of a team from you to a team member, follow these steps:

Step 1: Select Team Member menu and Add a Team Member if one does not currently exist with the Manage Team Members permission.
Step 2: Select Edit from the Team to transfer ownership. Transfer ownership is only available from Teams where the logged-in user is the team owner.
Step 3: Select Team Transfer Icon which displays team members which have Manage Team Members permission.
Step 4: Select the member and then select Transfer.
Step 5: The selected user's role is set to 'owner' and all permission are selected. The logged-in user's role is set to 'past owner' and several of the roles are removed.
Step 6 (optional): When needed, the original owner must be manually deleted from the team members.

Portals

The Dashboard is the initial landing area for all users other than user selecting Forms from links or Forms from Portals. When a user lands in the Dashboard, information is collated for that user. The user is then provided with a view of all related submissions, tasks, todos, and notifications. The user's access is controlled by team membership.

Account Delete

From the Dashboard page, select your profile and select the 'Account Delete' option.

ACCOUNT DELETE IS UNRECOVERABLE.

Select 'Account Delete' to delete 'All' Forms, Submissions, Tasks, Notifications, Portals and Team Members for all Teams where you are the 'Team Owner'. This action also deletes all your Todo. Once this action completes, you will also be immediately signed out.

** Account Delete does not delete any data from where you are not the 'Team Owner'.

Integrations and API

Guidance: Genie Snap supports APIs for submissions, responses, and document generation.

Postman - Genie Snap API

Submissions & Responses

All forms are ready for integration and have contracts to make it easy. When integrated, the submissions land in Dashboard Submissions same as when users select the submit button on the forms. Follow these instructions to integrate submissions and responses.

Rate Limiting: Rate limit allows for 10 submissions per minute. Implement logic to respect this limit.

Authentication and Authorization:
- The Username parameter on all Submission APIs must be a member of the Form's Team from which the request has been made.
- The member's role must have 'Submission Manage' checked.
- The TUID & FUID must be obtained from the Dashboard -> Forms list page by selecting the Form's hyperlink in the Name column.
- When the Form opens, the TUID and FUID are located on the URL. Pass these values in the API requests.

New Submission

Step 1: Download the contract for the specific form from the list located at Dashboard Forms.
Step 2: Contract Provides elements and certificate to perform post.
Step 3: POST to URL endpoint https://web.geniesnap.com/WebSubmissionGenie
Step 4: Pass contract as raw body: Supply values to the form's elements listed after '_webGenieControl'. Element values are applied to record and document.
Step 5: Pass these Query parameters:
- - Username: must provide a user from that Form's Team Members.
- - Description: must provide a description up to 250 characters.
- - FUID: must match exactly what is expected on submission. FUID is obtained by selecting the 'Name' link from Dashboard Forms list and copied from the URL.
- - TUID: must match exactly what is expected on submission. TUID is obtained by selecting the 'Name' link from Dashboard Forms list and copied from the URL.
- - Operation: for a new submission, the operation parameter is 'new'.
Step 6: When the service request is successful, the submission record is created and JSON is returned.
The JSON Response:
- - FileName: the filename and extension specifying the file type.
- - Base64Content: the file contents in a base64 stream.
- - Result: the successful submission is the new submissionUniqueId.
- - Comment: is empty.
- - Payload: is empty.

Update Submission

Step 1: Download the contract for the specific form from the list located at Dashboard Forms.
Step 2: Contract Provides elements and certificate to perform post.
Step 3: POST to URL endpoint https://web.geniesnap.com/WebSubmissionGenie
Step 4: Pass contract as raw body: Supply values to the form's elements listed after '_webGenieControl'. Element values are applies to record and document.
Step 5: Pass these Query parameters:
- - Username: must provide a user from that Form's Team Members.
- - FUID: must match exactly what is expected on submission. FUID is obtained by selecting the 'Name' link from Dashboard Forms list and copied from the URL.
- - TUID: must match exactly what is expected on submission. TUID is obtained by selecting the 'Name' link from Dashboard Forms list and copied from the URL.
- - Operation: for a new submission, the operation parameter is 'update'.
- - SubmissionUniqueId: this operation parameter is the uniqueId that was generated when the submission was created.
Step 6: When the service request is successful, the submission record is created and JSON is returned.
The JSON Response:
- - FileName: the filename and extension specifying the file type.
- - Base64Content: the file contents in a base64 stream.
- - Result: the successful submission is 'updated'.
- - Comment: is empty.
- - Payload: is empty.

Delete Submission

Step 1: Download the contract for the specific form from the list located at Dashboard Forms.
Step 2: Contract Provides elements and certificate to perform post.
Step 3: POST to URL endpoint https://web.geniesnap.com/WebSubmissionGenie
Step 4: Pass contract as raw body: No values are required for the Form's elements listed after '_webGenieControl'.
Step 5: Pass these Query parameters:
- - Username: must provide a user from that Form's Team Members.
- - FUID: must match exactly what is expected on submission. FUID is obtained by selecting the 'Name' link from Dashboard Forms list and copied from the URL.
- - TUID: must match exactly what is expected on submission. TUID is obtained by selecting the 'Name' link from Dashboard Forms list and copied from the URL.
- - Operation: for a new submission, the operation parameter is 'delete'.
- - SubmissionUniqueId: this operation parameter is the uniqueId that was generated when the submission was created.
Step 6: When the service request is successful, the submission record is created and JSON is returned.
The JSON Response:
- - FileName: is empty.
- - Base64Content: is empty.
- - Result: the successful submission is 'deleted' or a message if there is a failure.
- - Comment: is empty.
- - Payload: is empty.

Retrieve Submission

Step 1: Download the contract for the specific form from the list located at Dashboard Forms.
Step 2: Contract Provides elements and certificate to perform post.
Step 3: POST to URL endpoint https://web.geniesnap.com/WebSubmissionGenie
Step 4: Pass contract as raw body: No values are required for the Form's elements listed after '_webGenieControl'.
Step 5: Pass these Query parameters:
- - Username: must provide a user from that Form's Team Members.
- - FUID: must match exactly what is expected on submission. FUID is obtained by selecting the 'Name' link from Dashboard Forms list and copied from the URL.
- - TUID: must match exactly what is expected on submission. TUID is obtained by selecting the 'Name' link from Dashboard Forms list and copied from the URL.
- - Operation: for a new submission, the operation parameter is 'retrieve'.
- - SubmissionUniqueId: this operation parameter is the uniqueId that was generated when the submission was created.
Step 6: When the service request is successful, JSON is returned.
The JSON Response:
- - FileName: the filename and extension specifying the file type.
- - Base64Content: the file contents in base64 stream.
- - Result: the successful submission is 'retrieved'.
- - Comment: JSON list of comments in base64 stream.
- - Payload: JSON data elements in base64 stream.

Retrieve Submission List

The list retrieves all submissions related to the Username's teams' associations. This means that even though the contract was downloaded for a form, the list is obtained by the team relationships.

Step 1: Download the contract for a specific form from the list located at Dashboard Forms.
Step 2: Contract Provides elements and certificate to perform post.
Step 3: POST to URL endpoint https://web.geniesnap.com/WebSubmissionGenie
Step 4: Pass contract as raw body: No values are required for the Form's elements listed after '_webGenieControl'.
Step 5: Pass these Query parameters:
- - Username: must provide a user from that Form's Team Members.
- - FUID: must match exactly what is expected on submission. FUID is obtained by selecting the 'Name' link from Dashboard Forms list and copied from the URL.
- - TUID: must match exactly what is expected on submission. TUID is obtained by selecting the 'Name' link from Dashboard Forms list and copied from the URL.
- - Operation: for retrieve, the operation parameter is 'retrievelist'.
- - StartId: The submission id to begin request.
  - StartId is 0 to get from the first submission.
  - StartId can start from any number
  - When retrieving records sets, get the last Id from the previous data set and set StartId to that value.
- - Rows: The number of submissions to retreive on each request.
- - Description: Search submissions for a specific description.
- - RequestorEmailAddress: Search submissions for a specific requestor's email address.
- - SearchFormUniqueId: Search submissions for a specific form.
- - State: Search submissions for open, closed, pend.
- - DateFrom: Search submissions from a specific date.
- - DateTo: Search submissions up to a specific date.
Step 6: When the service request is successful, a JSON list of responses with SubmissionId, FileName and Description is returned. To retrieve details, use the Retrieve Submission service.
- - FileName: this is empty.
- - Base64Content: this is empty.
- - Result: the successful submission is 'retrieved list'.
- - Comment: this is empty.
- - Payload: JSON list of submissions in base64 stream.

Document Generation

All forms are ready for integration and have contracts to make it easy. This contract can also be used solely for the purpose of document generation without creating a submission. Follow these instructions to generate documents.

Rate Limiting: Rate limit allows for 10 submissions per minute. Implement logic to respect this limit.

Authentication and Authorization:
- The Username parameter on all Submission APIs must be a member of the Form's Team from which the request has been made.
- The member's role must have 'Submission Manage' checked.
- The TUID must be obtained from the Dashboard -> Forms list page by selecting the Form's hyperlink in the Name column.
- When the Form opens, the TUID is located on the URL. Pass the value in the API requests.

Step 1: Download the contract for the specific form from the list located at Dashboard Forms.
Step 2: Contract Provides elements and certificate to perform post.
Step 3: POST to URL endpoint https://web.geniesnap.com/WebDocumentGenieGenerate
Step 4: Pass contract as raw body: Supply values to the form's elements listed after '_webGenieControl', which are the element names you'll find in the HTML page.. Element values are applied to document and no record is created.
Step 5: Pass these Query parameters:
- - Username: must provide a user from that Form's Team Members.
- - TUID: must match exactly what is expected on submission. TUID is obtained by selecting the 'Name' link from Dashboard Forms list and copied from the URL.
Step 6: When the service request is successful, the document is the service response.

Form UI Integration Button

This feature is used to bring in details from an external source, saving users from having to type everything in by hand.

At the top of each form, users can click a button to pull in external data and have it applied directly to the form's input elements. The button can be customized to use either POST or GET requests, along with variable inputs, headers, and a POST body if needed. You can also customize the mapping so that fields from the external data line up correctly with the form’s inputs by name. A built‑in test area lets you verify that the data pull works as expected before using it live.

Select Form Wizard Integration Button for details.