DealMakerAPI 0.75.0 → 0.79.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: fea03a9e373a10f99bb2cf454a9dd411ea3cdc4da6d63f79a513267dc9deb9b1
-  data.tar.gz: 9228ee4e38d5eadd9c53bd576192439eebbe5dbf5ad8452efcc6aa08a2048cc9
+  metadata.gz: 1a771bc931bc8c915907312de122997682ae596fcd1ec7e9fcd95e27ce830e90
+  data.tar.gz: 9fb06e035c8461a93466dcae454c7f6442bdc9754df2c99a601b3680d65aa80a
 SHA512:
-  metadata.gz: ae3f5476e0b130480897e7efd269a0bd208c87e853d106a669d2f71f730c4404561ef2b70ad5f23be54daa1788270850e6b82e97a3dabe61ac004b5c2605583c
-  data.tar.gz: 575e1ab0995a7dd2a8a3b2590929e987db997ce3d1d715130c3d2d5ba21c6f0cd3739871b6c402007554777a40c550d90f1cf67bd054c136da998bb82873c9ce
+  metadata.gz: 911ae034583934dfd23fe503f0e312fed6fef9f8d32c379ddd1cf63066a6777b6090623e5267ef2f8de074efca8130f080f848cce4f928b576125f9d06279da9
+  data.tar.gz: c9283687be7ff418c552924168c2120f25c75d902c1ec987554dd71c9498b419a63ce240541f0417e0a3b1cf09a0ce4b43cc281991118770c3ca15c6c4bfcfa1

data/DealMakerAPI.gemspec

@@ -3,12 +3,12 @@
 =begin
 #DealMaker API
 
