Communication
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)
Retrieve a list of connections between Alice and Bob
GET
/api/v1/p2p
<Description of the endpoint>
Headers
Content-Type
application/json
Authorization
apikey = {Alice's API key}
Body
Response
Retrieve a specific connection maintained for Alice and Bob
GET
/api/v1/p2p/{id_connection}
<Description of the endpoit>
Headers
Content-Type
application/json
Authorization
apikey = {Alice's API key}
Body
Response
Create a connection invitation, handling out-of-band invitations
POST
/api/v1/p2p/invite
<Description of the endpoint>
Headers
Content-Type
application/json
Authorization
apikey = {Alice's API key}
Body
from
string
This is to generate a nicely formed message
Response
Accept a specific connection invitation
POST
/api/v1/p2p/accept
Headers
Content-Type
application/json
Authorization
apikey = {Bob's API key}
Body
invitation
string
The out of band invitation (eg: eyJpZCI6Ij...dfX0)
Response
Creates a communication between two peers in custodial mode
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
Content-Type
application/json
Authorization
None
Body
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
Response
Last updated