How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Algorand Multisig API

The Multisig API from Algorand — 6 operation(s) for multisig.

Algorand Multisig API is one of 15 APIs that Algorand publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Multisig. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 6 operations across 6 paths, and defines 19 schemas. It is described by OpenAPI 3.2.0, at version 0.0.1.

Requests are made against a single base URL, http://localhost/.

6 operations 6 paths 19 schemas 1 DELETE5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.0.1
Base URL
https://mainnet-api.4160.nodely.dev
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Algorand Multisig API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-KMD-API-Token (api_key). By default, every request must be authenticated.

  • api_key — Generated header parameter. This value can be found in /kmd/data/dir/kmd.token. Example value: '330b2e4fc9b20f4f89812cf87f1dabeb716d23e3f11aec97a61ff5f750563b7…

Paths & Operations 6

Across 6 paths, the API surfaces 6 operations — 1 DELETE, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Multisig 6
DELETE
/v1/multisig
Delete a multisig
DeleteMultisig body → 200
POST
/v1/multisig/export
Export multisig address metadata
ExportMultisig body → 200
POST
/v1/multisig/import
Import a multisig account
ImportMultisig body → 200
POST
/v1/multisig/list
List multisig accounts
ListMultisg body → 200
POST
/v1/multisig/sign
Sign a multisig transaction
SignMultisigTransaction body → 200
POST
/v1/multisig/signprogram
Sign a program for a multisig account
SignMultisigProgram body → 200

Schemas 19

The contract defines 19 schemas that model the data the API accepts and returns. The most detailed are SignProgramMultisigRequest (7 properties), SignMultisigRequest (6 properties), APIV1POSTMultisigExportResponse (5 properties), ImportMultisigRequest (4 properties). Each schema is shown below with its type and property counts.

MultisigSubsig
object
MultisigSubsig is a struct that holds a pair of public key and signatures signatures may be empty
2 properties
APIV1POSTMultisigProgramSignResponse
object
APIV1POSTMultisigProgramSignResponse is the response to POST /v1/multisig/signdata friendly:SignProgramMultisigResponse
3 properties
PublicKey
PublicKey is an exported ed25519PublicKey
SignMultisigRequest
object
APIV1POSTMultisigTransactionSignRequest is the request for POST /v1/multisig/sign
6 properties
ImportMultisigRequest
object
APIV1POSTMultisigImportRequest is the request for POST /v1/multisig/import
4 properties
APIV1DELETEMultisigResponse
object
APIV1DELETEMultisigResponse is the response to POST /v1/multisig/delete friendly:DeleteMultisigResponse
2 properties
Digest
array
Signature
A Signature is a cryptographic signature. It proves that a message was produced by a holder of a cryptographic secret.
ed25519Signature
array
ExportMultisigRequest
object
APIV1POSTMultisigExportRequest is the request for POST /v1/multisig/export
2 properties
APIV1POSTMultisigListResponse
object
APIV1POSTMultisigListResponse is the response to POST /v1/multisig/list friendly:ListMultisigResponse
3 properties
ListMultisigRequest
object
APIV1POSTMultisigListRequest is the request for POST /v1/multisig/list
1 property
MultisigSig
object
MultisigSig is the structure that holds multiple Subsigs
3 properties
DeleteMultisigRequest
object
APIV1DELETEMultisigRequest is the request for DELETE /v1/multisig
3 properties
APIV1POSTMultisigExportResponse
object
APIV1POSTMultisigExportResponse is the response to POST /v1/multisig/export friendly:ExportMultisigResponse
5 properties
SignProgramMultisigRequest
object
APIV1POSTMultisigProgramSignRequest is the request for POST /v1/multisig/signprogram
7 properties
APIV1POSTMultisigTransactionSignResponse
object
APIV1POSTMultisigTransactionSignResponse is the response to POST /v1/multisig/sign friendly:SignMultisigResponse
3 properties
APIV1POSTMultisigImportResponse
object
APIV1POSTMultisigImportResponse is the response to POST /v1/multisig/import friendly:ImportMultisigResponse
3 properties
ed25519PublicKey
array

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

algorand-multisig-api-openapi.yml Raw ↑

Other APIs Algorand publishes across the network.

Algorand KMD REST API
Algorand common API
Algorand Key API
Algorand lookup API
Algorand Master Key API
Algorand private API
Algorand Program API
Algorand public API
Algorand search API
Algorand Swagger.json API
Algorand Transaction API
Algorand Versions API
Where this information came from

This is an independent, third-party profile of Algorand Multisig API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.