Getting Started
Introduction
Vaultody is a platform that offers a suite of secure storage and management solutions for digital assets. The Vaultody platform includes a range of APIs (Application Programming Interfaces) and SDKs (Software Development Kits) that allow developers to integrate digital asset storage and management functionality into their applications and systems.
The technical documentation for Vaultody provides developers with a comprehensive overview of the platform's APIs, SDKs, and other tools, including their functionality, usage, and integration requirements. The documentation covers a range of topics, including digital asset storage and management protocols, secure key management, and multi-factor authentication.
You can download our OpenAPI 3.0 Specification as the latest JSON from here.
Supported Protocols and Networks
Vaultody's support for a wide range of digital assets makes it an ideal platform for developers and businesses looking to securely store and manage their digital assets. The platform is designed to support a variety of blockchain protocols and is constantly updating to support new assets as they become available. Supported Protocols.
The Dashboard
Once you create an account, you get access to a personalized Vaultody Dashboard.
From the Dashboard you can:
- Creating vaults
- Generating deposit addresses
- Creating transaction requests
- Managing funds
- Performing account-related actions
- Accessing specific features or functionalities of an API
- Create API key with specific access
Authenticate requests
To use and make calls to Vaultody, you must create an API key, in order for your requests to be authenticated.
An API key is a code unique to the user who generated it. It is used to identify the call to the specific API and track the access to it and its usage. You can generate your API key from within the Vaultody dashboard by clicking on the “Create new API key” button. You can generate more than one API key and use a single API key more than once.
For more information on Authenticating requests, please see “Authentication” section.