-
Notifications
You must be signed in to change notification settings - Fork 1
Expand file tree
/
Copy pathopenapi.json
More file actions
9394 lines (9394 loc) · 296 KB
/
openapi.json
File metadata and controls
9394 lines (9394 loc) · 296 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
{
"openapi": "3.0.0",
"info": {
"title": "DealMaker API",
"description": "# Introduction\n\nWelcome 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.\n\n# Libraries\n\n- Javascript\n- Ruby\n\n# Authentication\n\nTo 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\n\n## Create an Application\n\nDealMaker’s Web API v1 supports the use of OAuth applications. Applications can be generated in your [account](https://app.dealmaker.tech/developer/applications).\n\nTo 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\n\n\n\nName your application and assign the level of permissions for this application\n\n\n\nOnce your application is created, save in a secure space your client ID and secret.\n\n**WARNING**: The secret key will not be visible after you click the close button\n\n\n\nFrom the developer tab, you will be able to view and manage all the available applications\n\n\n\nEach 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.\n\n## How to generate an access token\n\nAfter 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:\n\n`token endpoint` - https://app.dealmaker.tech/oauth/token\n\n`grant_type` - must be set to `client_credentials`\n\n`client_id` - the Client ID displayed when you created the OAuth application in the previous step\n\n`client_secret` - the Client Secret displayed when you created the OAuth application in the previous step\n\n`scope` - the scope is established when you created the OAuth application in the previous step\n\nNote: 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.\n\nTo 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.\n\n### Example\n\n#### Postman\n\nHere'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)\n\n\n\n# Status Codes\n\n## Content-Type Header\n\nAll responses are returned in JSON format. We specify this by sending the Content-Type header.\n\n## Status Codes\n\nBelow is a table containing descriptions of the various status codes we currently support against various resources.\n\nSometimes 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.\n\n| Status Code | Description |\n| ----------- | ----------- |\n| `200` | Success |\n| `403` | Forbidden |\n| `404` | Not found |\n\n# Pagination\n\nPagination 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.\n\nWhen 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.\n\nPlease review the table below for the input parameters\n\n## Inputs\n\n| Parameter | Description |\n| ---------- | ------------------------------------------------------------------------------- |\n| `per_page` | Amount of records included on each page (Default is 25) |\n| `page` | Page number |\n| `offset` | Amount of records offset on the API request where 0 represents the first record |\n\n## Response Headers\n\n| Response Header | Description |\n| --------------- | -------------------------------------------- |\n| `X-Total` | Total number of records of response |\n| `X-Total-Pages` | Total number of pages of response |\n| `X-Per-Page` | Total number of records per page of response |\n| `X-Page` | Number of current page |\n| `X-Next-Page` | Number of next page |\n| `X-Prev-Page` | Number of previous page |\n| `X-Offset` | Total number of records offset |\n\n# Search and Filtering (The q parameter)\n\nThe 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@dealmaker.tech\" should be passed as “john%2Binvestor%40dealmaker.tech”. There are two main ways to filter with it.\n\n## Keyword filtering\n\nSome 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.\n\nHere’s a list of possible keywords and the “scope” each one of the keywords filters by:\n\n| Keywords | Scope | Decoded Example | Encoded Example |\n| ---------------------------------------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------------- | ---------------------------------------------------------------------------------------- |\n| 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` |\n| 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` |\n| 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` |\n| Offline | Investors added to the deal offline | Offline | `Offline` |\n| Online | Investors added to the deal online | Online | `Online` |\n| Signed | Investors who signed their agreement | Signed | `Signed` |\n| Waiting for countersignature | Investors who have signed and are waiting for counter signature | Waiting for countersignature | `Waiting%20for%20countersignature` |\n| Invited | Investors on the Invited Status | Invited | `Invited` |\n| Accepted | Investors in the Accepted Status | Accepted | `Accepted` |\n| Questionnaire in progress | All Investors who have not finished completing the questionnaire | Questionnaire in progress | `Questionnaire%20in%20progress` |\n| Has attachments | All Investors with attachments | Has attachments | `Has%20attachments` |\n| Has notes | All Investors with notes | Has notes | `Has%20notes` |\n| Waiting for co-signature | Investors who have signed and are waiting for co-signature | Waiting for co-signature | `Waiting%20for%20co-signature` |\n| Background Check Approved | Investors with approved background check | Background Check Approved | `Background%20Check%20Approved` |\n| Document Review Pending | Investors with pending review | Document Review Pending | `Document%20Review%20Pending` |\n| Document Upload Pending | Investors with pending documents to upload | Document Upload Pending | `Document%20Upload%20Pending` |\n| Required adjudicator review | Investors who are required to be review by the adjudicator | Required adjudicator review | `Required%20adjudicator%20review` |\n\n---\n\n**NOTE**\n\nFiltering keywords are case sensitive and need to be encoded\n\n---\n\n## Search String\n\nAny 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.\n\nFor 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.\n\n# Versioning\n\nThe latest version is v1.\n\nThe version can be updated on the `Accept` header, just set the version as stated on the following example:\n\n```\n\nAccept:application/vnd.dealmaker-v1+json\n\n```\n\n| Version | Accept Header |\n| ------- | ----------------------------------- |\n| `v1` | application/vnd.dealmaker-`v1`+json |\n\n# SDK’s\n\nFor instruction on installing SDKs, please view the following links\n\n- [Javascript](https://github.com/DealMakerTech/api/tree/main/v1/clients/javascript)\n- [Ruby](https://github.com/DealMakerTech/api/tree/main/v1/clients/ruby)\n\n# Webhooks\n\nOur webhooks functionality allows clients to automatically receive updates on a deal's investor data.\n\nSome of the data that the webhooks include:\n\n- Investor Name\n- Date created\n- Email\n- Phone\n- Allocation\n- Attachments\n- Accredited investor status\n- Accredited investor category\n- State (Draft, Invited, Signed, Accepted, Waiting, Inactive)\n\nVia webhooks clients can subscribe to the following events as they happen on Dealmaker:\n\n- Investor is created\n- Investor details are updated (any of the investor details above change or are updated)\n- Investor has signed their agreement\n- Invertor fully funded their investment\n- Investor has been accepted\n- Investor is deleted\n\nA 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.\n\n## Configuration\n\nFor 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).\n\nAs a developer user on DealMaker, you are able to configure webhooks by following the steps below:\n\n1. Sign into Dealmaker\n2. Go to **“Your profile”** in the top right corner\n3. Access an **“Integrations”** configuration via the left menu\n4. The developer configures webhooks by including:\n - The HTTPS URL where the request will be sent\n - 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.\n - The Deal(s) to include in the webhook subscription\n - An email address that will be used to notify about errors.\n5. The developers can disable webhooks temporarily if needed\n\n## Specification\n\n### Events\n\nThe initial set of events will be related to the investor. The events are:\n\n1. `investor.created`\n\n - Triggers every time a new investor is added to a deal\n\n2. `investor.updated`\n\n - Triggers on updates to any of the following fields:\n - Status\n - Name\n - Email - (this is a user field so we trigger event for all investors with webhook subscription)\n - Allocated Amount\n - Investment Amount\n - Accredited investor fields\n - Adding or removing attachments\n - Tags\n - When the investor status is signed, the payload also includes a link to the signed document; the link expires after 30 minutes\n \n3. `investor.signed`\n\n - Triggers when the investor signs their subscription agreement (terms and conditions)\n - When this happens the investor.state becomes `signed`\n - This event includes the same fields as the `investor.updated` event\n\n4. `investor.funded`\n\n - Triggers when the investor becomes fully funded\n - This happens when the investor.funded_state becomes `funded`\n - This event includes the same fields as the `investor.updated` event\n\n5. `investor.accepted`\n\n - Triggers when the investor is countersigned\n - When this happens the investor.state becomes `accepted`\n - This event includes the same fields as the `investor.updated` event\n\n6. `investor.deleted`\n\n - Triggers when the investor is removed from the deal\n - The investor key of the payload only includes investor ID\n - The deal is not included in the payload. Due to our implementation it’s impossible to retrieve the deal the investor was part of\n\n### Requests\n\n- The request is a `POST`\n- The payload’s `content-type` is `application/json`\n- Only `2XX` responses are considered successful. In the event of a different response, we consider it failed and queue the event for retry\n- 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\n- If an event fails all the attempts to be delivered, we send an email to the address that the user configured\n\n### Payload\n\n#### Common Properties\n\nThere will be some properties that are common to all the events on the system.\n\n| Key | Type | Description |\n| ----------------- | ------ | -------------------------------------------------------------------------------------- |\n| event | String | The event that triggered the call |\n| event_id | String | A unique identifier for the event |\n| deal<sup>\\*</sup> | Object | The deal in which the event occurred. please see below for an example on the deal object<sup>\\*\\*</sup> |\n\n<sup>\\*</sup>This field is not included when deleting a resource\n\n<sup>\\*\\*</sup> Sample Deal Object in the webhook payload\n\n```json\n\"deal\": {\n \"id\": 0,\n \"title\": \"string\",\n \"created_at\": \"2022-12-06T18:14:44.000Z\",\n \"updated_at\": \"2022-12-08T12:46:48.000Z\",\n \"state\": \"string\",\n \"currency\": \"string\",\n \"security_type\": \"string\",\n \"price_per_security\": 0.00,\n \"deal_type\": \"string\",\n \"minimum_investment\": 0,\n \"maximum_investment\": 0,\n \"issuer\": {\n \"id\": 0,\n \"name\": \"string\"\n },\n \"enterprise\": {\n \"id\": 0,\n \"name\": \"string\"\n }\n }\n```\n\n#### Common Properties (investor scope)\n\nBy 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. |\n#### Investor State\n\nHere is a brief description of each investor state:\n\n- **Draft:** the investor is added to the platform but hasn't been invited yet and cannot access the portal\n- **Invited:** the investor was added to the platform but hasn’t completed the questionnaire\n- **Signed:** the investor signed the document (needs approval from Lawyer or Reviewer before countersignature)\n- **Waiting:** the investor was approved for countersignature by any of the Lawyers or Reviewers in the deal\n- **Accepted:** the investor's agreement was countersigned by the Signatory\n- **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\n\n#### Update Delay\n\nGiven 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.\n",
"version": ""
},
"x-tagGroups": [
{
"name": "Endpoints",
"tags": [
"deal",
"investor",
"investor_profile",
"company",
"country"
]
},
{
"name": "Models",
"tags": [
"deal_model",
"investor_model",
"investor_profile_model",
"company_model",
"address_model",
"country_model"
]
}
],
"tags": [
{
"name": "users",
"description": "Operations about users"
},
{
"name": "user",
"description": "Operations about users"
},
{
"name": "incentive_plan",
"description": "Operations about incentive_plans"
},
{
"name": "deals",
"description": "Operations about deals"
},
{
"name": "shareholder",
"description": "Operations about shareholders"
},
{
"name": "custom_emails",
"description": "Operations about custom_emails"
},
{
"name": "deal",
"description": "The Deal is the portal which a Company uses for its raise. Each deal will have one Company, and will have multiple investors. An Investor represents a specific investment, meaning that a User could have multiple Investments. A Deal has many complex components. The Deal will have a subscription agreement, which is the document investors will sign. The Deal will have team members which have different roles and permissions in terms of how they interact with the Deal and with Investors on the Deal. The Deal will also have payment methods set up to allow Investors to pay for their investments. These features can be accessed within the DealMaker application. To set up a Deal and interact with these features, please view our help desk documentation: [How can I set up my own deal?](https://help.dealmaker.tech/new-deal). In the production environment, a Deal’s invoice must be recorded as paid before it can be set to `active`, however this requirement is waived in the staging environment.\n\nWith the Deal Endpoints you may interact with your deals. Each Deal has a unique ID, which is accessible from the URL of any page on that Deal.",
"x-displayName": "Deal"
},
{
"name": "investor",
"description": "Each individual investment in a deal is an Investor. Investments belong to a User, and a User may have multiple Investments, across different deals or in the same deal. Each Investor has a unique ID, which is accessible on the overview page for that Investor. The access link for each Investor will also be unique, even if multiple investors belong to the same User. If an Investor is using an Investor Profile, a snapshot of the profile will be included with the Investor payload once they are in the signed state. An Investor enters the signed state when they sign their subscription agreement. If an Investor has not yet signed their agreement, or if an Investor is created without an associated profile, then the “investor_profile” field will be `null`.",
"x-displayName": "Investor"
},
{
"name": "investor_profile",
"description": "An Investor Profile contains information about the identity of the investor. The Investor Profile is the information which identifies how the investor’s securities will be registered, namely the type of investor, the investor’s name, and the investor’s address. There are four possible investor types: Individual, Joint (i.e. joint tenants, tenants in common, community property), Trust, and Corporation.\n\nThe profile will also contain more detailed information, depending on what type of investor it is. An individual investor will contain the date of birth and taxpayer identification number, while a corporation profile will contain information about the signing officer and beneficial owners. The investor profile will also contain the investor’s accredited investor status.\n\nAn investor profile belongs to the User. An investor profile may be created by the user themselves, when they complete an investment, or it may be created by an external API application on behalf of the user. Only a User may update their own profile - an external API application cannot update a profile on a User’s behalf. When an investment is created, it may be associated to an investor profile. A User may have many Investor Profiles, and an Investor Profile may have many Investors associated to it. This may be represented by the structure below.\n\n\nAn investor profile contains all the information about an investor which is needed to complete an investment. The specific investment in a deal is done through the Investor model. The Investor model takes all the information contained in the Investor Profile and applies it to a specific investment, in a deal. When an Investor moves into the signed state (which happens the investor signs their digital subscription agreement), a snapshot is created of the Investor Profile to which that Investor is associated. This snapshot will make available the core information about that investor, including name, address, date of birth, taxpayer ID, and other fields (depending on profile type). The snapshot will reflect the information contained in the profile at the time the Investor moved into the signed state, meaning if the Investor Profile is update at a future time, any existing Investors associated with it who were in the signed (or waiting or accepted) states will not reflect the updates.\n\nAn Investor is related to a deal, but an Investor Profile is not. A User is also not related to any specific deal. A User may use an Investor Profile to create an Investor, the latter of which will be related to a specific deal.",
"x-displayName": "Investor Profile"
},
{
"name": "company",
"description": "Access to your companies",
"x-displayName": "Company"
},
{
"name": "country",
"description": "Access to your companies",
"x-displayName": "Country"
},
{
"name": "deal_model",
"description": "<SchemaDefinition schemaRef=\"#/components/schemas/V1_Entities_Deal\" />",
"x-displayName": "Deal"
},
{
"name": "investor_model",
"description": "<SchemaDefinition schemaRef=\"#/components/schemas/V1_Entities_Investor\" />",
"x-displayName": "Investor"
},
{
"name": "investor_profile_model",
"description": "<SchemaDefinition schemaRef=\"#/components/schemas/V1_Entities_InvestorProfile_Individual\" />",
"x-displayName": "Investor Profile"
},
{
"name": "company_model",
"description": "<SchemaDefinition schemaRef=\"#/components/schemas/V1_Entities_Company\" />",
"x-displayName": "Company"
},
{
"name": "address_model",
"description": "<SchemaDefinition schemaRef=\"#/components/schemas/V1_Entities_Address\" />",
"x-displayName": "Address"
},
{
"name": "country_model",
"description": "<SchemaDefinition schemaRef=\"#/components/schemas/V1_Entities_Country\" />",
"x-displayName": "Country"
},
{
"name": "upload",
"description": "Presigned url for interacting with a defined S3 buckets",
"x-displayName": "Upload"
}
],
"paths": {
"/investor_profiles/{deal_id}": {
"get": {
"summary": "Get list of InvestorProfiles for a specific deal",
"description": "Get investor profiles for a specific deal. Because an investor profile belongs\n to the user associated with it, external applications may not use this endpoint\n for other profiles. Only the user may use this endpoint for their own profiles\n (i.e. to see existing profiles within the DealMaker application).",
"parameters": [
{
"in": "query",
"name": "page",
"description": "Page offset to fetch.",
"required": false,
"schema": {
"type": "integer",
"format": "int32",
"default": 1
}
},
{
"in": "query",
"name": "per_page",
"description": "Number of results to return per page.",
"required": false,
"schema": {
"type": "integer",
"format": "int32",
"default": 25
}
},
{
"in": "query",
"name": "offset",
"description": "Pad a number of results.",
"required": false,
"schema": {
"type": "integer",
"format": "int32",
"default": 0
}
},
{
"in": "path",
"name": "deal_id",
"description": "The deal id.",
"required": true,
"schema": {
"type": "integer",
"format": "int32"
}
},
{
"in": "query",
"name": "user_id",
"description": "The user id filter.",
"required": false,
"schema": {
"type": "integer",
"format": "int32"
}
}
],
"security": [
{
"oauth": []
}
],
"responses": {
"200": {
"description": "Get investor profiles for a specific deal",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfiles"
}
}
}
},
"401": {
"description": "Forbidden"
}
},
"tags": [
"investor_profile"
],
"operationId": "getDealInvestorProfiles",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles": {
"get": {
"summary": "Get list of InvestorProfiles",
"description": "Get investor profiles. Because an investor profile belongs to the user associated with it, external\n applications may not use this endpoint for other profiles. Only the user may use this endpoint for\n their own profiles (i.e. to see existing profiles within the DealMaker application).",
"parameters": [
{
"in": "query",
"name": "page",
"description": "Page offset to fetch.",
"required": false,
"schema": {
"type": "integer",
"format": "int32",
"default": 1
}
},
{
"in": "query",
"name": "per_page",
"description": "Number of results to return per page.",
"required": false,
"schema": {
"type": "integer",
"format": "int32",
"default": 25
}
},
{
"in": "query",
"name": "offset",
"description": "Pad a number of results.",
"required": false,
"schema": {
"type": "integer",
"format": "int32",
"default": 0
}
}
],
"security": [
{
"oauth": []
}
],
"responses": {
"200": {
"description": "Get investor profiles",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfiles"
}
}
}
},
"401": {
"description": "Forbidden"
}
},
"tags": [
"investor_profile"
],
"operationId": "getInvestorProfiles",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles/profile/{id}": {
"get": {
"summary": "Get an investor profile by id",
"description": "Get an investor profile. Because an investor profile belongs to the user associated with it, external applications\n may not use this endpoint for other profiles. Only the user may use this endpoint for their own profiles (i.e. to\n see existing profiles within the DealMaker application).",
"parameters": [
{
"in": "path",
"name": "id",
"description": "The id of the investor profile.",
"required": true,
"schema": {
"type": "integer",
"format": "int32"
}
}
],
"security": [
{
"oauth": []
}
],
"responses": {
"200": {
"description": "Get an investor profile",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfileItem"
}
}
}
},
"401": {
"description": "Forbidden"
}
},
"tags": [
"investor_profile"
],
"operationId": "getInvestorProfile",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles/{type}/{id}": {
"delete": {
"summary": "Delete investor profile.",
"description": "Deletes the investor profile.",
"parameters": [
{
"in": "path",
"name": "type",
"required": true,
"schema": {
"type": "integer",
"format": "int32"
}
},
{
"in": "path",
"name": "id",
"required": true,
"schema": {
"type": "integer",
"format": "int32"
}
}
],
"security": [
{
"oauth": [
"deals.write"
]
}
],
"responses": {
"204": {
"description": "Investor profile deleted successfully."
},
"400": {
"description": "Bad Request"
},
"403": {
"description": "Forbidden"
}
},
"tags": [
"investor"
],
"operationId": "deleteInvestorProfile",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles/corporations": {
"post": {
"summary": "Create new corporation investor profile.",
"description": "Create new corporation investor profile associated to the user by email.",
"requestBody": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/postInvestorProfilesCorporations"
}
}
},
"required": true
},
"security": [
{
"oauth": [
"deals.write"
]
}
],
"responses": {
"201": {
"description": "Create new corporation investor profile.",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfile_Id"
}
}
}
},
"400": {
"description": "Bad Request"
},
"401": {
"description": "Forbidden"
}
},
"tags": [
"investor_profile"
],
"operationId": "createCorporationProfile",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles/corporations/{investor_profile_id}": {
"patch": {
"summary": "Patch a corporation investor profile",
"description": "Patch corporation investor profile",
"parameters": [
{
"in": "path",
"name": "investor_profile_id",
"required": true,
"schema": {
"type": "integer",
"format": "int32"
}
}
],
"requestBody": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/patchInvestorProfilesCorporations"
}
}
},
"required": true
},
"security": [
{
"oauth": [
"deals.write"
]
}
],
"responses": {
"200": {
"description": "Patch corporation investor profile",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfile_Id"
}
}
}
},
"400": {
"description": "Bad Request"
},
"403": {
"description": "Forbidden"
},
"404": {
"description": "Not found"
}
},
"tags": [
"investor_profile"
],
"operationId": "patchCorporationProfile",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles/joints": {
"post": {
"summary": "Create new joint investor profile",
"description": "Create new joint investor profile associated to the user by email.",
"requestBody": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/postInvestorProfilesJoints"
}
}
},
"required": true
},
"security": [
{
"oauth": [
"deals.write"
]
}
],
"responses": {
"201": {
"description": "Create new joint investor profile",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfile_Id"
}
}
}
},
"400": {
"description": "Bad Request"
}
},
"tags": [
"investor_profile"
],
"operationId": "createJointProfile",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles/joints/{investor_profile_id}": {
"patch": {
"summary": "Patch a joint investor profile",
"description": "Patch joint investor profile",
"parameters": [
{
"in": "path",
"name": "investor_profile_id",
"required": true,
"schema": {
"type": "integer",
"format": "int32"
}
}
],
"requestBody": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/patchInvestorProfilesJoints"
}
}
},
"required": true
},
"security": [
{
"oauth": [
"deals.write"
]
}
],
"responses": {
"200": {
"description": "Patch joint investor profile",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfile_Id"
}
}
}
},
"400": {
"description": "Bad Request"
},
"403": {
"description": "Forbidden"
},
"404": {
"description": "Not found"
}
},
"tags": [
"investor_profile"
],
"operationId": "patchJointProfile",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles/individuals": {
"post": {
"summary": "Create new individual investor profile",
"description": "Create new individual investor profile associated to the user by email.",
"requestBody": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/postInvestorProfilesIndividuals"
}
}
},
"required": true
},
"security": [
{
"oauth": [
"deals.write"
]
}
],
"responses": {
"201": {
"description": "Create new individual investor profile",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfile_Id"
}
}
}
},
"400": {
"description": "Bad Request"
},
"401": {
"description": "Forbidden"
}
},
"tags": [
"investor_profile"
],
"operationId": "createIndividualProfile",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles/individuals/{investor_profile_id}": {
"patch": {
"summary": "Patch an individual investor profile.",
"description": "Patch individual investor profile.",
"parameters": [
{
"in": "path",
"name": "investor_profile_id",
"required": true,
"schema": {
"type": "integer",
"format": "int32"
}
}
],
"requestBody": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/patchInvestorProfilesIndividuals"
}
}
},
"required": true
},
"security": [
{
"oauth": [
"deals.write"
]
}
],
"responses": {
"200": {
"description": "Patch individual investor profile.",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfile_Id"
}
}
}
},
"400": {
"description": "Bad Request"
},
"403": {
"description": "Forbidden"
},
"404": {
"description": "Not found"
}
},
"tags": [
"investor_profile"
],
"operationId": "patchIndividualProfile",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles/trusts": {
"post": {
"summary": "Create new trust investor profile.",
"description": "Create new trust investor profile associated to the user by email.",
"requestBody": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/postInvestorProfilesTrusts"
}
}
},
"required": true
},
"security": [
{
"oauth": [
"deals.write"
]
}
],
"responses": {
"201": {
"description": "Create new trust investor profile.",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfile_Id"
}
}
}
},
"400": {
"description": "Bad Request"
},
"401": {
"description": "Forbidden"
}
},
"tags": [
"investor_profile"
],
"operationId": "createTrustProfile",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles/trusts/{investor_profile_id}": {
"patch": {
"summary": "Patch a trust investor profile",
"description": "Patch trust investor profile",
"parameters": [
{
"in": "path",
"name": "investor_profile_id",
"required": true,
"schema": {
"type": "integer",
"format": "int32"
}
}
],
"requestBody": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/patchInvestorProfilesTrusts"
}
}
},
"required": true
},
"security": [
{
"oauth": [
"deals.write"
]
}
],
"responses": {
"200": {
"description": "Patch trust investor profile",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfile_Id"
}
}
}
},
"400": {
"description": "Bad Request"
},
"403": {
"description": "Forbidden"
},
"404": {
"description": "Not found"
}
},
"tags": [
"investor_profile"
],
"operationId": "patchTrustProfile",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/investor_profiles/managed": {
"post": {
"summary": "Create new managed investor profile.",
"description": "Create new managed investor profile associated to the user by email.",
"requestBody": {
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/postInvestorProfilesManaged"
}
}
},
"required": true
},
"security": [
{
"oauth": [
"deals.write"
]
}
],
"responses": {
"201": {
"description": "Create new managed investor profile.",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_InvestorProfile_Id"
}
}
}
},
"400": {
"description": "Bad Request"
},
"401": {
"description": "Forbidden"
}
},
"tags": [
"investor_profile"
],
"operationId": "createManagedProfile",
"x-codeSamples": [
{
"lang": "javascript",
"source": ""
},
{
"lang": "ruby",
"source": ""
}
]
}
},
"/uploads/generate_url": {
"post": {
"summary": "Create a presigned URL for Amazon S3",
"description": "Create a presigned URL for uploading file to Amazon S3 bucket",
"requestBody": {
"content": {
"application/x-www-form-urlencoded": {
"schema": {
"type": "object",
"properties": {
"filename": {
"description": "The name of the file to be uploaded to S3.",
"type": "string"
},
"target": {
"description": "The target is used to figure out the intended destination (which cloud provider and which bucket)",
"type": "string",
"enum": [
"IDOCR",
"GENERAL_UPLOAD"
]
}
},
"required": [
"filename"
]
}
}
},
"required": true
},
"security": [
{
"oauth": [
"internal"
]
}
],
"responses": {
"201": {
"description": "Create a presigned URL for uploading file to Amazon S3 bucket",
"content": {
"application/json": {
"schema": {
"$ref": "#/components/schemas/V1_Entities_PresignedUrlResult"
}
}
}
},
"400": {
"description": "Bad Request"
},
"403": {
"description": "Forbidden"
}