DealMakerAPI 0.107.4 → 0.107.5

Sign up to get free protection for your applications and to get access to all the features.
checksums.yaml CHANGED
@@ -1,7 +1,7 @@
1
1
  ---
2
2
  SHA256:
3
- metadata.gz: 34b9925eaf34b265ce731c165726ddc4f8481f1b8ed7ad845ecdba9f093fd64f
4
- data.tar.gz: 8a895cf0361f1c9845fcaf4b17a5c4f351f55ab8dc10dbcfc180cb8bbcac0017
3
+ metadata.gz: 81936a41aa12b403d9a4fc4837b0c18e62dc5e7ca33fbf8815229a1350fe1208
4
+ data.tar.gz: 9ab08efc4064b469677abf99f3f1c04d94c21e8b50fb725f29d18caf96b90b9b
5
5
  SHA512:
6
- metadata.gz: ed56b378ec1ee8a408eedefd0d6e2bd26f56375aa50c25b8668a8f2b91d3fab691d63c6ed31810973a1b7349b0bd80d700f1486621ec654acc650cdaf748bd72
7
- data.tar.gz: 9a0abdf6508e5b347e2302c1d12710975f38fb78fc70c14635202307fe0a6980673aecfcb8c89dd78f01f8098888c94bcbc6526372f56a65eb4c4d23d64f6e01
6
+ metadata.gz: 8a3bf5764df07d9e449ce327fd7bacd56f053d42297b4703b95c94fd27bb6df0cac85d07780bc1a849a296a871e0b6197ca83856123cd7e427beb4e61dcddc5a
7
+ data.tar.gz: 8cd00522d99bd1ad7febfb3d279cdb90242cbdb0d9b5b050921c419aa1e42c701ff682e634902b12bd2bd0a6cb0b13337df94de7b0c89de1f3d4a56928c6b499
data/README.md CHANGED
@@ -338,7 +338,7 @@ Given the high number of updates our platform performs on any investor, we’ve
338
338
  This SDK is automatically generated by the [OpenAPI Generator](https://openapi-generator.tech) project:
339
339
 
340
340
  - API version: 1.75.0
341
- - Package version: 0.107.4
341
+ - Package version: 0.107.5
342
342
  - Generator version: 7.8.0-SNAPSHOT
343
343
  - Build package: org.openapitools.codegen.languages.RubyClientCodegen
344
344
 
@@ -355,16 +355,16 @@ gem build DealMakerAPI.gemspec
355
355
  Then either install the gem locally:
356
356
 
357
357
  ```shell
358
- gem install ./DealMakerAPI-0.107.4.gem
358
+ gem install ./DealMakerAPI-0.107.5.gem
359
359
  ```
360
360
 
361
- (for development, run `gem install --dev ./DealMakerAPI-0.107.4.gem` to install the development dependencies)
361
+ (for development, run `gem install --dev ./DealMakerAPI-0.107.5.gem` to install the development dependencies)
362
362
 
363
363
  or publish the gem to a gem hosting service, e.g. [RubyGems](https://rubygems.org/).
364
364
 
365
365
  Finally add this to the Gemfile:
366
366
 
367
- gem 'DealMakerAPI', '~> 0.107.4'
367
+ gem 'DealMakerAPI', '~> 0.107.5'
368
368
 
369
369
  ### Install from Git
370
370
 
@@ -443,10 +443,11 @@ Class | Method | HTTP request | Description
443
443
  *DealMakerAPI::DealApi* | [**create_deal_setup**](docs/DealApi.md#create_deal_setup) | **POST** /deal_setups | Create deal setup
444
444
  *DealMakerAPI::DealApi* | [**get_deal**](docs/DealApi.md#get_deal) | **GET** /deals/{id} | Get deal by Deal ID
445
445
  *DealMakerAPI::DealApi* | [**get_deal_incentive_plan**](docs/DealApi.md#get_deal_incentive_plan) | **GET** /deals/{id}/incentive_plan | Get incentive plan by deal id
446
- *DealMakerAPI::DealApi* | [**get_platform_email_page**](docs/DealApi.md#get_platform_email_page) | **GET** /deals/{id}/platform_emails/{platform_email_id}/page | Get the Page for a given Platform Email
446
+ *DealMakerAPI::DealApi* | [**get_platform_email_page**](docs/DealApi.md#get_platform_email_page) | **GET** /deals/{id}/platform_emails/{kind}/page | Get the Page for a given Platform Email
447
447
  *DealMakerAPI::DealApi* | [**list_deals**](docs/DealApi.md#list_deals) | **GET** /deals | List available deals
448
448
  *DealMakerAPI::DealApi* | [**list_platform_emails**](docs/DealApi.md#list_platform_emails) | **GET** /deals/{id}/platform_emails | Get a list of platform emails for the deal
449
449
  *DealMakerAPI::DealApi* | [**patch_platform_email**](docs/DealApi.md#patch_platform_email) | **PATCH** /deals/{id}/platform_emails/{kind}/update | Patch platform email by kind and deal.
450
+ *DealMakerAPI::DealApi* | [**patch_platform_email_page**](docs/DealApi.md#patch_platform_email_page) | **PATCH** /deals/{id}/platform_emails/{kind}/page | Create and associate a page with a platform email or update the existing page
450
451
  *DealMakerAPI::DealsApi* | [**post_deals_id_email_campaign_email_campaign_id_send_email**](docs/DealsApi.md#post_deals_id_email_campaign_email_campaign_id_send_email) | **POST** /deals/{id}/email_campaign/{email_campaign_id}/send_email | Send emails to all the investors invited to the material change campaign
451
452
  *DealMakerAPI::DealsApi* | [**put_deals_id_script_tag_environment**](docs/DealsApi.md#put_deals_id_script_tag_environment) | **PUT** /deals/{id}/script_tag_environment | Update script tag environment for the deal.
452
453
  *DealMakerAPI::DefaultApi* | [**get_deals_deal_id_payment_onboarding_questionnaire_digital_payments_connection_data**](docs/DefaultApi.md#get_deals_deal_id_payment_onboarding_questionnaire_digital_payments_connection_data) | **GET** /deals/{deal_id}/payment_onboarding/questionnaire/digital_payments_connection/data | Load data for the digital payments connection stage
@@ -554,6 +555,7 @@ Class | Method | HTTP request | Description
554
555
  - [DealMakerAPI::PatchInvestorProfilesTrusts](docs/PatchInvestorProfilesTrusts.md)
555
556
  - [DealMakerAPI::PatchInvestorProfilesTrustsTrusteesInner](docs/PatchInvestorProfilesTrustsTrusteesInner.md)
556
557
  - [DealMakerAPI::PatchInvestorRequest](docs/PatchInvestorRequest.md)
558
+ - [DealMakerAPI::PatchPlatformEmailPageRequest](docs/PatchPlatformEmailPageRequest.md)
557
559
  - [DealMakerAPI::PatchPlatformEmailRequest](docs/PatchPlatformEmailRequest.md)
558
560
  - [DealMakerAPI::PostDealIncentivePlanRequest](docs/PostDealIncentivePlanRequest.md)
559
561
  - [DealMakerAPI::PostDealsIdInvestors](docs/PostDealsIdInvestors.md)
data/docs/DealApi.md CHANGED
@@ -9,10 +9,11 @@ All URIs are relative to *http://api.dealmaker.tech*
9
9
  | [**create_deal_setup**](DealApi.md#create_deal_setup) | **POST** /deal_setups | Create deal setup |
10
10
  | [**get_deal**](DealApi.md#get_deal) | **GET** /deals/{id} | Get deal by Deal ID |
11
11
  | [**get_deal_incentive_plan**](DealApi.md#get_deal_incentive_plan) | **GET** /deals/{id}/incentive_plan | Get incentive plan by deal id |
12
- | [**get_platform_email_page**](DealApi.md#get_platform_email_page) | **GET** /deals/{id}/platform_emails/{platform_email_id}/page | Get the Page for a given Platform Email |
12
+ | [**get_platform_email_page**](DealApi.md#get_platform_email_page) | **GET** /deals/{id}/platform_emails/{kind}/page | Get the Page for a given Platform Email |
13
13
  | [**list_deals**](DealApi.md#list_deals) | **GET** /deals | List available deals |
14
14
  | [**list_platform_emails**](DealApi.md#list_platform_emails) | **GET** /deals/{id}/platform_emails | Get a list of platform emails for the deal |
15
15
  | [**patch_platform_email**](DealApi.md#patch_platform_email) | **PATCH** /deals/{id}/platform_emails/{kind}/update | Patch platform email by kind and deal. |
16
+ | [**patch_platform_email_page**](DealApi.md#patch_platform_email_page) | **PATCH** /deals/{id}/platform_emails/{kind}/page | Create and associate a page with a platform email or update the existing page |
16
17
 
17
18
 
18
19
  ## ach_bank_account_setup_intent
@@ -357,7 +358,7 @@ No authorization required
357
358
 
358
359
  ## get_platform_email_page
359
360
 
360
- > <V1EntitiesPage> get_platform_email_page(id, platform_email_id)
361
+ > <V1EntitiesPage> get_platform_email_page(id, kind)
361
362
 
362
363
  Get the Page for a given Platform Email
363
364
 
@@ -373,11 +374,11 @@ DealMakerAPI.configure do |config|end
373
374
 
374
375
  api_instance = DealMakerAPI::DealApi.new
375
376
  id = 56 # Integer | The deal id.
376
- platform_email_id = 56 # Integer | The platform email id.
377
+ kind = 'global' # String | The platform email id.
377
378
 
378
379
  begin
379
380
  # Get the Page for a given Platform Email
380
- result = api_instance.get_platform_email_page(id, platform_email_id)
381
+ result = api_instance.get_platform_email_page(id, kind)
381
382
  p result
382
383
  rescue DealMakerAPI::ApiError => e
383
384
  puts "Error when calling DealApi->get_platform_email_page: #{e}"
@@ -388,12 +389,12 @@ end
388
389
 
389
390
  This returns an Array which contains the response data, status code and headers.
390
391
 
391
- > <Array(<V1EntitiesPage>, Integer, Hash)> get_platform_email_page_with_http_info(id, platform_email_id)
392
+ > <Array(<V1EntitiesPage>, Integer, Hash)> get_platform_email_page_with_http_info(id, kind)
392
393
 
393
394
  ```ruby
394
395
  begin
395
396
  # Get the Page for a given Platform Email
396
- data, status_code, headers = api_instance.get_platform_email_page_with_http_info(id, platform_email_id)
397
+ data, status_code, headers = api_instance.get_platform_email_page_with_http_info(id, kind)
397
398
  p status_code # => 2xx
398
399
  p headers # => { ... }
399
400
  p data # => <V1EntitiesPage>
@@ -407,7 +408,7 @@ end
407
408
  | Name | Type | Description | Notes |
408
409
  | ---- | ---- | ----------- | ----- |
409
410
  | **id** | **Integer** | The deal id. | |
410
- | **platform_email_id** | **Integer** | The platform email id. | |
411
+ | **kind** | **String** | The platform email id. | |
411
412
 
412
413
  ### Return type
413
414
 
@@ -630,3 +631,75 @@ No authorization required
630
631
  - **Content-Type**: application/json
631
632
  - **Accept**: application/json
632
633
 
634
+
635
+ ## patch_platform_email_page
636
+
637
+ > <V1EntitiesPage> patch_platform_email_page(id, kind, opts)
638
+
639
+ Create and associate a page with a platform email or update the existing page
640
+
641
+ Create and associate a page with a platform email or update the existing page
642
+
643
+ ### Examples
644
+
645
+ ```ruby
646
+ require 'time'
647
+ require 'DealMakerAPI'
648
+ # setup authorization
649
+ DealMakerAPI.configure do |config|end
650
+
651
+ api_instance = DealMakerAPI::DealApi.new
652
+ id = 56 # Integer | The deal id.
653
+ kind = 'global' # String | The platform email id.
654
+ opts = {
655
+ patch_platform_email_page_request: DealMakerAPI::PatchPlatformEmailPageRequest.new # PatchPlatformEmailPageRequest |
656
+ }
657
+
658
+ begin
659
+ # Create and associate a page with a platform email or update the existing page
660
+ result = api_instance.patch_platform_email_page(id, kind, opts)
661
+ p result
662
+ rescue DealMakerAPI::ApiError => e
663
+ puts "Error when calling DealApi->patch_platform_email_page: #{e}"
664
+ end
665
+ ```
666
+
667
+ #### Using the patch_platform_email_page_with_http_info variant
668
+
669
+ This returns an Array which contains the response data, status code and headers.
670
+
671
+ > <Array(<V1EntitiesPage>, Integer, Hash)> patch_platform_email_page_with_http_info(id, kind, opts)
672
+
673
+ ```ruby
674
+ begin
675
+ # Create and associate a page with a platform email or update the existing page
676
+ data, status_code, headers = api_instance.patch_platform_email_page_with_http_info(id, kind, opts)
677
+ p status_code # => 2xx
678
+ p headers # => { ... }
679
+ p data # => <V1EntitiesPage>
680
+ rescue DealMakerAPI::ApiError => e
681
+ puts "Error when calling DealApi->patch_platform_email_page_with_http_info: #{e}"
682
+ end
683
+ ```
684
+
685
+ ### Parameters
686
+
687
+ | Name | Type | Description | Notes |
688
+ | ---- | ---- | ----------- | ----- |
689
+ | **id** | **Integer** | The deal id. | |
690
+ | **kind** | **String** | The platform email id. | |
691
+ | **patch_platform_email_page_request** | [**PatchPlatformEmailPageRequest**](PatchPlatformEmailPageRequest.md) | | [optional] |
692
+
693
+ ### Return type
694
+
695
+ [**V1EntitiesPage**](V1EntitiesPage.md)
696
+
697
+ ### Authorization
698
+
699
+ No authorization required
700
+
701
+ ### HTTP request headers
702
+
703
+ - **Content-Type**: application/json
704
+ - **Accept**: application/json
705
+
@@ -0,0 +1,20 @@
1
+ # DealMakerAPI::PatchPlatformEmailPageRequest
2
+
3
+ ## Properties
4
+
5
+ | Name | Type | Description | Notes |
6
+ | ---- | ---- | ----------- | ----- |
7
+ | **draft_json_content** | **String** | The invitation page draft json content | [optional] |
8
+ | **name** | **String** | The name of the invitation page. | [optional] |
9
+
10
+ ## Example
11
+
12
+ ```ruby
13
+ require 'DealMakerAPI'
14
+
15
+ instance = DealMakerAPI::PatchPlatformEmailPageRequest.new(
16
+ draft_json_content: null,
17
+ name: null
18
+ )
19
+ ```
20
+
@@ -4,6 +4,8 @@
4
4
 
5
5
  | Name | Type | Description | Notes |
6
6
  | ---- | ---- | ----------- | ----- |
7
+ | **has_investments** | **Boolean** | A boolean indicating if the user has investments. | [optional] |
8
+ | **default** | [**V1EntitiesUsersContext**](V1EntitiesUsersContext.md) | | [optional] |
7
9
  | **contexts** | [**V1EntitiesUsersContext**](V1EntitiesUsersContext.md) | | [optional] |
8
10
 
9
11
  ## Example
@@ -12,6 +14,8 @@
12
14
  require 'DealMakerAPI'
13
15
 
14
16
  instance = DealMakerAPI::V1EntitiesUsersContexts.new(
17
+ has_investments: null,
18
+ default: null,
15
19
  contexts: null
16
20
  )
17
21
  ```
@@ -369,21 +369,21 @@ module DealMakerAPI
369
369
  # Get the Page for a given Platform Email
370
370
  # Get the Page for a given Platform Email
371
371
  # @param id [Integer] The deal id.
372
- # @param platform_email_id [Integer] The platform email id.
372
+ # @param kind [String] The platform email id.
373
373
  # @param [Hash] opts the optional parameters
374
374
  # @return [V1EntitiesPage]
375
- def get_platform_email_page(id, platform_email_id, opts = {})
376
- data, _status_code, _headers = get_platform_email_page_with_http_info(id, platform_email_id, opts)
375
+ def get_platform_email_page(id, kind, opts = {})
376
+ data, _status_code, _headers = get_platform_email_page_with_http_info(id, kind, opts)
377
377
  data
378
378
  end
379
379
 
380
380
  # Get the Page for a given Platform Email
381
381
  # Get the Page for a given Platform Email
382
382
  # @param id [Integer] The deal id.
383
- # @param platform_email_id [Integer] The platform email id.
383
+ # @param kind [String] The platform email id.
384
384
  # @param [Hash] opts the optional parameters
385
385
  # @return [Array<(V1EntitiesPage, Integer, Hash)>] V1EntitiesPage data, response status code and response headers
386
- def get_platform_email_page_with_http_info(id, platform_email_id, opts = {})
386
+ def get_platform_email_page_with_http_info(id, kind, opts = {})
387
387
  if @api_client.config.debugging
388
388
  @api_client.config.logger.debug 'Calling API: DealApi.get_platform_email_page ...'
389
389
  end
@@ -391,12 +391,17 @@ module DealMakerAPI
391
391
  if @api_client.config.client_side_validation && id.nil?
392
392
  fail ArgumentError, "Missing the required parameter 'id' when calling DealApi.get_platform_email_page"
393
393
  end
394
- # verify the required parameter 'platform_email_id' is set
395
- if @api_client.config.client_side_validation && platform_email_id.nil?
396
- fail ArgumentError, "Missing the required parameter 'platform_email_id' when calling DealApi.get_platform_email_page"
394
+ # verify the required parameter 'kind' is set
395
+ if @api_client.config.client_side_validation && kind.nil?
396
+ fail ArgumentError, "Missing the required parameter 'kind' when calling DealApi.get_platform_email_page"
397
+ end
398
+ # verify enum value
399
+ allowable_values = ["global", "introduction_email", "manual_email", "funnel_start_reminder", "mid_funnel_reminder", "end_of_funnel_reminder", "payment_reminder_email", "payment_failure_email", "payment_confirmation_email", "document_reminder_email", "next_steps_email", "acceptance_email", "reset_signature_or_agreement", "refund_email", "access_link", "payment_instructions", "microdeposit_email", "closing_campaign_email", "closing_opt_out_email", "material_change_email"]
400
+ if @api_client.config.client_side_validation && !allowable_values.include?(kind)
401
+ fail ArgumentError, "invalid value for \"kind\", must be one of #{allowable_values}"
397
402
  end
398
403
  # resource path
399
- local_var_path = '/deals/{id}/platform_emails/{platform_email_id}/page'.sub('{' + 'id' + '}', CGI.escape(id.to_s)).sub('{' + 'platform_email_id' + '}', CGI.escape(platform_email_id.to_s))
404
+ local_var_path = '/deals/{id}/platform_emails/{kind}/page'.sub('{' + 'id' + '}', CGI.escape(id.to_s)).sub('{' + 'kind' + '}', CGI.escape(kind.to_s))
400
405
 
401
406
  # query parameters
402
407
  query_params = opts[:query_params] || {}
@@ -643,5 +648,86 @@ module DealMakerAPI
643
648
  end
644
649
  return data, status_code, headers
645
650
  end
651
+
652
+ # Create and associate a page with a platform email or update the existing page
653
+ # Create and associate a page with a platform email or update the existing page
654
+ # @param id [Integer] The deal id.
655
+ # @param kind [String] The platform email id.
656
+ # @param [Hash] opts the optional parameters
657
+ # @option opts [PatchPlatformEmailPageRequest] :patch_platform_email_page_request
658
+ # @return [V1EntitiesPage]
659
+ def patch_platform_email_page(id, kind, opts = {})
660
+ data, _status_code, _headers = patch_platform_email_page_with_http_info(id, kind, opts)
661
+ data
662
+ end
663
+
664
+ # Create and associate a page with a platform email or update the existing page
665
+ # Create and associate a page with a platform email or update the existing page
666
+ # @param id [Integer] The deal id.
667
+ # @param kind [String] The platform email id.
668
+ # @param [Hash] opts the optional parameters
669
+ # @option opts [PatchPlatformEmailPageRequest] :patch_platform_email_page_request
670
+ # @return [Array<(V1EntitiesPage, Integer, Hash)>] V1EntitiesPage data, response status code and response headers
671
+ def patch_platform_email_page_with_http_info(id, kind, opts = {})
672
+ if @api_client.config.debugging
673
+ @api_client.config.logger.debug 'Calling API: DealApi.patch_platform_email_page ...'
674
+ end
675
+ # verify the required parameter 'id' is set
676
+ if @api_client.config.client_side_validation && id.nil?
677
+ fail ArgumentError, "Missing the required parameter 'id' when calling DealApi.patch_platform_email_page"
678
+ end
679
+ # verify the required parameter 'kind' is set
680
+ if @api_client.config.client_side_validation && kind.nil?
681
+ fail ArgumentError, "Missing the required parameter 'kind' when calling DealApi.patch_platform_email_page"
682
+ end
683
+ # verify enum value
684
+ allowable_values = ["global", "introduction_email", "manual_email", "funnel_start_reminder", "mid_funnel_reminder", "end_of_funnel_reminder", "payment_reminder_email", "payment_failure_email", "payment_confirmation_email", "document_reminder_email", "next_steps_email", "acceptance_email", "reset_signature_or_agreement", "refund_email", "access_link", "payment_instructions", "microdeposit_email", "closing_campaign_email", "closing_opt_out_email", "material_change_email"]
685
+ if @api_client.config.client_side_validation && !allowable_values.include?(kind)
686
+ fail ArgumentError, "invalid value for \"kind\", must be one of #{allowable_values}"
687
+ end
688
+ # resource path
689
+ local_var_path = '/deals/{id}/platform_emails/{kind}/page'.sub('{' + 'id' + '}', CGI.escape(id.to_s)).sub('{' + 'kind' + '}', CGI.escape(kind.to_s))
690
+
691
+ # query parameters
692
+ query_params = opts[:query_params] || {}
693
+
694
+ # header parameters
695
+ header_params = opts[:header_params] || {}
696
+ # HTTP header 'Accept' (if needed)
697
+ header_params['Accept'] = @api_client.select_header_accept(['application/json']) unless header_params['Accept']
698
+ # HTTP header 'Content-Type'
699
+ content_type = @api_client.select_header_content_type(['application/json'])
700
+ if !content_type.nil?
701
+ header_params['Content-Type'] = content_type
702
+ end
703
+
704
+ # form parameters
705
+ form_params = opts[:form_params] || {}
706
+
707
+ # http body (model)
708
+ post_body = opts[:debug_body] || @api_client.object_to_http_body(opts[:'patch_platform_email_page_request'])
709
+
710
+ # return_type
711
+ return_type = opts[:debug_return_type] || 'V1EntitiesPage'
712
+
713
+ # auth_names
714
+ auth_names = opts[:debug_auth_names] || []
715
+
716
+ new_options = opts.merge(
717
+ :operation => :"DealApi.patch_platform_email_page",
718
+ :header_params => header_params,
719
+ :query_params => query_params,
720
+ :form_params => form_params,
721
+ :body => post_body,
722
+ :auth_names => auth_names,
723
+ :return_type => return_type
724
+ )
725
+
726
+ data, status_code, headers = @api_client.call_api(:PATCH, local_var_path, new_options)
727
+ if @api_client.config.debugging
728
+ @api_client.config.logger.debug "API called: DealApi#patch_platform_email_page\nData: #{data.inspect}\nStatus code: #{status_code}\nHeaders: #{headers}"
729
+ end
730
+ return data, status_code, headers
731
+ end
646
732
  end
647
733
  end
@@ -0,0 +1,225 @@
1
+ =begin
2
+ #DealMaker API
3
+
4
+ ## 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.
5
+
6
+ The version of the OpenAPI document: 1.75.0
7
+
8
+ Generated by: https://openapi-generator.tech
9
+ Generator version: 7.8.0-SNAPSHOT
10
+
11
+ =end
12
+
13
+ require 'date'
14
+ require 'time'
15
+
16
+ module DealMakerAPI
17
+ class PatchPlatformEmailPageRequest
18
+ # The invitation page draft json content
19
+ attr_accessor :draft_json_content
20
+
21
+ # The name of the invitation page.
22
+ attr_accessor :name
23
+
24
+ # Attribute mapping from ruby-style variable name to JSON key.
25
+ def self.attribute_map
26
+ {
27
+ :'draft_json_content' => :'draft_json_content',
28
+ :'name' => :'name'
29
+ }
30
+ end
31
+
32
+ # Returns all the JSON keys this model knows about
33
+ def self.acceptable_attributes
34
+ attribute_map.values
35
+ end
36
+
37
+ # Attribute type mapping.
38
+ def self.openapi_types
39
+ {
40
+ :'draft_json_content' => :'String',
41
+ :'name' => :'String'
42
+ }
43
+ end
44
+
45
+ # List of attributes with nullable: true
46
+ def self.openapi_nullable
47
+ Set.new([
48
+ ])
49
+ end
50
+
51
+ # Initializes the object
52
+ # @param [Hash] attributes Model attributes in the form of hash
53
+ def initialize(attributes = {})
54
+ if (!attributes.is_a?(Hash))
55
+ fail ArgumentError, "The input argument (attributes) must be a hash in `DealMakerAPI::PatchPlatformEmailPageRequest` initialize method"
56
+ end
57
+
58
+ # check to see if the attribute exists and convert string to symbol for hash key
59
+ attributes = attributes.each_with_object({}) { |(k, v), h|
60
+ if (!self.class.attribute_map.key?(k.to_sym))
61
+ fail ArgumentError, "`#{k}` is not a valid attribute in `DealMakerAPI::PatchPlatformEmailPageRequest`. Please check the name to make sure it's valid. List of attributes: " + self.class.attribute_map.keys.inspect
62
+ end
63
+ h[k.to_sym] = v
64
+ }
65
+
66
+ if attributes.key?(:'draft_json_content')
67
+ self.draft_json_content = attributes[:'draft_json_content']
68
+ end
69
+
70
+ if attributes.key?(:'name')
71
+ self.name = attributes[:'name']
72
+ end
73
+ end
74
+
75
+ # Show invalid properties with the reasons. Usually used together with valid?
76
+ # @return Array for valid properties with the reasons
77
+ def list_invalid_properties
78
+ warn '[DEPRECATED] the `list_invalid_properties` method is obsolete'
79
+ invalid_properties = Array.new
80
+ invalid_properties
81
+ end
82
+
83
+ # Check to see if the all the properties in the model are valid
84
+ # @return true if the model is valid
85
+ def valid?
86
+ warn '[DEPRECATED] the `valid?` method is obsolete'
87
+ true
88
+ end
89
+
90
+ # Checks equality by comparing each attribute.
91
+ # @param [Object] Object to be compared
92
+ def ==(o)
93
+ return true if self.equal?(o)
94
+ self.class == o.class &&
95
+ draft_json_content == o.draft_json_content &&
96
+ name == o.name
97
+ end
98
+
99
+ # @see the `==` method
100
+ # @param [Object] Object to be compared
101
+ def eql?(o)
102
+ self == o
103
+ end
104
+
105
+ # Calculates hash code according to all attributes.
106
+ # @return [Integer] Hash code
107
+ def hash
108
+ [draft_json_content, name].hash
109
+ end
110
+
111
+ # Builds the object from hash
112
+ # @param [Hash] attributes Model attributes in the form of hash
113
+ # @return [Object] Returns the model itself
114
+ def self.build_from_hash(attributes)
115
+ return nil unless attributes.is_a?(Hash)
116
+ attributes = attributes.transform_keys(&:to_sym)
117
+ transformed_hash = {}
118
+ openapi_types.each_pair do |key, type|
119
+ if attributes.key?(attribute_map[key]) && attributes[attribute_map[key]].nil?
120
+ transformed_hash["#{key}"] = nil
121
+ elsif type =~ /\AArray<(.*)>/i
122
+ # check to ensure the input is an array given that the attribute
123
+ # is documented as an array but the input is not
124
+ if attributes[attribute_map[key]].is_a?(Array)
125
+ transformed_hash["#{key}"] = attributes[attribute_map[key]].map { |v| _deserialize($1, v) }
126
+ end
127
+ elsif !attributes[attribute_map[key]].nil?
128
+ transformed_hash["#{key}"] = _deserialize(type, attributes[attribute_map[key]])
129
+ end
130
+ end
131
+ new(transformed_hash)
132
+ end
133
+
134
+ # Deserializes the data based on type
135
+ # @param string type Data type
136
+ # @param string value Value to be deserialized
137
+ # @return [Object] Deserialized data
138
+ def self._deserialize(type, value)
139
+ case type.to_sym
140
+ when :Time
141
+ Time.parse(value)
142
+ when :Date
143
+ Date.parse(value)
144
+ when :String
145
+ value.to_s
146
+ when :Integer
147
+ value.to_i
148
+ when :Float
149
+ value.to_f
150
+ when :Boolean
151
+ if value.to_s =~ /\A(true|t|yes|y|1)\z/i
152
+ true
153
+ else
154
+ false
155
+ end
156
+ when :Object
157
+ # generic object (usually a Hash), return directly
158
+ value
159
+ when /\AArray<(?<inner_type>.+)>\z/
160
+ inner_type = Regexp.last_match[:inner_type]
161
+ value.map { |v| _deserialize(inner_type, v) }
162
+ when /\AHash<(?<k_type>.+?), (?<v_type>.+)>\z/
163
+ k_type = Regexp.last_match[:k_type]
164
+ v_type = Regexp.last_match[:v_type]
165
+ {}.tap do |hash|
166
+ value.each do |k, v|
167
+ hash[_deserialize(k_type, k)] = _deserialize(v_type, v)
168
+ end
169
+ end
170
+ else # model
171
+ # models (e.g. Pet) or oneOf
172
+ klass = DealMakerAPI.const_get(type)
173
+ klass.respond_to?(:openapi_any_of) || klass.respond_to?(:openapi_one_of) ? klass.build(value) : klass.build_from_hash(value)
174
+ end
175
+ end
176
+
177
+ # Returns the string representation of the object
178
+ # @return [String] String presentation of the object
179
+ def to_s
180
+ to_hash.to_s
181
+ end
182
+
183
+ # to_body is an alias to to_hash (backward compatibility)
184
+ # @return [Hash] Returns the object in the form of hash
185
+ def to_body
186
+ to_hash
187
+ end
188
+
189
+ # Returns the object in the form of hash
190
+ # @return [Hash] Returns the object in the form of hash
191
+ def to_hash
192
+ hash = {}
193
+ self.class.attribute_map.each_pair do |attr, param|
194
+ value = self.send(attr)
195
+ if value.nil?
196
+ is_nullable = self.class.openapi_nullable.include?(attr)
197
+ next if !is_nullable || (is_nullable && !instance_variable_defined?(:"@#{attr}"))
198
+ end
199
+
200
+ hash[param] = _to_hash(value)
201
+ end
202
+ hash
203
+ end
204
+
205
+ # Outputs non-array value in the form of hash
206
+ # For object, use to_hash. Otherwise, just return the value
207
+ # @param [Object] value Any valid value
208
+ # @return [Hash] Returns the value in the form of hash
209
+ def _to_hash(value)
210
+ if value.is_a?(Array)
211
+ value.compact.map { |v| _to_hash(v) }
212
+ elsif value.is_a?(Hash)
213
+ {}.tap do |hash|
214
+ value.each { |k, v| hash[k] = _to_hash(v) }
215
+ end
216
+ elsif value.respond_to? :to_hash
217
+ value.to_hash
218
+ else
219
+ value
220
+ end
221
+ end
222
+
223
+ end
224
+
225
+ end
@@ -16,11 +16,18 @@ require 'time'
16
16
  module DealMakerAPI
17
17
  # V1_Entities_Users_Contexts model
18
18
  class V1EntitiesUsersContexts
19
+ # A boolean indicating if the user has investments.
20
+ attr_accessor :has_investments
21
+
22
+ attr_accessor :default
23
+
19
24
  attr_accessor :contexts
20
25
 
21
26
  # Attribute mapping from ruby-style variable name to JSON key.
22
27
  def self.attribute_map
23
28
  {
29
+ :'has_investments' => :'hasInvestments',
30
+ :'default' => :'default',
24
31
  :'contexts' => :'contexts'
25
32
  }
26
33
  end
@@ -33,6 +40,8 @@ module DealMakerAPI
33
40
  # Attribute type mapping.
34
41
  def self.openapi_types
35
42
  {
43
+ :'has_investments' => :'Boolean',
44
+ :'default' => :'V1EntitiesUsersContext',
36
45
  :'contexts' => :'V1EntitiesUsersContext'
37
46
  }
38
47
  end
@@ -58,6 +67,14 @@ module DealMakerAPI
58
67
  h[k.to_sym] = v
59
68
  }
60
69
 
70
+ if attributes.key?(:'has_investments')
71
+ self.has_investments = attributes[:'has_investments']
72
+ end
73
+
74
+ if attributes.key?(:'default')
75
+ self.default = attributes[:'default']
76
+ end
77
+
61
78
  if attributes.key?(:'contexts')
62
79
  self.contexts = attributes[:'contexts']
63
80
  end
@@ -83,6 +100,8 @@ module DealMakerAPI
83
100
  def ==(o)
84
101
  return true if self.equal?(o)
85
102
  self.class == o.class &&
103
+ has_investments == o.has_investments &&
104
+ default == o.default &&
86
105
  contexts == o.contexts
87
106
  end
88
107
 
@@ -95,7 +114,7 @@ module DealMakerAPI
95
114
  # Calculates hash code according to all attributes.
96
115
  # @return [Integer] Hash code
97
116
  def hash
98
- [contexts].hash
117
+ [has_investments, default, contexts].hash
99
118
  end
100
119
 
101
120
  # Builds the object from hash
@@ -11,5 +11,5 @@ Generator version: 7.8.0-SNAPSHOT
11
11
  =end
12
12
 
13
13
  module DealMakerAPI
14
- VERSION = '0.107.4'
14
+ VERSION = '0.107.5'
15
15
  end
data/lib/DealMakerAPI.rb CHANGED
@@ -41,6 +41,7 @@ require 'DealMakerAPI/models/patch_investor_profiles_managed'
41
41
  require 'DealMakerAPI/models/patch_investor_profiles_trusts'
42
42
  require 'DealMakerAPI/models/patch_investor_profiles_trusts_trustees_inner'
43
43
  require 'DealMakerAPI/models/patch_investor_request'
44
+ require 'DealMakerAPI/models/patch_platform_email_page_request'
44
45
  require 'DealMakerAPI/models/patch_platform_email_request'
45
46
  require 'DealMakerAPI/models/post_deal_incentive_plan_request'
46
47
  require 'DealMakerAPI/models/post_deals_id_investors'
@@ -101,7 +101,7 @@ describe 'DealApi' do
101
101
  # Get the Page for a given Platform Email
102
102
  # Get the Page for a given Platform Email
103
103
  # @param id The deal id.
104
- # @param platform_email_id The platform email id.
104
+ # @param kind The platform email id.
105
105
  # @param [Hash] opts the optional parameters
106
106
  # @return [V1EntitiesPage]
107
107
  describe 'get_platform_email_page test' do
@@ -150,4 +150,18 @@ describe 'DealApi' do
150
150
  end
151
151
  end
152
152
 
153
+ # unit tests for patch_platform_email_page
154
+ # Create and associate a page with a platform email or update the existing page
155
+ # Create and associate a page with a platform email or update the existing page
156
+ # @param id The deal id.
157
+ # @param kind The platform email id.
158
+ # @param [Hash] opts the optional parameters
159
+ # @option opts [PatchPlatformEmailPageRequest] :patch_platform_email_page_request
160
+ # @return [V1EntitiesPage]
161
+ describe 'patch_platform_email_page test' do
162
+ it 'should work' do
163
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
164
+ end
165
+ end
166
+
153
167
  end
@@ -0,0 +1,42 @@
1
+ =begin
2
+ #DealMaker API
3
+
4
+ ## 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.
5
+
6
+ The version of the OpenAPI document: 1.75.0
7
+
8
+ Generated by: https://openapi-generator.tech
9
+ Generator version: 7.8.0-SNAPSHOT
10
+
11
+ =end
12
+
13
+ require 'spec_helper'
14
+ require 'json'
15
+ require 'date'
16
+
17
+ # Unit tests for DealMakerAPI::PatchPlatformEmailPageRequest
18
+ # Automatically generated by openapi-generator (https://openapi-generator.tech)
19
+ # Please update as you see appropriate
20
+ describe DealMakerAPI::PatchPlatformEmailPageRequest do
21
+ let(:instance) { DealMakerAPI::PatchPlatformEmailPageRequest.new }
22
+
23
+ describe 'test an instance of PatchPlatformEmailPageRequest' do
24
+ it 'should create an instance of PatchPlatformEmailPageRequest' do
25
+ # uncomment below to test the instance creation
26
+ #expect(instance).to be_instance_of(DealMakerAPI::PatchPlatformEmailPageRequest)
27
+ end
28
+ end
29
+
30
+ describe 'test attribute "draft_json_content"' do
31
+ it 'should work' do
32
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
33
+ end
34
+ end
35
+
36
+ describe 'test attribute "name"' do
37
+ it 'should work' do
38
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
39
+ end
40
+ end
41
+
42
+ end
@@ -27,6 +27,18 @@ describe DealMakerAPI::V1EntitiesUsersContexts do
27
27
  end
28
28
  end
29
29
 
30
+ describe 'test attribute "has_investments"' do
31
+ it 'should work' do
32
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
33
+ end
34
+ end
35
+
36
+ describe 'test attribute "default"' do
37
+ it 'should work' do
38
+ # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
39
+ end
40
+ end
41
+
30
42
  describe 'test attribute "contexts"' do
31
43
  it 'should work' do
32
44
  # assertion here. ref: https://rspec.info/features/3-12/rspec-expectations/built-in-matchers/
metadata CHANGED
@@ -1,14 +1,14 @@
1
1
  --- !ruby/object:Gem::Specification
2
2
  name: DealMakerAPI
3
3
  version: !ruby/object:Gem::Version
4
- version: 0.107.4
4
+ version: 0.107.5
5
5
  platform: ruby
6
6
  authors:
7
7
  - DealMaker
8
8
  autorequire:
9
9
  bindir: bin
10
10
  cert_chain: []
11
- date: 2024-07-22 00:00:00.000000000 Z
11
+ date: 2024-07-25 00:00:00.000000000 Z
12
12
  dependencies:
13
13
  - !ruby/object:Gem::Dependency
14
14
  name: typhoeus
@@ -95,6 +95,7 @@ files:
95
95
  - docs/PatchInvestorProfilesTrusts.md
96
96
  - docs/PatchInvestorProfilesTrustsTrusteesInner.md
97
97
  - docs/PatchInvestorRequest.md
98
+ - docs/PatchPlatformEmailPageRequest.md
98
99
  - docs/PatchPlatformEmailRequest.md
99
100
  - docs/PaymentsApi.md
100
101
  - docs/PostDealIncentivePlanRequest.md
@@ -275,6 +276,7 @@ files:
275
276
  - lib/DealMakerAPI/models/patch_investor_profiles_trusts.rb
276
277
  - lib/DealMakerAPI/models/patch_investor_profiles_trusts_trustees_inner.rb
277
278
  - lib/DealMakerAPI/models/patch_investor_request.rb
279
+ - lib/DealMakerAPI/models/patch_platform_email_page_request.rb
278
280
  - lib/DealMakerAPI/models/patch_platform_email_request.rb
279
281
  - lib/DealMakerAPI/models/post_deal_incentive_plan_request.rb
280
282
  - lib/DealMakerAPI/models/post_deals_id_investors.rb
@@ -443,6 +445,7 @@ files:
443
445
  - spec/models/patch_investor_profiles_trusts_spec.rb
444
446
  - spec/models/patch_investor_profiles_trusts_trustees_inner_spec.rb
445
447
  - spec/models/patch_investor_request_spec.rb
448
+ - spec/models/patch_platform_email_page_request_spec.rb
446
449
  - spec/models/patch_platform_email_request_spec.rb
447
450
  - spec/models/post_deal_incentive_plan_request_spec.rb
448
451
  - spec/models/post_deals_id_investors_spec.rb
@@ -593,171 +596,172 @@ signing_key:
593
596
  specification_version: 4
594
597
  summary: A ruby wrapper for the DealMaker API
595
598
  test_files:
599
+ - spec/api/payments_api_spec.rb
600
+ - spec/api/campaign_api_spec.rb
601
+ - spec/api/ttw_campaigns_api_spec.rb
596
602
  - spec/api/default_api_spec.rb
597
- - spec/api/shw_api_spec.rb
598
- - spec/api/user_api_spec.rb
603
+ - spec/api/custom_emails_api_spec.rb
599
604
  - spec/api/company_api_spec.rb
600
- - spec/api/upload_api_spec.rb
601
- - spec/api/investor_api_spec.rb
602
605
  - spec/api/shareholder_api_spec.rb
603
- - spec/api/users_api_spec.rb
604
- - spec/api/investor_profile_api_spec.rb
605
- - spec/api/campaign_api_spec.rb
606
- - spec/api/payments_api_spec.rb
606
+ - spec/api/user_api_spec.rb
607
607
  - spec/api/reservation_api_spec.rb
608
- - spec/api/incentive_plan_api_spec.rb
608
+ - spec/api/shw_api_spec.rb
609
+ - spec/api/investor_profile_api_spec.rb
610
+ - spec/api/deal_api_spec.rb
609
611
  - spec/api/deals_api_spec.rb
610
- - spec/api/ttw_campaigns_api_spec.rb
611
- - spec/api/custom_emails_api_spec.rb
612
+ - spec/api/incentive_plan_api_spec.rb
613
+ - spec/api/users_api_spec.rb
614
+ - spec/api/investor_api_spec.rb
615
+ - spec/api/upload_api_spec.rb
612
616
  - spec/api/country_api_spec.rb
613
- - spec/api/deal_api_spec.rb
614
- - spec/models/v1_entities_company_deals_spec.rb
615
- - spec/models/setup_sms_verification_request_spec.rb
616
617
  - spec/models/v1_entities_delete_result_spec.rb
617
- - spec/models/v1_entities_investor_profile_fields_beneficial_owner_spec.rb
618
- - spec/models/v1_entities_attachment_spec.rb
619
- - spec/models/v1_entities_users_context_spec.rb
620
- - spec/models/patch_platform_email_request_spec.rb
621
- - spec/models/v1_entities_investor_profiles_spec.rb
622
- - spec/models/v1_entities_background_check_search_spec.rb
623
- - spec/models/v1_entities_bulk_upload_spec.rb
624
- - spec/models/v1_entities_users_two_factor_channel_spec.rb
625
- - spec/models/v1_entities_shareholder_ledger_spec.rb
626
- - spec/models/v1_entities_address_spec.rb
627
- - spec/models/v1_entities_deals_incentive_plans_incentive_tier_spec.rb
628
- - spec/models/v1_entities_deals_investors_payment_acss_bank_account_setup_intent_spec.rb
629
- - spec/models/create_shareholder_action_request_spec.rb
630
- - spec/models/patch_investor_profiles_individuals_spec.rb
631
- - spec/models/v1_entities_payments_self_serve_onboarding_payout_account_details_data_spec.rb
632
- - spec/models/v1_entities_company_deal_spec.rb
633
618
  - spec/models/v1_entities_presigned_url_result_spec.rb
634
- - spec/models/v1_entities_deals_platform_email_spec.rb
635
- - spec/models/verify_sms_verification_request_spec.rb
619
+ - spec/models/v1_entities_deal_issuer_spec.rb
620
+ - spec/models/v1_entities_deals_spec.rb
621
+ - spec/models/v1_entities_addresses_spec.rb
622
+ - spec/models/v1_entities_investor_profile_owner_spec.rb
623
+ - spec/models/v1_entities_investor_profile_item_spec.rb
636
624
  - spec/models/v1_entities_bulk_upload_detail_spec.rb
637
- - spec/models/v1_entities_shareholder_spec.rb
638
- - spec/models/v1_entities_users_binding_spec.rb
639
- - spec/models/v1_entities_shareholders_spec.rb
640
- - spec/models/post_deals_id_investors_spec.rb
641
- - spec/models/patch_deal_incentive_plan_request_spec.rb
642
- - spec/models/add_document_request_spec.rb
643
- - spec/models/patch_investor_profiles_managed_spec.rb
644
- - spec/models/create_bulk_upload_request_spec.rb
645
- - spec/models/run_background_search_request_spec.rb
646
- - spec/models/v1_entities_bulk_upload_details_spec.rb
647
- - spec/models/put_webhooks_id_request_spec.rb
648
- - spec/models/v1_entities_country_spec.rb
649
- - spec/models/create_members_bulk_upload_request_spec.rb
650
- - spec/models/patch_investor_profiles_corporations_spec.rb
651
- - spec/models/v1_entities_bulk_uploads_spec.rb
652
- - spec/models/v1_entities_deal_spec.rb
653
- - spec/models/v1_entities_beefree_access_token_spec.rb
654
- - spec/models/v1_entities_payments_self_serve_onboarding_digital_payments_connection_data_spec.rb
655
- - spec/models/v1_entities_webhooks_subscription_spec.rb
656
- - spec/models/v1_entities_webhooks_subscription_deals_spec.rb
657
625
  - spec/models/create_bulk_upload_detail_request_spec.rb
658
- - spec/models/v1_entities_investor_profile_fields_provider_spec.rb
626
+ - spec/models/add_document_request_spec.rb
627
+ - spec/models/v1_entities_email_events_spec.rb
628
+ - spec/models/v1_entities_email_template_spec.rb
629
+ - spec/models/v1_entities_state_spec.rb
630
+ - spec/models/v1_entities_deal_setup_user_spec.rb
659
631
  - spec/models/post_webhooks_request_spec.rb
660
- - spec/models/v1_entities_investor_profile_joint_spec.rb
661
632
  - spec/models/patch_investor_profiles_corporations_beneficial_owners_inner_spec.rb
662
- - spec/models/v1_entities_email_template_spec.rb
663
- - spec/models/v1_entities_investor_profile_address_spec.rb
664
- - spec/models/v1_entities_investor_profile_fields_beneficiary_spec.rb
665
- - spec/models/v1_entities_deals_progress_kinds_spec.rb
666
- - spec/models/v1_entities_deals_progress_column_spec.rb
667
- - spec/models/post_investor_profiles_corporations_beneficial_owners_inner_spec.rb
668
- - spec/models/put_deals_id_investors_spec.rb
669
- - spec/models/v1_entities_dividends_spec.rb
670
- - spec/models/post_investor_profiles_corporations_spec.rb
671
- - spec/models/v1_entities_investor_profile_owner_spec.rb
672
- - spec/models/v1_entities_generic_response_spec.rb
673
- - spec/models/v1_entities_deals_progress_page_summary_spec.rb
674
- - spec/models/create_reservation_request_spec.rb
633
+ - spec/models/v1_entities_users_binding_spec.rb
675
634
  - spec/models/v1_entities_deal_investor_metrics_spec.rb
676
- - spec/models/v1_entities_webhooks_subscription_deal_spec.rb
677
- - spec/models/post_investor_profiles_joints_spec.rb
635
+ - spec/models/v1_entities_ttw_reservation_get_response_spec.rb
636
+ - spec/models/v1_entities_country_spec.rb
637
+ - spec/models/v1_entities_deal_spec.rb
638
+ - spec/models/patch_investor_profiles_individuals_spec.rb
639
+ - spec/models/update_user_password_request_spec.rb
678
640
  - spec/models/v1_entities_countries_spec.rb
679
- - spec/models/add506c_document_request_spec.rb
680
- - spec/models/v1_entities_deals_spec.rb
681
- - spec/models/v1_entities_investor_profile_fields_trustee_spec.rb
682
- - spec/models/v1_entities_deals_platform_emails_spec.rb
683
- - spec/models/patch_deals_id_platform_emails_domain_request_spec.rb
684
- - spec/models/v1_entities_investor_profile_managed_spec.rb
685
- - spec/models/v1_entities_investor_profile_id_spec.rb
686
- - spec/models/v1_entities_company_spec.rb
687
- - spec/models/v1_entities_users_contexts_spec.rb
688
- - spec/models/v1_entities_addresses_spec.rb
689
- - spec/models/v1_entities_dividend_spec.rb
690
- - spec/models/v1_entities_users_verification_resources_spec.rb
691
- - spec/models/v1_entities_investor_profile_fields_account_holder_spec.rb
692
- - spec/models/v1_entities_deal_issuer_spec.rb
693
- - spec/models/v1_entities_deal_setup_user_spec.rb
694
- - spec/models/v1_entities_deal_funding_metrics_spec.rb
641
+ - spec/models/post_deal_incentive_plan_request_spec.rb
695
642
  - spec/models/v1_entities_ttw_campaign_response_spec.rb
696
- - spec/models/v1_entities_money_entity_spec.rb
697
- - spec/models/v1_entities_deals_platform_emails_domain_settings_spec.rb
698
643
  - spec/models/v1_entities_deals_incentive_plan_spec.rb
644
+ - spec/models/v1_entities_address_spec.rb
645
+ - spec/models/patch_investor_request_spec.rb
646
+ - spec/models/v1_entities_investor_profile_joint_spec.rb
647
+ - spec/models/post_investor_profiles_joints_spec.rb
648
+ - spec/models/v1_entities_deals_investors_payment_ach_bank_account_setup_intent_spec.rb
649
+ - spec/models/v1_entities_investor_otp_access_link_spec.rb
650
+ - spec/models/v1_entities_generic_response_spec.rb
651
+ - spec/models/v1_entities_beefree_access_token_spec.rb
652
+ - spec/models/v1_entities_shareholders_tags_spec.rb
699
653
  - spec/models/v1_entities_investor_profile_fields_signing_officer_spec.rb
700
- - spec/models/v1_entities_investor_profile_trust_spec.rb
701
- - spec/models/update_user_password_request_spec.rb
654
+ - spec/models/patch_platform_email_request_spec.rb
655
+ - spec/models/verify_sms_verification_request_spec.rb
656
+ - spec/models/v1_entities_investor_profile_corporation_spec.rb
702
657
  - spec/models/v1_entities_payments_self_serve_onboarding_qualification_questionnaire_result_spec.rb
703
- - spec/models/v1_entities_investor_profile_individual_spec.rb
704
- - spec/models/patch_investor_request_spec.rb
705
- - spec/models/v1_entities_ttw_reservation_response_spec.rb
706
- - spec/models/verify_factor_request_spec.rb
707
- - spec/models/v1_entities_page_spec.rb
658
+ - spec/models/v1_entities_payments_self_serve_onboarding_payout_account_details_data_spec.rb
659
+ - spec/models/v1_entities_attachment_spec.rb
660
+ - spec/models/v1_entities_investor_profile_fields_trustee_spec.rb
661
+ - spec/models/v1_entities_deals_platform_email_spec.rb
708
662
  - spec/models/post_investor_profiles_trusts_trustees_inner_spec.rb
709
- - spec/models/v1_entities_webhooks_deal_spec.rb
710
- - spec/models/v1_entities_investor_profile_fields_corporation_spec.rb
711
- - spec/models/v1_entities_investors_spec.rb
712
- - spec/models/v1_entities_email_event_spec.rb
713
663
  - spec/models/v1_entities_payments_self_serve_onboarding_payout_account_details_result_spec.rb
714
- - spec/models/v1_entities_deal_enterprise_spec.rb
715
- - spec/models/put_deals_id_script_tag_environment_request_spec.rb
716
- - spec/models/create_deal_setup_request_spec.rb
717
- - spec/models/post_investor_profiles_individuals_spec.rb
718
- - spec/models/v1_entities_investor_spec.rb
664
+ - spec/models/v1_entities_investor_profile_id_spec.rb
665
+ - spec/models/v1_entities_user_spec.rb
666
+ - spec/models/v1_entities_investor_profile_managed_spec.rb
667
+ - spec/models/patch_investor_profiles_trusts_spec.rb
668
+ - spec/models/v1_entities_deals_incentive_plans_incentive_tier_spec.rb
669
+ - spec/models/v1_entities_investors_spec.rb
670
+ - spec/models/create_email_template_request_spec.rb
671
+ - spec/models/v1_entities_webhooks_security_token_spec.rb
672
+ - spec/models/v1_entities_shareholder_spec.rb
673
+ - spec/models/v1_entities_members_bulk_upload_spec.rb
674
+ - spec/models/v1_entities_express_wire_instruction_spec.rb
675
+ - spec/models/put_webhooks_id_request_spec.rb
676
+ - spec/models/v1_entities_webhooks_subscription_deal_spec.rb
677
+ - spec/models/add506c_document_request_spec.rb
678
+ - spec/models/v1_entities_company_deal_spec.rb
679
+ - spec/models/create_company_request_spec.rb
680
+ - spec/models/v1_entities_members_bulk_uploads_spec.rb
681
+ - spec/models/v1_entities_background_check_search_spec.rb
719
682
  - spec/models/patch_investor_profiles_joints_spec.rb
720
- - spec/models/v1_entities_investor_profile_fields_trust_spec.rb
721
- - spec/models/v1_entities_ttw_reservation_create_spec.rb
722
- - spec/models/v1_entities_email_events_spec.rb
723
- - spec/models/v1_entities_deals_price_details_spec.rb
724
- - spec/models/send_portal_invite_request_spec.rb
725
- - spec/models/v1_entities_investor_search_entities_required_fields_spec.rb
726
- - spec/models/v1_entities_deal_setup_spec.rb
727
- - spec/models/v1_entities_investor_profile_item_spec.rb
683
+ - spec/models/v1_entities_investor_profile_address_spec.rb
684
+ - spec/models/verify_factor_request_spec.rb
685
+ - spec/models/v1_entities_bulk_upload_details_spec.rb
686
+ - spec/models/post_investor_profiles_managed_spec.rb
687
+ - spec/models/v1_entities_company_deals_spec.rb
688
+ - spec/models/patch_deal_incentive_plan_request_spec.rb
689
+ - spec/models/put_deals_id_investors_spec.rb
690
+ - spec/models/post_investor_profiles_corporations_beneficial_owners_inner_spec.rb
691
+ - spec/models/v1_entities_deals_progress_kinds_spec.rb
692
+ - spec/models/post_investor_profiles_individuals_spec.rb
693
+ - spec/models/v1_entities_dividend_spec.rb
728
694
  - spec/models/v1_entities_deals_progress_page_summary_item_spec.rb
729
- - spec/models/v1_entities_webhooks_security_token_spec.rb
730
- - spec/models/create_email_template_request_spec.rb
731
- - spec/models/patch_investor_profiles_trusts_spec.rb
732
- - spec/models/v1_entities_express_wire_instructions_spec.rb
733
- - spec/models/v1_entities_state_spec.rb
695
+ - spec/models/patch_investor_profiles_corporations_spec.rb
696
+ - spec/models/v1_entities_ttw_reservation_create_spec.rb
734
697
  - spec/models/test_document_upload_email_request_spec.rb
735
- - spec/models/v1_entities_investor_user_spec.rb
736
- - spec/models/v1_entities_users_factor_spec.rb
737
- - spec/models/create_company_request_spec.rb
698
+ - spec/models/request_new_document_request_spec.rb
699
+ - spec/models/v1_entities_investor_profiles_spec.rb
700
+ - spec/models/v1_entities_users_contexts_spec.rb
701
+ - spec/models/v1_entities_money_entity_spec.rb
702
+ - spec/models/v1_entities_bulk_upload_spec.rb
703
+ - spec/models/v1_entities_investor_profile_trust_spec.rb
704
+ - spec/models/post_investor_profiles_corporations_spec.rb
705
+ - spec/models/v1_entities_users_two_factor_channels_spec.rb
706
+ - spec/models/v1_entities_investor_profile_individual_spec.rb
707
+ - spec/models/patch_investor_profiles_trusts_trustees_inner_spec.rb
708
+ - spec/models/create_bulk_upload_request_spec.rb
709
+ - spec/models/v1_entities_deals_progress_column_spec.rb
710
+ - spec/models/v1_entities_dividends_spec.rb
711
+ - spec/models/v1_entities_investor_profile_fields_corporation_spec.rb
712
+ - spec/models/v1_entities_deal_enterprise_spec.rb
713
+ - spec/models/run_background_search_request_spec.rb
714
+ - spec/models/v1_entities_deals_investors_payment_acss_bank_account_setup_intent_spec.rb
715
+ - spec/models/create_shareholder_action_request_spec.rb
716
+ - spec/models/v1_entities_deal_funding_metrics_spec.rb
717
+ - spec/models/v1_entities_webhooks_subscription_spec.rb
718
+ - spec/models/create_deal_setup_request_spec.rb
738
719
  - spec/models/v1_entities_investor_search_entities_spec.rb
739
720
  - spec/models/bulk_upload_investors_request_spec.rb
740
- - spec/models/post_investor_profiles_trusts_spec.rb
741
- - spec/models/v1_entities_ttw_campaign_list_spec.rb
742
- - spec/models/v1_entities_subscription_agreement_spec.rb
743
- - spec/models/patch_investor_profiles_trusts_trustees_inner_spec.rb
744
- - spec/models/post_deal_incentive_plan_request_spec.rb
745
- - spec/models/v1_entities_shareholders_tags_spec.rb
746
- - spec/models/v1_entities_members_bulk_upload_spec.rb
721
+ - spec/models/patch_platform_email_page_request_spec.rb
722
+ - spec/models/v1_entities_deals_progress_page_summary_spec.rb
723
+ - spec/models/post_deals_id_investors_spec.rb
724
+ - spec/models/v1_entities_payments_self_serve_onboarding_digital_payments_connection_data_spec.rb
725
+ - spec/models/v1_entities_email_event_spec.rb
726
+ - spec/models/v1_entities_shareholders_spec.rb
727
+ - spec/models/v1_entities_users_context_spec.rb
728
+ - spec/models/v1_entities_bulk_uploads_spec.rb
729
+ - spec/models/send_portal_invite_request_spec.rb
730
+ - spec/models/create_reservation_request_spec.rb
731
+ - spec/models/v1_entities_express_wire_instructions_spec.rb
747
732
  - spec/models/send_verification_code_request_spec.rb
748
- - spec/models/request_new_document_request_spec.rb
749
- - spec/models/v1_entities_investor_profile_corporation_spec.rb
750
- - spec/models/v1_entities_members_bulk_uploads_spec.rb
751
- - spec/models/generate_url_request_spec.rb
752
- - spec/models/v1_entities_ttw_reservation_get_response_spec.rb
753
- - spec/models/v1_entities_deals_investors_payment_ach_bank_account_setup_intent_spec.rb
754
- - spec/models/v1_entities_investor_otp_access_link_spec.rb
755
- - spec/models/get_access_token_request_spec.rb
733
+ - spec/models/v1_entities_investor_profile_fields_beneficiary_spec.rb
734
+ - spec/models/v1_entities_investor_spec.rb
735
+ - spec/models/v1_entities_deals_price_details_spec.rb
756
736
  - spec/models/v1_entities_investor_profile_fields_primary_holder_spec.rb
757
- - spec/models/post_investor_profiles_managed_spec.rb
758
- - spec/models/v1_entities_users_two_factor_channels_spec.rb
759
- - spec/models/v1_entities_deals_progress_spec.rb
760
- - spec/models/v1_entities_user_spec.rb
737
+ - spec/models/post_investor_profiles_trusts_spec.rb
738
+ - spec/models/patch_deals_id_platform_emails_domain_request_spec.rb
739
+ - spec/models/v1_entities_ttw_reservation_response_spec.rb
761
740
  - spec/models/edit_investor_tags_request_spec.rb
762
- - spec/models/v1_entities_express_wire_instruction_spec.rb
741
+ - spec/models/v1_entities_company_spec.rb
742
+ - spec/models/setup_sms_verification_request_spec.rb
743
+ - spec/models/v1_entities_deals_platform_emails_domain_settings_spec.rb
744
+ - spec/models/v1_entities_investor_user_spec.rb
745
+ - spec/models/patch_investor_profiles_managed_spec.rb
746
+ - spec/models/v1_entities_investor_profile_fields_beneficial_owner_spec.rb
747
+ - spec/models/v1_entities_subscription_agreement_spec.rb
748
+ - spec/models/v1_entities_deals_progress_spec.rb
749
+ - spec/models/v1_entities_investor_search_entities_required_fields_spec.rb
750
+ - spec/models/v1_entities_users_verification_resources_spec.rb
751
+ - spec/models/v1_entities_ttw_campaign_list_spec.rb
752
+ - spec/models/v1_entities_webhooks_deal_spec.rb
753
+ - spec/models/get_access_token_request_spec.rb
754
+ - spec/models/v1_entities_users_factor_spec.rb
755
+ - spec/models/v1_entities_deals_platform_emails_spec.rb
756
+ - spec/models/put_deals_id_script_tag_environment_request_spec.rb
757
+ - spec/models/v1_entities_users_two_factor_channel_spec.rb
758
+ - spec/models/v1_entities_deal_setup_spec.rb
759
+ - spec/models/v1_entities_investor_profile_fields_account_holder_spec.rb
760
+ - spec/models/v1_entities_shareholder_ledger_spec.rb
761
+ - spec/models/generate_url_request_spec.rb
762
+ - spec/models/v1_entities_investor_profile_fields_trust_spec.rb
763
+ - spec/models/v1_entities_page_spec.rb
764
+ - spec/models/v1_entities_webhooks_subscription_deals_spec.rb
765
+ - spec/models/v1_entities_investor_profile_fields_provider_spec.rb
766
+ - spec/models/create_members_bulk_upload_request_spec.rb
763
767
  - spec/spec_helper.rb