https://api.vertalo.com/docs/introduction/ Recent content in 1 Introduction on Vertalo API Primer Hugo -- gohugo.io en Copyright © {year} Vertalo Inc., a SeriesX Company. All rights reserved. Tue, 28 Jan 2020 00:34:39 +0900 https://api.vertalo.com/docs/introduction/welcome/ Tue, 28 Jan 2020 00:39:09 +0900 https://api.vertalo.com/docs/introduction/welcome/ The Vertalo platform is a modern, blockchain-aware architecture that supports many functions, including: Digital asset configuration and management Investor onboarding (with KYC/AML, accreditation, document signing) Payment processing Cap table management Securities issuance Tokenization ATS integration General transfer agency services As an “integration first” company, Vertalo has designed its platform in an open and flexible way. This makes it possible for our partners to integrate with our platform through the Vertalo API when and where it’s needed. https://api.vertalo.com/docs/introduction/roles/ Tue, 28 Jan 2020 00:39:09 +0900 https://api.vertalo.com/docs/introduction/roles/ It’s important that you understand the basic Vertalo access control model and how your API access fits within it. A central part of the Vertalo access control model is the concept of roles. The following roles are currently supported: Role Description System Privileges Issuer A legal entity that registers and sells securities, with the purpose of generating income to fund operations. Create assets, rounds, allocations, distributions; manage investors; issue and tokenize holdings Broker A legal entity that assists with the distribution of an issuer’s offerings to investors, including broker-dealers, registered investment advisors, capital advisors. https://api.vertalo.com/docs/introduction/accounts-users/ Tue, 28 Jan 2020 00:39:09 +0900 https://api.vertalo.com/docs/introduction/accounts-users/ There is a distinction between accounts and users in the Vertalo system. An account defines an entity in the system to which a single role is assigned (for instance, the issuer role). One or more users are then assigned as a delegate to the account and these users exercise the rights that the role allows. So in effect, an account is a collection of privileges granted to an entity. Delegation The delegation model described above allows for a one-to-many relationship between account and users, and gives you a great deal of flexibility as to how to manage access to the accounts you control. https://api.vertalo.com/docs/introduction/multi-tenancy/ Tue, 28 Jan 2020 00:39:09 +0900 https://api.vertalo.com/docs/introduction/multi-tenancy/ As a multi-tenant system, an investor has a single account in the Vertalo platform regardless of how many different vendors with which they may be engaged. For instance, an investor may hold shares with both Issuer A and Issuer B. From an investor perspective, the investor is a customer to each issuer but has only one account in the system. The challenge comes when allowing each vendor to maintain its own version of the investor’s details (name, address, etc. https://api.vertalo.com/docs/introduction/getting-going/ Tue, 28 Jan 2020 00:39:09 +0900 https://api.vertalo.com/docs/introduction/getting-going/ Your starting point for exploring the Vertalo API is the Vertalo Sandbox. The Sandbox is a fully functioning version of our production environment and allows participants to model assets, rounds and other entities in a safe and controlled manner. For an organization that is interested in leveraging the Vertalo API, the Sandbox also offers a way to explore and try out the API through an interactive interface. Follow these steps to access this environment: https://api.vertalo.com/docs/introduction/object-model/ Tue, 28 Jan 2020 00:39:09 +0900 https://api.vertalo.com/docs/introduction/object-model/ The Vertalo object model consists of the following major components: Users Accounts Assets Rounds Allocations Investors Distributions Securities Holdings As you peruse the API documentation in GraphiQL, you’ll see these objects appearing in root-level fieldnames, type names, and other areas of the API. The examples in this section represent a good starting point for your exploration of the Vertalo API. The basic pre-issuance object hierarchy is: Issuers (which manage) Assets (which contain) Rounds (which contain) Allocations (which contain) Investors (which hold) Distributions The basic post-issuance object hierarchy is: https://api.vertalo.com/docs/introduction/partner-integrations/ Tue, 28 Jan 2020 00:39:09 +0900 https://api.vertalo.com/docs/introduction/partner-integrations/ As a digital transfer agent, Vertalo sits at the intersection of a digital asset ecosystem that includes key partners providing the following services: KYC/AML Accreditation Document signing Payment Processing Trade order matching Custody/Escrow The Vertalo platform is integrated with partners in each of these categories. These integrations, however, are not available to issuers or brokers through the API as they require investor login. The platform enforces safeguards that prevent an issuer or broker from acting on behalf of an investor for certain actions and thereby ensuring investor protection. https://api.vertalo.com/docs/introduction/postgraphile/ Tue, 28 Jan 2020 00:39:09 +0900 https://api.vertalo.com/docs/introduction/postgraphile/ The Vertalo GraphQL API is derived from a collection of PostgreSQL databases that underpin our platform. We also use an open-source framework called PostGraphile, which is able to interpret a PostgreSQL schema and then auto-generate a GraphQL schema from it. It is recommended that you gain some familiarity with PostGraphile in order to understand how the Vertalo API is created. The PostGraphile documentation provides a roadmap to what you’ll see in the Vertalo API. https://api.vertalo.com/docs/introduction/internal-blockchain/ Tue, 28 Jan 2020 00:39:09 +0900 https://api.vertalo.com/docs/introduction/internal-blockchain/ A purely internal, proprietary blockchain underpins the Vertalo software model, creating a complex web of relationships between pre-issuance and post-issuance events/objects. As a purpose-built digital asset ledger, this architecture also allows for a consistent, clean mapping between internal events (typically related to the issuance and transfer of shares) and those on the external blockchains with which Vertalo is integrated. As you explore and traverse the Vertalo GraphQL schema exposed through the API, you will see refererences to internal blockchain addresses throughout, and in many use cases these addresses allow you to make connections between various nodes in the graph.