The AngelList data model is made up of a few key data structures detailed below.

Account

An Account is a AngelList user and keeps track of the information we need to authenticate a user (e.g. email address, etc).

We support the ability for trusted third parties (the organizations integrating with our API) to create Limited Sessions for their users, in which they authenticate an account using a signed JWT. Accounts created via this mechanism are called Connected Accounts and (by default) cannot authenticate on their own. They require their connected organization to sign an authentication request for them.

Organization

An Organization represents a company within AngelList. Organizations can have multiple entities that represent different subsidiaries, trusts, funds, etc. Multiple Organizations can have access to a single Entity; however, there is always one primary organization for an entity. This is useful if third-party Organizations (e.g. consultants, auditors) need access to an Entity with limited permissions.

Entity

An Entity corresponds to a legal entity used in a transaction. Senders send transactions from an entity (typically one of their funds), and Recipients complete transactions using one of their entities (e.g. an Individual entity, a Partnership entity, etc).

An entity has an email and a name.

Transactions are made between two Entities.

Transaction

A transaction is defined as a set of exchanges between two Entities completing processes (e.g., completing contracts and/or passing information to each other). A Transaction object in AngelList contains information about:

• Transaction Processes
• Transaction Files
• Transaction Recipients
• Sender Entity

A transaction is created based on a template, which is based on a workflow. A transaction is complete only when all processes are complete.

States

Note: These are the default states for the AngelList platform. If these states do not fit your workflow, please contact the AngelList team and we can customize the workflow to fit your needs.

• created - Initial state
• pendingSubmission - Sent to the investor, awaiting submission
• submitted - Submitted by investor
• pendingReview - Picked up by fund administrator, awaiting final review notes
• pendingRevision - Sent back to investor for revision by the fund administrator
• igo - Review completed, marked in good order by the fund administrator
• confirmed - Counter-signed by the customer
• rejected - Review completed, marked rejected by the fund administrator