-## Introduction  Welcome to DealMaker’s Web API v1! This API is RESTful, easy to integrate with, and offers support in 2 different languages. This is the technical documentation for our API. There are tutorials and examples of integrations with our API available on our [knowledge centre](https://help.dealmaker.tech/training-centre) as well.  # Libraries  - Javascript - Ruby  # Authentication  To authenticate, add an Authorization header to your API request that contains an access token. Before you [generate an access token](#how-to-generate-an-access-token) your must first [create an application](#create-an-application) on your portal and retrieve the your client ID and secret  ## Create an Application  DealMaker’s Web API v1 supports the use of OAuth applications. Applications can be generated in your [account](https://app.dealmaker.tech/developer/applications).  To create an API Application, click on your user name in the top right corner to open a dropdown menu, and select \"Integrations\". Under the API settings tab, click the `Create New Application` button  ![Screenshot](https://s3.ca-central-1.amazonaws.com/docs.dealmaker.tech/images/api-application-1.png)  Name your application and assign the level of permissions for this application  ![Screenshot](https://s3.ca-central-1.amazonaws.com/docs.dealmaker.tech/images/api-application-2.png)  Once your application is created, save in a secure space your client ID and secret.  **WARNING**: The secret key will not be visible after you click the close button  ![Screenshot](https://s3.ca-central-1.amazonaws.com/docs.dealmaker.tech/images/api-application-3.png)  From the developer tab, you will be able to view and manage all the available applications  ![Screenshot](https://s3.ca-central-1.amazonaws.com/docs.dealmaker.tech/images/api-application-4.png)  Each Application consists of a client id, secret and set of scopes. The scopes define what resources you want to have access to. The client ID and secret are used to generate an access token. You will need to create an application to use API endpoints.  ## How to generate an access token  After creating an application, you must make a call to obtain a bearer token using the Generate an OAuth token operation. This operation requires the following parameters:  `token endpoint` - https://app.dealmaker.tech/oauth/token  `grant_type` - must be set to `client_credentials`  `client_id` - the Client ID displayed when you created the OAuth application in the previous step  `client_secret` - the Client Secret displayed when you created the OAuth application in the previous step  `scope` - the scope is established when you created the OAuth application in the previous step  Note: The Generate an OAuth token response specifies how long the bearer token is valid for. You should reuse the bearer token until it is expired. When the token is expired, call Generate an OAuth token again to generate a new one.  To use the access token, you must set a plain text header named `Authorization` with the contents of the header being “Bearer XXX” where XXX is your generated access token.  ### Example  #### Postman  Here's an example on how to generate the access token with Postman, where `{{CLIENT_ID}}` and `{{CLIENT_SECRET}}` are the values generated after following the steps on [Create an Application](#create-an-application)  ![Get access token postman example](https://s3.ca-central-1.amazonaws.com/docs.dealmaker.tech/images/token-postman.png)  # Status Codes  ## Content-Type Header  All responses are returned in JSON format. We specify this by sending the Content-Type header.  ## Status Codes  Below is a table containing descriptions of the various status codes we currently support against various resources.  Sometimes your API call will generate an error. Here you will find additional information about what to expect if you don’t format your request properly, or we fail to properly process your request.  | Status Code | Description | | ----------- | ----------- | | `200`       | Success     | | `403`       | Forbidden   | | `404`       | Not found   |  # Pagination  Pagination is used to divide large responses is smaller portions (pages). By default, all endpoints return a maximum of 25 records per page. You can change the number of records on a per request basis by passing a `per_page` parameter in the request header parameters. The largest supported `per_page` parameter is 100.  When the response exceeds the `per_page` parameter, you can paginate through the records by increasing the `offset` parameter. Example: `offset=25` will return 25 records starting from 26th record. You may also paginate using the `page` parameter to indicate the page number you would like to show on the response.  Please review the table below for the input parameters  ## Inputs  | Parameter  | Description                                                                     | | ---------- | ------------------------------------------------------------------------------- | | `per_page` | Amount of records included on each page (Default is 25)                         | | `page`     | Page number                                                                     | | `offset`   | Amount of records offset on the API request where 0 represents the first record |  ## Response Headers  | Response Header | Description                                  | | --------------- | -------------------------------------------- | | `X-Total`       | Total number of records of response          | | `X-Total-Pages` | Total number of pages of response            | | `X-Per-Page`    | Total number of records per page of response | | `X-Page`        | Number of current page                       | | `X-Next-Page`   | Number of next page                          | | `X-Prev-Page`   | Number of previous page                      | | `X-Offset`      | Total number of records offset               |  # Search and Filtering (The q parameter)  The q optional parameter accepts a string as input and allows you to filter the request based on that string. Please note that search strings must be encoded according to ASCII. For example, \"john+investor&#64;dealmaker.tech\" should be passed as “john%2Binvestor%40dealmaker.tech”. There are two main ways to filter with it.  ## Keyword filtering  Some keywords allow you to filter investors based on a specific “scope” of the investors, for example using the string “Invited” will filter all investors with the status invited, and the keyword “Has attachments” will filter investors with attachments.  Here’s a list of possible keywords and the “scope” each one of the keywords filters by:  | Keywords                                       | Scope                                                                       | Decoded Example                                                      | Encoded Example                                                                          | | ---------------------------------------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | Signed on \\(date range\\)                       | Investors who signed in the provided date range                             | Signed on (date range) [2020-07-01:2020-07-31]                       | `Signed%20on%20%28date%20range%29%20%5B2020-07-01%3A2020-07-31%5D`                       | | Enabled for countersignature on \\(date range\\) | Investors who were enabled for counter signature in the provided date range | Enabled for countersignature on (date range) [2022-05-24:2022-05-25] | `Enabled%20for%20countersignature%20on%20(date%20range)%20%5B2022-05-24%3A2022-05-25%5D` | | Accepted on \\(date range\\)                     | Investors accepted in the provided date rage                                | Accepted on (date range) [2022-05-24:2022-05-25]                     | `Accepted%20on%20(date%20range)%20%5B2022-05-24%3A2022-05-25%5D`                         | | Offline                                        | Investors added to the deal offline                                         | Offline                                                              | `Offline`                                                                                | | Online                                         | Investors added to the deal online                                          | Online                                                               | `Online`                                                                                 | | Signed                                         | Investors who signed their agreement                                        | Signed                                                               | `Signed`                                                                                 | | Waiting for countersignature                   | Investors who have signed and are waiting for counter signature             | Waiting for countersignature                                         | `Waiting%20for%20countersignature`                                                       | | Invited                                        | Investors on the Invited Status                                             | Invited                                                              | `Invited`                                                                                | | Accepted                                       | Investors in the Accepted Status                                            | Accepted                                                             | `Accepted`                                                                               | | Questionnaire in progress                      | All Investors who have not finished completing the questionnaire            | Questionnaire in progress                                            | `Questionnaire%20in%20progress`                                                          | | Has attachments                                | All Investors with attachments                                              | Has attachments                                                      | `Has%20attachments`                                                                      | | Has notes                                      | All Investors with notes                                                    | Has notes                                                            | `Has%20notes`                                                                            | | Waiting for co-signature                       | Investors who have signed and are waiting for co-signature                  | Waiting for co-signature                                             | `Waiting%20for%20co-signature`                                                           | | Background Check Approved                      | Investors with approved background check                                    | Background Check Approved                                            | `Background%20Check%20Approved`                                                          | | Document Review Pending                        | Investors with pending review                                               | Document Review Pending                                              | `Document%20Review%20Pending`                                                            | | Document Upload Pending                        | Investors with pending documents to upload                                  | Document Upload Pending                                              | `Document%20Upload%20Pending`                                                            | | Required adjudicator review                    | Investors who are required to be review by the adjudicator                  | Required adjudicator review                                          | `Required%20adjudicator%20review`                                                        |  ---  **NOTE**  Filtering keywords are case sensitive and need to be encoded  ---  ## Search String  Any value for the parameter which does not match one of the keywords listed above, will use fields like `first name`, `last name`, `email`, `tags` to search for the investor.  For example, if you search “Robert”, because this does not match one of the keywords listed above, it will then return any investors who have the string “Robert” in their name, email, or tags fields.  # Versioning  The latest version is v1.  The version can be updated on the `Accept` header, just set the version as stated on the following example:  ```  Accept:application/vnd.dealmaker-v1+json  ```  | Version | Accept Header                       | | ------- | ----------------------------------- | | `v1`    | application/vnd.dealmaker-`v1`+json |  # SDK’s  For instruction on installing SDKs, please view the following links  - [Javascript](https://github.com/DealMakerTech/api/tree/main/v1/clients/javascript) - [Ruby](https://github.com/DealMakerTech/api/tree/main/v1/clients/ruby)  # Webhooks  Our webhooks functionality allows clients to automatically receive updates on a deal's investor data.  The type of data that the webhooks include:  - Investor Name - Date created - Email - Phone - Allocation - Attachments - Accredited investor status - Accredited investor category - Status (Draft, Invited, Accepted, Waiting)  Via webhooks clients can subscribe to the following events as they happen on Dealmaker:  - Investor is created - Investor details are updated (any of the investor details above change or are updated) - Investor is deleted  A URL supplied by the client will receive all the events with the information as part of the payload. Clients are able to add and update the URL within DealMaker.  ## Configuration  For a comprehensive guide on how to configure Webhooks please visit our support article: [Configuring Webhooks on DealMaker – DealMaker Support](https://help.dealmaker.tech/configuring-webhooks-on-dealmaker).  As a developer user on DealMaker, you are able to configure webhooks by following the steps below:  1. Sign into Dealmaker 2. Go to **“Your profile”** in the top right corner 3. Access an **“Integrations”** configuration via the left menu 4. The developer configures webhooks by including:    - The HTTPS URL where the request will be sent    - Optionally, a security token that we would use to build a SHA1 hash that would be included in the request headers. The name of the header is `X-DealMaker-Signature`. If the secret is not specified, the hash won’t be included in the headers.    - An email address that will be used to notify about errors. 5. The developers can disable webhooks temporarily if needed  ## Specification  ### Events  The initial set of events will be related to the investor. The events are:  1. `investor.created`     - Triggers every time a new investor is added to a deal  2. `investor.updated`     - Triggers on updates to any of the following fields:      1. Status      2. Name      3. Email - (this is a user field so we trigger event for all investors with webhook subscription)      4. Allocated Amount      5. Investment Amount      6. Accredited investor fields      7. Adding or removing attachments      8. Tags    - When the investor status is signed, the payload also includes a link to the signed document; the link expires after 30 minutes  3. `investor.deleted`     - Triggers when the investor is removed from the deal    - The investor key of the payload only includes investor ID    - The deal is not included in the payload. Due to our implementation it’s impossible to retrieve the deal the investor was part of  ### Requests  - The request is a `POST` - The payload’s `content-type` is `application/json` - Only `2XX` responses are considered successful. In the event of a different response, we consider it failed and queue the event for retry - We retry the request five times, after the initial attempt. Doubling the waiting time between intervals with each try. The first retry happens after 30 seconds, then 60 seconds, 2 mins, 4 minutes, and 8 minutes. This timing scheme gives the receiver about 1 hour if all the requests fail - If an event fails all the attempts to be delivered, we send an email to the address that the user configured  ### Payload  #### Common Properties  There will be some properties that are common to all the events on the system.  | Key               | Type   | Description                                                                            | | ----------------- | ------ | -------------------------------------------------------------------------------------- | | event             | String | The event that triggered the call                                                      | | event_id          | String | A unique identifier for the event                                                      | | deal<sup>\\*</sup> | Object | The deal in which the event occurred. It includes id, title, created_at and updated_at |  <sup>\\*</sup>This field is not included when deleting a resource  #### Common Properties (investor scope)  Every event on this scope must contain an investor object, here are some properties that are common to this object on all events in the investor scope:  | Key                 | Type             | Description                                                                                                              | | ------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------ | | id                  | Integer          | The unique ID of the Investor                                                                                            | | name                | String           | Investor’s Name                                                                                                          | | status              | String           | Current status of the investor<br />Possible states are: <br />draft<br />invited<br />signed<br />waiting<br />accepted | | email               | String           |                                                                                                                          | | phone_number        | String           |                                                                                                                          | | investment_amount   | Double           |                                                                                                                          | | allocated_amount    | Double           |                                                                                                                          | | accredited_investor | Object           | See format in respective ticket                                                                                          | | attachments         | Array of Objects | List of supporting documents uploaded to the investor, including URL (expire after 30 minutes) and title (caption)       | | funding_state       | String           | Investor’s current funding state (unfunded, underfunded, funded, overfunded)                                             | | funds_pending       | Boolean          | True if there are pending transactions, False otherwise                                                                  | | created_at          | Date             |                                                                                                                          | | updated_at          | Date             |                                                                                                                          | | tags                | Array of Strings | a list of the investor's tags, separated by comma.                                                                       |  ### investor.status >= signed Specific Properties  | Key                    | Type   | Description            | | ---------------------- | ------ | ---------------------- | | subscription_agreement | object | id, url (expiring URL) |  #### Investor Status  Here is a brief description of each investor state:  - **Draft:** the investor is added to the platform but hasn't been invited yet and cannot access the portal - **Invited:** the investor was added to the platform but hasn’t completed the questionnaire - **Signed:** the investor signed the document (needs approval from Lawyer or Reviewer before countersignature) - **Waiting:** the investor was approved for countersignature by any of the Lawyers or Reviewers in the deal - **Accepted:** the investor's agreement was countersigned by the Signatory  #### Update Delay  Given the high number of updates our platform performs on any investor, we’ve added a cool down period on update events that allows us to “group” updates and trigger only one every minute. In consequence, update events will be delivered 1 minute after the initial request was made and will include the latest version of the investor data at delivery time. 
+## Introduction  Welcome to DealMaker’s Web API v1! This API is RESTful, easy to integrate with, and offers support in 2 different languages. This is the technical documentation for our API. There are tutorials and examples of integrations with our API available on our [knowledge centre](https://help.dealmaker.tech/training-centre) as well.  # Libraries  - Javascript - Ruby  # Authentication  To authenticate, add an Authorization header to your API request that contains an access token. Before you [generate an access token](#how-to-generate-an-access-token) your must first [create an application](#create-an-application) on your portal and retrieve the your client ID and secret  ## Create an Application  DealMaker’s Web API v1 supports the use of OAuth applications. Applications can be generated in your [account](https://app.dealmaker.tech/developer/applications).  To create an API Application, click on your user name in the top right corner to open a dropdown menu, and select \"Integrations\". Under the API settings tab, click the `Create New Application` button  ![Screenshot](https://s3.ca-central-1.amazonaws.com/docs.dealmaker.tech/images/api-application-1.png)  Name your application and assign the level of permissions for this application  ![Screenshot](https://s3.ca-central-1.amazonaws.com/docs.dealmaker.tech/images/api-application-2.png)  Once your application is created, save in a secure space your client ID and secret.  **WARNING**: The secret key will not be visible after you click the close button  ![Screenshot](https://s3.ca-central-1.amazonaws.com/docs.dealmaker.tech/images/api-application-3.png)  From the developer tab, you will be able to view and manage all the available applications  ![Screenshot](https://s3.ca-central-1.amazonaws.com/docs.dealmaker.tech/images/api-application-4.png)  Each Application consists of a client id, secret and set of scopes. The scopes define what resources you want to have access to. The client ID and secret are used to generate an access token. You will need to create an application to use API endpoints.  ## How to generate an access token  After creating an application, you must make a call to obtain a bearer token using the Generate an OAuth token operation. This operation requires the following parameters:  `token endpoint` - https://app.dealmaker.tech/oauth/token  `grant_type` - must be set to `client_credentials`  `client_id` - the Client ID displayed when you created the OAuth application in the previous step  `client_secret` - the Client Secret displayed when you created the OAuth application in the previous step  `scope` - the scope is established when you created the OAuth application in the previous step  Note: The Generate an OAuth token response specifies how long the bearer token is valid for. You should reuse the bearer token until it is expired. When the token is expired, call Generate an OAuth token again to generate a new one.  To use the access token, you must set a plain text header named `Authorization` with the contents of the header being “Bearer XXX” where XXX is your generated access token.  ### Example  #### Postman  Here's an example on how to generate the access token with Postman, where `{{CLIENT_ID}}` and `{{CLIENT_SECRET}}` are the values generated after following the steps on [Create an Application](#create-an-application)  ![Get access token postman example](https://s3.ca-central-1.amazonaws.com/docs.dealmaker.tech/images/token-postman.png)  # Status Codes  ## Content-Type Header  All responses are returned in JSON format. We specify this by sending the Content-Type header.  ## Status Codes  Below is a table containing descriptions of the various status codes we currently support against various resources.  Sometimes your API call will generate an error. Here you will find additional information about what to expect if you don’t format your request properly, or we fail to properly process your request.  | Status Code | Description | | ----------- | ----------- | | `200`       | Success     | | `403`       | Forbidden   | | `404`       | Not found   |  # Pagination  Pagination is used to divide large responses is smaller portions (pages). By default, all endpoints return a maximum of 25 records per page. You can change the number of records on a per request basis by passing a `per_page` parameter in the request header parameters. The largest supported `per_page` parameter is 100.  When the response exceeds the `per_page` parameter, you can paginate through the records by increasing the `offset` parameter. Example: `offset=25` will return 25 records starting from 26th record. You may also paginate using the `page` parameter to indicate the page number you would like to show on the response.  Please review the table below for the input parameters  ## Inputs  | Parameter  | Description                                                                     | | ---------- | ------------------------------------------------------------------------------- | | `per_page` | Amount of records included on each page (Default is 25)                         | | `page`     | Page number                                                                     | | `offset`   | Amount of records offset on the API request where 0 represents the first record |  ## Response Headers  | Response Header | Description                                  | | --------------- | -------------------------------------------- | | `X-Total`       | Total number of records of response          | | `X-Total-Pages` | Total number of pages of response            | | `X-Per-Page`    | Total number of records per page of response | | `X-Page`        | Number of current page                       | | `X-Next-Page`   | Number of next page                          | | `X-Prev-Page`   | Number of previous page                      | | `X-Offset`      | Total number of records offset               |  # Search and Filtering (The q parameter)  The q optional parameter accepts a string as input and allows you to filter the request based on that string. Please note that search strings must be encoded according to ASCII. For example, \"john+investor&#64;dealmaker.tech\" should be passed as “john%2Binvestor%40dealmaker.tech”. There are two main ways to filter with it.  ## Keyword filtering  Some keywords allow you to filter investors based on a specific “scope” of the investors, for example using the string “Invited” will filter all investors with the status invited, and the keyword “Has attachments” will filter investors with attachments.  Here’s a list of possible keywords and the “scope” each one of the keywords filters by:  | Keywords                                       | Scope                                                                       | Decoded Example                                                      | Encoded Example                                                                          | | ---------------------------------------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- | | Signed on \\(date range\\)                       | Investors who signed in the provided date range                             | Signed on (date range) [2020-07-01:2020-07-31]                       | `Signed%20on%20%28date%20range%29%20%5B2020-07-01%3A2020-07-31%5D`                       | | Enabled for countersignature on \\(date range\\) | Investors who were enabled for counter signature in the provided date range | Enabled for countersignature on (date range) [2022-05-24:2022-05-25] | `Enabled%20for%20countersignature%20on%20(date%20range)%20%5B2022-05-24%3A2022-05-25%5D` | | Accepted on \\(date range\\)                     | Investors accepted in the provided date rage                                | Accepted on (date range) [2022-05-24:2022-05-25]                     | `Accepted%20on%20(date%20range)%20%5B2022-05-24%3A2022-05-25%5D`                         | | Offline                                        | Investors added to the deal offline                                         | Offline                                                              | `Offline`                                                                                | | Online                                         | Investors added to the deal online                                          | Online                                                               | `Online`                                                                                 | | Signed                                         | Investors who signed their agreement                                        | Signed                                                               | `Signed`                                                                                 | | Waiting for countersignature                   | Investors who have signed and are waiting for counter signature             | Waiting for countersignature                                         | `Waiting%20for%20countersignature`                                                       | | Invited                                        | Investors on the Invited Status                                             | Invited                                                              | `Invited`                                                                                | | Accepted                                       | Investors in the Accepted Status                                            | Accepted                                                             | `Accepted`                                                                               | | Questionnaire in progress                      | All Investors who have not finished completing the questionnaire            | Questionnaire in progress                                            | `Questionnaire%20in%20progress`                                                          | | Has attachments                                | All Investors with attachments                                              | Has attachments                                                      | `Has%20attachments`                                                                      | | Has notes                                      | All Investors with notes                                                    | Has notes                                                            | `Has%20notes`                                                                            | | Waiting for co-signature                       | Investors who have signed and are waiting for co-signature                  | Waiting for co-signature                                             | `Waiting%20for%20co-signature`                                                           | | Background Check Approved                      | Investors with approved background check                                    | Background Check Approved                                            | `Background%20Check%20Approved`                                                          | | Document Review Pending                        | Investors with pending review                                               | Document Review Pending                                              | `Document%20Review%20Pending`                                                            | | Document Upload Pending                        | Investors with pending documents to upload                                  | Document Upload Pending                                              | `Document%20Upload%20Pending`                                                            | | Required adjudicator review                    | Investors who are required to be review by the adjudicator                  | Required adjudicator review                                          | `Required%20adjudicator%20review`                                                        |  ---  **NOTE**  Filtering keywords are case sensitive and need to be encoded  ---  ## Search String  Any value for the parameter which does not match one of the keywords listed above, will use fields like `first name`, `last name`, `email`, `tags` to search for the investor.  For example, if you search “Robert”, because this does not match one of the keywords listed above, it will then return any investors who have the string “Robert” in their name, email, or tags fields.  # Versioning  The latest version is v1.  The version can be updated on the `Accept` header, just set the version as stated on the following example:  ```  Accept:application/vnd.dealmaker-v1+json  ```  | Version | Accept Header                       | | ------- | ----------------------------------- | | `v1`    | application/vnd.dealmaker-`v1`+json |  # SDK’s  For instruction on installing SDKs, please view the following links  - [Javascript](https://github.com/DealMakerTech/api/tree/main/v1/clients/javascript) - [Ruby](https://github.com/DealMakerTech/api/tree/main/v1/clients/ruby)  # Webhooks  Our webhooks functionality allows clients to automatically receive updates on a deal's investor data.  Some of the data that the webhooks include:  - Investor Name - Date created - Email - Phone - Allocation - Attachments - Accredited investor status - Accredited investor category - State (Draft, Invited, Signed, Accepted, Waiting, Inactive)  Via webhooks clients can subscribe to the following events as they happen on Dealmaker:  - Investor is created - Investor details are updated (any of the investor details above change or are updated) - Investor has signed their agreement - Invertor fully funded their investment - Investor has been accepted - Investor is deleted  A URL supplied by the client will receive all the events with the information as part of the payload. Clients are able to add and update the URL within DealMaker.  ## Configuration  For a comprehensive guide on how to configure Webhooks please visit our support article: [Configuring Webhooks on DealMaker – DealMaker Support](https://help.dealmaker.tech/configuring-webhooks-on-dealmaker).  As a developer user on DealMaker, you are able to configure webhooks by following the steps below:  1. Sign into Dealmaker 2. Go to **“Your profile”** in the top right corner 3. Access an **“Integrations”** configuration via the left menu 4. The developer configures webhooks by including:    - The HTTPS URL where the request will be sent    - Optionally, a security token that we would use to build a SHA1 hash that would be included in the request headers. The name of the header is `X-DealMaker-Signature`. If the secret is not specified, the hash won’t be included in the headers.    - The Deal(s) to include in the webhook subscription    - An email address that will be used to notify about errors. 5. The developers can disable webhooks temporarily if needed  ## Specification  ### Events  The initial set of events will be related to the investor. The events are:  1. `investor.created`     - Triggers every time a new investor is added to a deal  2. `investor.updated`     - Triggers on updates to any of the following fields:      - Status      - Name      - Email - (this is a user field so we trigger event for all investors with webhook subscription)      - Allocated Amount      - Investment Amount      - Accredited investor fields      - Adding or removing attachments      - Tags    - When the investor status is signed, the payload also includes a link to the signed document; the link expires after 30 minutes    3. `investor.signed`     - Triggers when the investor signs their subscription agreement (terms and conditions)      - When this happens the investor.state becomes `signed`    - This event includes the same fields as the `investor.updated` event  4. `investor.funded`     - Triggers when the investor becomes fully funded      - This happens when the investor.funded_state becomes `funded`    - This event includes the same fields as the `investor.updated` event  5. `investor.accepted`     - Triggers when the investor is countersigned      - When this happens the investor.state becomes `accepted`    - This event includes the same fields as the `investor.updated` event  6.  `investor.deleted`     - Triggers when the investor is removed from the deal    - The investor key of the payload only includes investor ID    - The deal is not included in the payload. Due to our implementation it’s impossible to retrieve the deal the investor was part of  ### Requests  - The request is a `POST` - The payload’s `content-type` is `application/json` - Only `2XX` responses are considered successful. In the event of a different response, we consider it failed and queue the event for retry - We retry the request five times, after the initial attempt. Doubling the waiting time between intervals with each try. The first retry happens after 30 seconds, then 60 seconds, 2 mins, 4 minutes, and 8 minutes. This timing scheme gives the receiver about 1 hour if all the requests fail - If an event fails all the attempts to be delivered, we send an email to the address that the user configured  ### Payload  #### Common Properties  There will be some properties that are common to all the events on the system.  | Key               | Type   | Description                                                                              | | ----------------- | ------ | --------------------------------------------------------------------------------------   | | event             | String | The event that triggered the call                                                        | | event_id          | String | A unique identifier for the event                                                        | | deal<sup>\\*</sup> | Object | The deal in which the event occurred. please see below for an example on the deal object<sup>\\*\\*</sup> |  <sup>\\*</sup>This field is not included when deleting a resource  <sup>\\*\\*</sup> Sample Deal Object in the webhook payload  ```json \"deal\": {         \"id\": 0,         \"title\": \"string\",         \"created_at\": \"2022-12-06T18:14:44.000Z\",         \"updated_at\": \"2022-12-08T12:46:48.000Z\",         \"state\": \"string\",         \"currency\": \"string\",         \"security_type\": \"string\",         \"price_per_security\": 0.00,         \"deal_type\": \"string\",         \"minimum_investment\": 0,         \"maximum_investment\": 0,         \"issuer\": {             \"id\": 0,             \"name\": \"string\"         },         \"enterprise\": {             \"id\": 0,             \"name\": \"string\"         }     } ```  #### Common Properties (investor scope)  By design, we have incorporated on the webhooks payload the same investor-related fields included in the Investor model, for reference on the included fields, their types and values please click [here](https://docs.dealmaker.tech/#tag/investor_model). This will allow you to get all the necessary information you need about a particular investor without having to call the Get Investor by ID endpoint.                                                           | #### Investor State  Here is a brief description of each investor state:  - **Draft:** the investor is added to the platform but hasn't been invited yet and cannot access the portal - **Invited:** the investor was added to the platform but hasn’t completed the questionnaire - **Signed:** the investor signed the document (needs approval from Lawyer or Reviewer before countersignature) - **Waiting:** the investor was approved for countersignature by any of the Lawyers or Reviewers in the deal - **Accepted:** the investor's agreement was countersigned by the Signatory - **Inactive** the investor is no longer eligible to participate in the offering. This may be because their warrant expired, they requested a refund, or they opted out of the offering  #### Update Delay  Given the high number of updates our platform performs on any investor, we’ve added a cool down period on update events that allows us to “group” updates and trigger only one every minute. In consequence, update events will be delivered 1 minute after the initial request was made and will include the latest version of the investor data at delivery time. 
 
 The version of the OpenAPI document: 1.0.0
 
 Generated by: https://openapi-generator.tech
