Communication
Last updated
Last updated
This API suite focuses on managing connections within an Identus agent system, with different authentication keys for different subsystems or access levels. The communication layer is mostly managed via DID Comm v2 (within Identus)
GET
/api/v1/p2p
<Description of the endpoint>
Headers
Name | Value |
---|---|
Body
Response
GET
/api/v1/p2p/{id_connection}
<Description of the endpoit>
Headers
Body
Response
POST
/api/v1/p2p/invite
<Description of the endpoint>
Headers
Body
Response
POST
/api/v1/p2p/accept
Headers
Body
Response
POST
/api/v1/p2p/custodial/connect
Creates a connection between two peers, in a custodial mode, where the owner (generally peer1) can then act as issuer, verifier, etc...
Headers
Body
Response
Name | Value |
---|---|
Name | Value |
---|---|
Name | Type | Description |
---|---|---|
Name | Value |
---|---|
Name | Type | Description |
---|---|---|
Name | Value |
---|---|
Name | Type | Description |
---|---|---|
Content-Type
application/json
Authorization
apikey = {Alice's API key}
Content-Type
application/json
Authorization
apikey = {Alice's API key}
Content-Type
application/json
Authorization
apikey = {Alice's API key}
from
string
This is to generate a nicely formed message
Content-Type
application/json
Authorization
apikey = {Bob's API key}
invitation
string
The out of band invitation (eg: eyJpZCI6Ij...dfX0)
Content-Type
application/json
Authorization
None
key_peer1
string
the private authentication key of peer1
key_peer2
string
the private authentication key of peer1
name_peer1
string
name of peer1
name_peer2
string
name of peer2