Roger

Roger API documentation

## 🚀 Theneo

Theneo is the quickest, simplest way to generate high-quality, interactive API docs. Just import your API collection and we'll take care of the rest.

**⚠️ Note:** All of the stated endpoints and sections are for demonstration purposes only. Theneo does not manage payments API. Get sales data, itemize payments, push orders to POS, and more.The Orders API provides a one-stop shop for integrating advanced payment functionality. You can itemize payments with custom line items or catalog objects, send orders to real Point of Sale devices to be fulfilled, and more.In addition, the Orders API allows you to look through all of a seller's previous sales and returns itemization data, customer references, and other information from POS or online transactions.

&lt;img src="https://assets.website-files.com/61f7e03934c23c1dcc9c3cd4/6306089ecc13c15fe0a7e006_Main page_2 (with visual studoi code logo) 2.svg" alt="" height="237" width="322">

### Generate API Documentation

- Build interactive API docs
- Tailor you documentation
- Create and launch quickly
- Update easily within seconds
- Built for everyone
    

# Integrations

Import your collections manually or use our integrations to automatically migrate your work from:

- Swagger
- Postman
- Github
    

[  
](https://www.theneo.io/#)

[  
](https://app.theneo.io/signup)

Drafting a contract

Finding a TemplateId

Finding a FieldId

Generating an API Key

Creating and sending contracts

Sending a contract via email

Creating a contract without sending

Webhooks

Configuration

Handling webhook requests

Support

Theneo Demo TechCrunch

Production

Sandbox

Roger provides APIs for developers to connect data and functionality with your CRM or integration tools like Zapier.

Roger provides APIs for developers to connect data and functionality with your CRM or integration tools like Zapier.

Developers can create links to the Send contract (Page) with customizations.<h2>Customizations</h2><ul><li><div>Term sheet: Pre-populate definitions of the term sheet.</div></li><li><div>Form: Pre-populate answers to</div></li></ul>

To provide a definition to pre-populate in the 

, provide the field identifier (FieldId) and definition in the following format as a query parameter in the URL:

 can be found on the by switching to the 

To specify a file to as an exhibit in the 

 section, provide the field identifier (FieldId) and a publicly accessible URL to a PDF file:

To provide an answer to pre-populate in the 

, provide the field identifier (FieldId) and answer in the following format as a query parameter in the URL:

The answer should be specified according to the type of the field:

To provide the name and/or email address to pre-populate in the 

String identifiers may be associated with a contract in the form of key-value pairs. Any key-value pairs (called 

) associated with a contract will be retained and delivered with any configured Webhook events for the contract. Use this feature if you need to store the identifier of a lead from your CRM in the contract; when you receive the 

 event, you'll be able to update the corresponding lead in your CRM.

Developers can generate API keys from the developer console. When creating the API key, the teams assigned to the API key will determine which templates are available.<div style="text-align:left"><img src="https://theneo-prod-public.s3.amazonaws.com/images-1699380258725.png" alt="" style="width:40%"/></div>In order to validate an API key send a GET request to the /apiKey endpoint. You will need to provide the API Key in the authorization

Developers can generate API keys from the developer console. When creating the API key, the teams assigned to the API key will determine which templates are available.

In order to validate an API key send a GET request to the  /apiKey endpoint. You will need to provide the API Key in the authorization 

Add your api key as the token to authorize requests.

Authorization

The Roger API allows developers the ability to create integrations that programmatically create contracts and optionally send them via email. Every Roger contract is based on a template. To create a contract, one can provide the values required by a template to the body of a request to the API. There are two options available to generate the contract, one that simply generates the contract in the Roger system and provides a URL for signing the agreement. The second option does all the aforementioned and will additionally attempt to send an email to the recipient, requesting them to sign the contract.Contracts created via the API can be viewed in the Roger UI like any other contract. You&apos;ll can filter to see the contracts created by a particular API key in the “Created by” menu in the top-right corner of the list of contracts.<div style="text-align:center"><img src="https://theneo-prod-public.s3.amazonaws.com/images-1701095538175.jpg" alt="" style="width:75%"/></div>

The Roger API allows developers the ability to create integrations that programmatically create contracts and optionally send them via email. Every Roger contract is based on a template. To create a contract, one can provide the values required by a template to the body of a request to the API. There are two options available to generate the contract, one that simply generates the contract in the Roger system and provides a URL for signing the agreement. The second option does all the aforementioned and will additionally attempt to send an email to the recipient, requesting them to sign the contract.

Contracts created via the API can be viewed in the Roger UI like any other contract. You'll can filter to see the contracts created by a particular API key in the “Created by” menu in the top-right corner of the list of contracts.

The TemplateId can be found via the instructions at <a href="https://app.theneo.io/thanksroger/roger/drafting-a-contract/finding-a-templateid" target="_blank">Finding a TemplateId</a>. The contract will be based off the template, and represents preparing the contract as a sender. To specify a value of a term&apos;s definition or prefill an answer on behalf of the recipient, use its FieldId as the key.

. The contract will be based off the template, and represents preparing the contract as a sender. To specify a value of a term's definition or prefill an answer on behalf of the recipient, use its 

Specifies that an agreement has been accepted by the signer.

templateId

Make it easier to find the agreement later.

label

These are the parts of the term sheet that you need to fill out.

definitions

exhibits

This is to prefill questions on behalf of a signer. If you desire to not prefill, use an empty string.

answers

The name of the signer if known. If you do not know what to use, use an empty string.

name

The email of the signer if known. If you do not know what to use, use an empty string.

email

The attached "terms and conditions" PDF if it should be different from the template's

attachmentUrl

senderName

The email address that the contract will be sent from.

senderEmail

customArgs

Looks up the senderEmail and sends the agreement as if it were created by that user in the UI

asUser

Content-Type

agreementId

The TemplateId can be found via the instructions at <a href="https://app.theneo.io/thanksroger/roger/drafting-a-contract/finding-a-templateid" target="_blank">Finding a TemplateId</a>. The contract will be based off the template, and represents preparing the contract as a sender. To specify a value of a term&apos;s definition or prefill an answer on behalf of the recipient, use its FieldId as the key.<div class="slate-code_line"></div>

Use webhooks to get real-time updates. Webhooks allow developers to receive an HTTP request when an agreement is signed.

Use webhooks to get real-time updates. Webhooks allow developers to receive an HTTP request when an agreement is signed.

If you have any questions, feedback, or need help with Roger APIs, please contact us at support@thanksroger.com.

If you have any questions, feedback, or need help with Roger APIs, please contact us at 