-OpenAPI Generator version: 6.5.0-SNAPSHOT
+OpenAPI Generator version: 7.0.0-SNAPSHOT
 
 =end
 

data/README.md

@@ -182,7 +182,7 @@ For instruction on installing SDKs, please view the following links
 
 Our webhooks functionality allows clients to automatically receive updates on a deal's investor data.
 
-The type of data that the webhooks include:
+Some of the data that the webhooks include:
 
 - Investor Name
 - Date created
@@ -192,12 +192,15 @@ The type of data that the webhooks include:
 - Attachments
 - Accredited investor status
 - Accredited investor category
-- Status (Draft, Invited, Accepted, Waiting)
+- State (Draft, Invited, Signed, Accepted, Waiting, Inactive)
 
 Via webhooks clients can subscribe to the following events as they happen on Dealmaker:
 
 - Investor is created
 - Investor details are updated (any of the investor details above change or are updated)
+- Investor has signed their agreement
+- Invertor fully funded their investment
+- Investor has been accepted
 - Investor is deleted
 
 A URL supplied by the client will receive all the events with the information as part of the payload. Clients are able to add and update the URL within DealMaker.
@@ -214,6 +217,7 @@ As a developer user on DealMaker, you are able to configure webhooks by followin
 4. The developer configures webhooks by including:
    - The HTTPS URL where the request will be sent
    - Optionally, a security token that we would use to build a SHA1 hash that would be included in the request headers. The name of the header is `X-DealMaker-Signature`. If the secret is not specified, the hash won’t be included in the headers.
