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 as well.

• Javascript
• Ruby

To authenticate, add an Authorization header to your API request that contains an access token. Before you generate an access token your must first create an application on your portal and retrieve the your client ID and secret

DealMaker’s Web API v1 supports the use of OAuth applications. Applications can be generated in your account.

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

Name your application and assign the level of permissions for this application

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

From the developer tab, you will be able to view and manage all the available applications

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.

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

All responses are returned in JSON format. We specify this by sending the Content-Type header.

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.

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

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@dealmaker.tech" should be passed as “john%2Binvestor%40dealmaker.tech”. There are two main ways to filter with it.

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:

NOTE

Filtering keywords are case sensitive and need to be encoded

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.

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

For instruction on installing SDKs, please view the following links

• Javascript
• Ruby

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.

For a comprehensive guide on how to configure Webhooks please visit our support article: Configuring Webhooks on DealMaker – DealMaker Support.

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

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.

^*This field is not included when deleting a resource

^** Sample Deal Object in the webhook payload

"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. This will allow you to get all the necessary information you need about a particular investor without having to call the Get Investor by ID endpoint. |

Investor State

Here is a brief description of each investor state:

• Draft: the investor is added to the platform but hasn't been invited yet and cannot access the portal
• Invited: the investor was added to the platform but hasn’t completed the questionnaire
• Signed: the investor signed the document (needs approval from Lawyer or Reviewer before countersignature)
• Waiting: the investor was approved for countersignature by any of the Lawyers or Reviewers in the deal
• Accepted: the investor's agreement was countersigned by the Signatory
• Inactive the investor is no longer eligible to participate in the offering. This may be because their warrant expired, they requested a refund, or they opted out of the offering

Update Delay

Given the high number of updates our platform performs on any investor, we’ve added a cool down period on update events that allows us to “group” updates and trigger only one every minute. In consequence, update events will be delivered 1 minute after the initial request was made and will include the latest version of the investor data at delivery time.

The 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?. 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.

With 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.

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.