Webbdevelop PRO RWA Platform API (1.0.0)

Invest Platform uses an cookie authorize all requests, allowing access to the API. Proper cookie automatically generated during sign up process. Platform expects cookie to be included via HTTP in all API requests to the server.

To learn the ACCOUNT_NAME for your target account, you can get it with the /authorization API call.

This returns the following as a JSON payload:

So, this curl call:

curl https://platform.com/api/authorization \
  -u <YOUR_API_KEY>:x

Returns JSON structured like this:

{
  "identity": {
    "id": "999",
    "name": "Sheldon Cooper",
    "email": "s.cooperphd@yahoo.com",
    "publishable_key":"pk_1111111111111111",
    "href": "https://nippur-999.platform.com/api/"
  }
}

Note that in all cases, if the user does not have permission to do something, you'll get a 401 Unauthorized error.

To make it easier to determine if your application is being rate-limited, or is approaching that level, we have the following HTTP headers on our successful responses:

• X-RateLimit-Reset: The remaining window before the rate limit resets in UTC epoch seconds.
• X-RateLimit-Remaining: The number of requests left for the time window.
• X-RateLimit-Limit: Request limit per time window.

The current limits are 100 API calls per 15 seconds.

We reserve the right to tune the limitations, but we promise to keep them high enough to allow a well-behaving interactive app to do it's job.

When you exceed the limit you will receive a HTTP 429 (Too Many Requests).

We don't usually have any trouble on our end, but when we do we'll let you know!

The Platform API uses the following error codes:

Note that when API errors occur, it is up to you to retry your request - Platform does not keep track of failed calls.

Create a log and store it in timeline storage

Create a PageView log and store it in timeline storage

Return a list of PageView Rows

Return PageView Statistics in format usable for diagrams

Create Distribution of profile

Create Distribution for profile

Initialize accreditation request in escrow account

Start accreditation process

Send accreditation document for verification

Manually update user accreditation status. Use only in case of emergency

Synchronize accreditation status with accreditation partner

Handle accreditation provider status change webhook

Create escrow account in escrow partner

Create offer in escrow provider

Create issuer in escrow provider

Create Esign Signature Request

Return binary blob of signed document

Exchange tokens

Get Wallet Information

Withdraw token from a wallet

delete file by ID

get file by ID

returns url for file downloading

returns url for file uploading

returns metadata by object ID and object Name

returns user's files

delete file by ID

get file by ID

returns url for file downloading

returns url for file uploading

returns metadata by object ID and object Name

get file by ID

returns metadata by object ID and object Name

Create an investor’s initial commitment to an offering.

Workflow overview:
1. Validate investor eligibility (KYC/AML).
2. Verify offering availability and minimum investment amount.
3. Record the commitment, status, and allocation.
4. Return the created investment record with its unique identifier.
    

Set up investment amount

Set up Ownership information

Create electronical signature document with legal binding

Funding step

Investment Confirmation Step

Get list of user confirmed investments

Get list of user unconfirmed investments

List of user bank accounts

Get user investment by id