+   - The Deal(s) to include in the webhook subscription
    - An email address that will be used to notify about errors.
 5. The developers can disable webhooks temporarily if needed
 
@@ -230,17 +234,35 @@ The initial set of events will be related to the investor. The events are:
 2. `investor.updated`
 
    - Triggers on updates to any of the following fields:
-     1. Status
-     2. Name
-     3. Email - (this is a user field so we trigger event for all investors with webhook subscription)
-     4. Allocated Amount
-     5. Investment Amount
-     6. Accredited investor fields
-     7. Adding or removing attachments
-     8. Tags
+     - Status
+     - Name
+     - Email - (this is a user field so we trigger event for all investors with webhook subscription)
+     - Allocated Amount
+     - Investment Amount
+     - Accredited investor fields
+     - Adding or removing attachments
+     - Tags
    - When the investor status is signed, the payload also includes a link to the signed document; the link expires after 30 minutes
+  
+3. `investor.signed`
 
-3. `investor.deleted`
+   - Triggers when the investor signs their subscription agreement (terms and conditions)
+     - When this happens the investor.state becomes `signed`
+   - This event includes the same fields as the `investor.updated` event
+
+4. `investor.funded`
+
+   - Triggers when the investor becomes fully funded
+     - This happens when the investor.funded_state becomes `funded`
+   - This event includes the same fields as the `investor.updated` event
+
+5. `investor.accepted`
+
+   - Triggers when the investor is countersigned
+     - When this happens the investor.state becomes `accepted`
+   - This event includes the same fields as the `investor.updated` event
+
+6.  `investor.deleted`
 
    - Triggers when the investor is removed from the deal
    - The investor key of the payload only includes investor ID
@@ -260,42 +282,44 @@ The initial set of events will be related to the investor. The events are:
 
 There will be some properties that are common to all the events on the system.
 
-| Key               | Type   | Description                                                                            |
-| ----------------- | ------ | -------------------------------------------------------------------------------------- |
-| event             | String | The event that triggered the call                                                      |
-| event_id          | String | A unique identifier for the event                                                      |
-| deal<sup>\\*</sup> | Object | The deal in which the event occurred. It includes id, title, created_at and updated_at |
+| Key               | Type   | Description                                                                              |
+| ----------------- | ------ | --------------------------------------------------------------------------------------   |
+| event             | String | The event that triggered the call                                                        |
+| event_id          | String | A unique identifier for the event                                                        |
+| deal<sup>\\*</sup> | Object | The deal in which the event occurred. please see below for an example on the deal object<sup>\\*\\*</sup> |
 
 <sup>\\*</sup>This field is not included when deleting a resource
 
+<sup>\\*\\*</sup> Sample Deal Object in the webhook payload
+
+```json
+\"deal\": {
+        \"id\": 0,
+        \"title\": \"string\",
+        \"created_at\": \"2022-12-06T18:14:44.000Z\",
+        \"updated_at\": \"2022-12-08T12:46:48.000Z\",
+        \"state\": \"string\",
+        \"currency\": \"string\",
+        \"security_type\": \"string\",
+        \"price_per_security\": 0.00,
+        \"deal_type\": \"string\",
+        \"minimum_investment\": 0,
+        \"maximum_investment\": 0,
+        \"issuer\": {
+            \"id\": 0,
+            \"name\": \"string\"
+        },
+        \"enterprise\": {
+            \"id\": 0,
+            \"name\": \"string\"
+        }
+    }
+```
+
 #### Common Properties (investor scope)
 
-Every event on this scope must contain an investor object, here are some properties that are common to this object on all events in the investor scope:
-
-| Key                 | Type             | Description                                                                                                              |
-| ------------------- | ---------------- | ------------------------------------------------------------------------------------------------------------------------ |
-| id                  | Integer          | The unique ID of the Investor                                                                                            |
-| name                | String           | Investor’s Name                                                                                                          |
-| status              | String           | Current status of the investor<br />Possible states are: <br />draft<br />invited<br />signed<br />waiting<br />accepted |
-| email               | String           |                                                                                                                          |
-| phone_number        | String           |                                                                                                                          |
-| investment_amount   | Double           |                                                                                                                          |
-| allocated_amount    | Double           |                                                                                                                          |
-| accredited_investor | Object           | See format in respective ticket                                                                                          |
-| attachments         | Array of Objects | List of supporting documents uploaded to the investor, including URL (expire after 30 minutes) and title (caption)       |
-| funding_state       | String           | Investor’s current funding state (unfunded, underfunded, funded, overfunded)                                             |
-| funds_pending       | Boolean          | True if there are pending transactions, False otherwise                                                                  |
-| created_at          | Date             |                                                                                                                          |
-| updated_at          | Date             |                                                                                                                          |
-| tags                | Array of Strings | a list of the investor's tags, separated by comma.                                                                       |
-
-### investor.status >= signed Specific Properties
-
-| Key                    | Type   | Description            |
-| ---------------------- | ------ | ---------------------- |
-| subscription_agreement | object | id, url (expiring URL) |
-
-#### Investor Status
+By design, we have incorporated on the webhooks payload the same investor-related fields included in the Investor model, for reference on the included fields, their types and values please click [here](https://docs.dealmaker.tech/#tag/investor_model). This will allow you to get all the necessary information you need about a particular investor without having to call the Get Investor by ID endpoint.                                                           |
+#### Investor State
 
 Here is a brief description of each investor state:
 
@@ -304,6 +328,7 @@ Here is a brief description of each investor state:
 - **Signed:** the investor signed the document (needs approval from Lawyer or Reviewer before countersignature)
 - **Waiting:** the investor was approved for countersignature by any of the Lawyers or Reviewers in the deal
 - **Accepted:** the investor's agreement was countersigned by the Signatory
+- **Inactive** the investor is no longer eligible to participate in the offering. This may be because their warrant expired, they requested a refund, or they opted out of the offering
 
 #### Update Delay
 
@@ -313,7 +338,7 @@ Given the high number of updates our platform performs on any investor, we’ve
 This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
 
 - API version: 1.0.0
-- Package version: 0.75.0
+- Package version: 0.79.1
 - Build package: org.openapitools.codegen.languages.RubyClientCodegen
 
 ## Installation
@@ -329,16 +354,16 @@ gem build DealMakerAPI.gemspec
 Then either install the gem locally:
 
 ```shell
-gem install ./DealMakerAPI-0.75.0.gem
+gem install ./DealMakerAPI-0.79.1.gem
 ```
 
-(for development, run `gem install --dev ./DealMakerAPI-0.75.0.gem` to install the development dependencies)
+(for development, run `gem install --dev ./DealMakerAPI-0.79.1.gem` to install the development dependencies)
 
 or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
 
 Finally add this to the Gemfile:
 
-    gem 'DealMakerAPI', '~> 0.75.0'
+    gem 'DealMakerAPI', '~> 0.79.1'
 
 ### Install from Git
 
@@ -458,6 +483,7 @@ Class | Method | HTTP request | Description
  - [DealMakerAPI::V1EntitiesInvestorProfileIndividual](docs/V1EntitiesInvestorProfileIndividual.md)
  - [DealMakerAPI::V1EntitiesInvestorProfileItem](docs/V1EntitiesInvestorProfileItem.md)
  - [DealMakerAPI::V1EntitiesInvestorProfileJoint](docs/V1EntitiesInvestorProfileJoint.md)
+ - [DealMakerAPI::V1EntitiesInvestorProfileOwner](docs/V1EntitiesInvestorProfileOwner.md)
  - [DealMakerAPI::V1EntitiesInvestorProfileTrust](docs/V1EntitiesInvestorProfileTrust.md)
  - [DealMakerAPI::V1EntitiesInvestorProfiles](docs/V1EntitiesInvestorProfiles.md)
  - [DealMakerAPI::V1EntitiesInvestorUser](docs/V1EntitiesInvestorUser.md)
@@ -472,5 +498,5 @@ Class | Method | HTTP request | Description
 
 ## Documentation for Authorization
 
- All endpoints do not require authorization.
+Endpoints do not require authorization.
 

data/docs/CreateCorporationProfileRequest.md

@@ -15,6 +15,9 @@
 | **postal_code** | **String** | The postal code or zipcode of the corporation (required). | [optional] |
 | **business_number** | **String** | The taxpayer identification number  of the corporation (required). | [optional] |
 | **phone_number** | **String** | The phone number o of the corporation (required). | [optional] |
+| **income** | **Float** | The income of the individual investor profile | [optional] |
+| **net_worth** | **Float** | The net worth of the individual investor profile | [optional] |
+| **reg_cf_prior_offerings_amount** | **Float** | The prior offering amount of the individual investor profile | [optional] |
 | **signing_officer_first_name** | **String** | The first name of the signing officer (required). | [optional] |
 | **signing_officer_last_name** | **String** | The last name of the signing officer (required). | [optional] |
 | **signing_officer_suffix** | **String** | The suffix of the signing officer. | [optional] |
@@ -55,6 +58,9 @@ instance = DealMakerAPI::CreateCorporationProfileRequest.new(
   postal_code: null,
   business_number: null,
   phone_number: null,
+  income: null,
+  net_worth: null,
+  reg_cf_prior_offerings_amount: null,
   signing_officer_first_name: null,
   signing_officer_last_name: null,
   signing_officer_suffix: null,

data/docs/CreateIndividualProfileRequest.md

@@ -18,6 +18,9 @@
 | **city** | **String** | The city of the individual investor profile (required) | [optional] |
 | **region** | **String** | The region or state of the individual investor profile (required) | [optional] |
 | **postal_code** | **String** | The postal code or zipcode of the individual investor profile (required) | [optional] |
+| **income** | **Float** | The income of the individual investor profile | [optional] |
+| **net_worth** | **Float** | The net worth of the individual investor profile | [optional] |
+| **reg_cf_prior_offerings_amount** | **Float** | The prior offering amount of the individual investor profile | [optional] |
 
 ## Example
 
@@ -38,7 +41,10 @@ instance = DealMakerAPI::CreateIndividualProfileRequest.new(
   unit2: null,
   city: null,
   region: null,
-  postal_code: null
+  postal_code: null,
+  income: null,
+  net_worth: null,
+  reg_cf_prior_offerings_amount: null
 )
 ```
 

data/docs/CreateInvestorRequest.md

@@ -14,6 +14,7 @@
 | **warrant_expiry_date** | **Date** | The warrant expiry date of the investor. | [optional] |
 | **warrant_certificate_number** | **Integer** | The certificate number of the investor. | [optional] |
 | **allocated_amount** | **Float** | The allocation amount of the investor. | [optional] |
+| **investment_value** | **Float** | The investment value of the investor. | [optional] |
 | **allocation_unit** | **String** | The allocation unit of the investor. | [optional][default to 'securities'] |
 | **state** | **String** | The initial state of the investor. | [optional][default to 'invited'] |
 
@@ -33,6 +34,7 @@ instance = DealMakerAPI::CreateInvestorRequest.new(
   warrant_expiry_date: null,
   warrant_certificate_number: null,
   allocated_amount: null,
+  investment_value: null,
   allocation_unit: null,
   state: null
 )

data/docs/CreateJointProfileRequest.md

@@ -19,6 +19,9 @@
 | **date_of_birth** | **String** | The date of birth of the primary holder (required). | [optional] |
 | **taxpayer_id** | **String** | The taxpayer identification number of the primary holder (required). | [optional] |
 | **phone_number** | **String** | The phone number of the primary holder (required). | [optional] |
+| **income** | **Float** | The income of the primary holder. | [optional] |
+| **net_worth** | **Float** | The net worth of the primary holder. | [optional] |
+| **reg_cf_prior_offerings_amount** | **Float** | The prior offerings amount of the primary holder. | [optional] |
 | **joint_holder_first_name** | **String** | The first name of the joint holder (required). | [optional] |
 | **joint_holder_last_name** | **String** | The last name of the joint holder (required). | [optional] |
 | **joint_holder_suffix** | **String** | The suffix of the joint holder. | [optional] |
@@ -52,6 +55,9 @@ instance = DealMakerAPI::CreateJointProfileRequest.new(
   date_of_birth: null,
   taxpayer_id: null,
   phone_number: null,
+  income: null,
+  net_worth: null,
+  reg_cf_prior_offerings_amount: null,
   joint_holder_first_name: null,
   joint_holder_last_name: null,
   joint_holder_suffix: null,

data/docs/CreateTrustProfileRequest.md

@@ -15,6 +15,9 @@
 | **region** | **String** | The region or state of the trust (required). | [optional] |
 | **postal_code** | **String** | The postal code or zipcode of the trust (required). | [optional] |
 | **phone_number** | **String** | The phone number of the trust (required). | [optional] |
+| **income** | **Float** | The income of the trust. | [optional] |
+| **net_worth** | **Float** | The net worth of the trust. | [optional] |
+| **reg_cf_prior_offerings_amount** | **Float** | The prior offering amount of the trust. | [optional] |
 | **trustees_first_name** | **Array<String>** | The list of first names for the trustees (required for trustee 1). | [optional] |
 | **trustees_last_name** | **Array<String>** | The list of last names for the trustees (required for trustee 1). | [optional] |
 | **trustees_suffix** | **Array<String>** | The list of suffixes for the trustees. | [optional] |
@@ -44,6 +47,9 @@ instance = DealMakerAPI::CreateTrustProfileRequest.new(
   region: null,
   postal_code: null,
   phone_number: null,
+  income: null,
+  net_worth: null,
+  reg_cf_prior_offerings_amount: null,
   trustees_first_name: null,
   trustees_last_name: null,
   trustees_suffix: null,

data/docs/PatchCorporationProfileRequest.md

@@ -14,6 +14,9 @@
 | **postal_code** | **String** | Corporation postal code or zipcode. | [optional] |
 | **business_number** | **String** | The business number of the investor profile. | [optional] |
 | **phone_number** | **String** | The phone number of the investor profile. | [optional] |
+| **income** | **Float** | The income of the individual investor profile | [optional] |
+| **net_worth** | **Float** | The net worth of the individual investor profile | [optional] |
+| **reg_cf_prior_offerings_amount** | **Float** | The prior offering amount of the individual investor profile | [optional] |
 | **signing_officer_first_name** | **String** | Signing officer first name. | [optional] |
 | **signing_officer_last_name** | **String** | Signing officer last name. | [optional] |
 | **signing_officer_suffix** | **String** | Signing officer suffix. | [optional] |
@@ -42,6 +45,9 @@ instance = DealMakerAPI::PatchCorporationProfileRequest.new(
   postal_code: null,
   business_number: null,
   phone_number: null,
+  income: null,
+  net_worth: null,
+  reg_cf_prior_offerings_amount: null,
   signing_officer_first_name: null,
   signing_officer_last_name: null,
   signing_officer_suffix: null,

data/docs/PatchIndividualProfileRequest.md

@@ -17,6 +17,9 @@
 | **city** | **String** | The city of the individual investor profile. | [optional] |
 | **region** | **String** | The region or state of the individual investor profile. | [optional] |
 | **postal_code** | **String** | The postal code or zipcode of the individual investor profile. | [optional] |
+| **income** | **Float** | The income of the individual investor profile | [optional] |
+| **net_worth** | **Float** | The net worth of the individual investor profile | [optional] |
+| **reg_cf_prior_offerings_amount** | **Float** | The prior offering amount of the individual investor profile | [optional] |
 
 ## Example
 
@@ -36,7 +39,10 @@ instance = DealMakerAPI::PatchIndividualProfileRequest.new(
   unit2: null,
   city: null,
   region: null,
-  postal_code: null
+  postal_code: null,
+  income: null,
+  net_worth: null,
+  reg_cf_prior_offerings_amount: null
 )
 ```
 

data/docs/PatchJointProfileRequest.md

@@ -18,6 +18,9 @@
 | **date_of_birth** | **String** | The date of birth of the investor profile. | [optional] |
 | **taxpayer_id** | **String** | The taxpayer identification number of the investor profile. | [optional] |
 | **phone_number** | **String** | The phone number of the investor profile. | [optional] |
+| **income** | **Float** | The income of the investor profile. | [optional] |
+| **net_worth** | **Float** | The net worth of the investor profile. | [optional] |
+| **reg_cf_prior_offerings_amount** | **Float** | The prior offerings amount of the investor profile. | [optional] |
 | **joint_holder_first_name** | **String** | The joint holder first name of the investor profile. | [optional] |
 | **joint_holder_last_name** | **String** | The joint holder last name of the investor profile. | [optional] |
 | **joint_holder_suffix** | **String** | The suffix of the individual investor profile. | [optional] |
@@ -50,6 +53,9 @@ instance = DealMakerAPI::PatchJointProfileRequest.new(
   date_of_birth: null,
   taxpayer_id: null,
   phone_number: null,
+  income: null,
+  net_worth: null,
+  reg_cf_prior_offerings_amount: null,
   joint_holder_first_name: null,
   joint_holder_last_name: null,
   joint_holder_suffix: null,

data/docs/PatchTrustProfileRequest.md

@@ -14,6 +14,9 @@
 | **city** | **String** | Trust city. | [optional] |
 | **region** | **String** | Trust region or state. | [optional] |
 | **postal_code** | **String** | Trust postal code or zipcode. | [optional] |
+| **income** | **Float** | The income of the Trust. | [optional] |
+| **net_worth** | **Float** | The net worth of the Trust. | [optional] |
+| **reg_cf_prior_offerings_amount** | **Float** | The prior offering amount of the Trust. | [optional] |
 | **trustee_first_name** | **String** | Trustee first name. | [optional] |
 | **trustee_last_name** | **String** | Trustee last name. | [optional] |
 | **trustee_suffix** | **String** | Trustee suffix. | [optional] |
@@ -42,6 +45,9 @@ instance = DealMakerAPI::PatchTrustProfileRequest.new(
   city: null,
   region: null,
   postal_code: null,
+  income: null,
+  net_worth: null,
+  reg_cf_prior_offerings_amount: null,
   trustee_first_name: null,
   trustee_last_name: null,
   trustee_suffix: null,

data/docs/V1EntitiesDealFundingMetrics.md

@@ -5,6 +5,8 @@
 | Name | Type | Description | Notes |
 | ---- | ---- | ----------- | ----- |
 | **amount_subscribed** | **Float** | The amount subscribed. <br><br>This value is obtained by taking the sum of the investment amount from committed investors. Committed investors are investors with a status of `signed``, `waiting`, or `accepted`. | [optional] |
+| **funds_received** | **Float** | The amount received. | [optional] |
+| **funds_pending** | **Float** | The amount pending. | [optional] |
 | **securities_subscribed** | **Integer** | The number of securities that have been subscribed. <br><br>This value is obtained by taking the sum of the total number of securities from committed investors. Committed investors are investors with a status of `signed`, `waiting`, or `accepted`. | [optional] |
 | **amount_allocated** | **Float** | The amount allocated. <br><br>This value is obtained by taking the sum of the total allocated investment amount for investors with a status of `invited`. Allocated investment amounts are locked in and cannot be changed by the investor. | [optional] |
 | **securities_allocated** | **Integer** | The number of securities that have been allocated. <br><br>This value is obtained by taking the sum of the total allocated number of securities for investors with a status of `invited`. Allocated securities are locked in and cannot be changed by the investor. | [optional] |
@@ -18,6 +20,8 @@ require 'DealMakerAPI'
 
 instance = DealMakerAPI::V1EntitiesDealFundingMetrics.new(
   amount_subscribed: null,
+  funds_received: null,
+  funds_pending: null,
   securities_subscribed: null,
   amount_allocated: null,
   securities_allocated: null,

data/docs/V1EntitiesInvestor.md

@@ -16,8 +16,8 @@
 | **beneficial_address** | **String** | The address. | [optional] |
 | **phone_number** | **String** | The beneficial phone number associated with the investor. If there is no phone number, this returns the phone number associated with the user profile. | [optional] |
 | **investor_currency** | **String** | The investor currency. | [optional] |
-| **investment_value** | **Float** | The current investment value. | [optional] |
 | **number_of_securities** | **Integer** | The number of securities. | [optional] |
+| **investment_value** | **Float** | The current investment value. | [optional] |
 | **allocated_amount** | **Float** | The amount allocated. | [optional] |
 | **funds_value** | **Float** | The current amount that has been funded. | [optional] |
 | **access_link** | **String** | The access link for the investor. This is the access link for the specific investment, not the user. If the same user has multiple investments, each one will have a different access link. | [optional] |
@@ -50,8 +50,8 @@ instance = DealMakerAPI::V1EntitiesInvestor.new(
   beneficial_address: null,
   phone_number: null,
   investor_currency: null,
-  investment_value: null,
   number_of_securities: null,
+  investment_value: null,
   allocated_amount: null,
   funds_value: null,
   access_link: null,

data/docs/V1EntitiesInvestorProfileCorporation.md

@@ -10,6 +10,8 @@
 | **type** | **String** | Investor Profile type | [optional] |
 | **us_accredited_category** | **String** | The accredited investor information | [optional] |
 | **complete** | **Boolean** | To check if the profile is complete or not | [optional] |
+| **owner_type** | **String** | Type of the investor profile owner | [optional] |
+| **owner** | [**V1EntitiesInvestorProfileOwner**](V1EntitiesInvestorProfileOwner.md) |  | [optional] |
 | **corporation** | [**V1EntitiesInvestorProfileFieldsCorporation**](V1EntitiesInvestorProfileFieldsCorporation.md) |  | [optional] |
 | **signing_officer** | [**V1EntitiesInvestorProfileFieldsAccountHolder**](V1EntitiesInvestorProfileFieldsAccountHolder.md) |  | [optional] |
 | **beneficial_owners** | [**V1EntitiesInvestorProfileFieldsAccountHolder**](V1EntitiesInvestorProfileFieldsAccountHolder.md) |  | [optional] |
@@ -26,6 +28,8 @@ instance = DealMakerAPI::V1EntitiesInvestorProfileCorporation.new(
   type: null,
   us_accredited_category: null,
   complete: null,
+  owner_type: null,
+  owner: null,
   corporation: null,
   signing_officer: null,
   beneficial_owners: null

data/docs/V1EntitiesInvestorProfileFieldsCorporation.md

@@ -7,6 +7,9 @@
 | **name** | **String** | The corporation name | [optional] |
 | **business_number** | **String** | The corporation business number | [optional] |
 | **phone_number** | **String** | The corporation phone number | [optional] |
+| **income** | **Float** | The income | [optional] |
+| **net_worth** | **Float** | The net worth | [optional] |
+| **reg_cf_prior_offerings_amount** | **Float** | The prior offering amount in the last 12 months | [optional] |
 | **address** | [**V1EntitiesInvestorProfileAddress**](V1EntitiesInvestorProfileAddress.md) |  | [optional] |
 
 ## Example
@@ -18,6 +21,9 @@ instance = DealMakerAPI::V1EntitiesInvestorProfileFieldsCorporation.new(
   name: null,
   business_number: null,
   phone_number: null,
+  income: null,
+  net_worth: null,
+  reg_cf_prior_offerings_amount: null,
   address: null
 )
 ```

data/docs/V1EntitiesInvestorProfileFieldsPrimaryHolder.md

@@ -10,6 +10,9 @@
 | **date_of_birth** | **String** | The date of birth | [optional] |
 | **taxpayer_id** | **String** | The taxpayer identification number | [optional] |
 | **phone_number** | **String** | The phone number of the primary account holder | [optional] |
+| **income** | **Float** | The income | [optional] |
+| **net_worth** | **Float** | The net worth | [optional] |
+| **reg_cf_prior_offerings_amount** | **Float** | The prior offering amount in the last 12 months | [optional] |
 | **address** | [**V1EntitiesInvestorProfileAddress**](V1EntitiesInvestorProfileAddress.md) |  | [optional] |
 
 ## Example
@@ -24,6 +27,9 @@ instance = DealMakerAPI::V1EntitiesInvestorProfileFieldsPrimaryHolder.new(
   date_of_birth: null,
   taxpayer_id: null,
   phone_number: null,
+  income: null,
+  net_worth: null,
+  reg_cf_prior_offerings_amount: null,
   address: null
 )
 ```

data/docs/V1EntitiesInvestorProfileFieldsTrust.md

@@ -7,6 +7,9 @@
 | **name** | **String** | The name of the trust | [optional] |
 | **date** | **String** | The creation date of the trust | [optional] |
 | **phone_number** | **String** | The phone number of the trust | [optional] |
+| **income** | **Float** | The income | [optional] |
+| **net_worth** | **Float** | The net worth | [optional] |
+| **reg_cf_prior_offerings_amount** | **Float** | The prior offering amount in the last 12 months | [optional] |
 | **address** | [**V1EntitiesInvestorProfileAddress**](V1EntitiesInvestorProfileAddress.md) |  | [optional] |
 
 ## Example
@@ -18,6 +21,9 @@ instance = DealMakerAPI::V1EntitiesInvestorProfileFieldsTrust.new(
   name: null,
   date: null,
   phone_number: null,
+  income: null,
+  net_worth: null,
+  reg_cf_prior_offerings_amount: null,
   address: null
 )
 ```