IntenseFinance/simplex-chat
3
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
Files
d74c109328dc62d9f3ae5fbb661558b9e23d9f2f
simplex-chat/simplex-messaging-api.md
Evgeny Poberezkin cc55bf3e6b Different approach to commands (#34) 
* different approach to command types (WIP)

* PartyProtocol class and other commands

* pretty-print scenarion

* remove old files

* remove unused prf/predicate templates

* remove NoImplicitePrelude from doctest (although there are no doctests atm)
2020-05-31 21:51:15 +01:00

3.7 KiB
Raw Blame History

Simplex messaging protocol REST API

This document lists all required REST endpoints of simplex messaging API.

Also see Simplex messaging protocol implementation for more details.

POST /connection

Create connection

Request:

  • Supported content types are:

    • application/json;charset=utf-8
    • application/json

  • Example (application/json;charset=utf-8, application/json):

{"recipientKey":"BODbZxmtKUUF1l8pj4nVjQ"}

Response:

  • Status code 201

  • Headers: []

  • Supported content types are:

    • application/json;charset=utf-8
    • application/json

  • Example (application/json;charset=utf-8, application/json):

{"senderId":"N9pA3g","recipientId":"Qxz93A"}

DELETE /connection/:connectionId

Delete connection

Captures:

  • connectionId: Recipient connection ID - unique connection ID to be used by connection recipient

Response:

  • Status code 200

  • Headers: []

  • Supported content types are:

    • application/json;charset=utf-8
    • application/json

  • Example (application/json;charset=utf-8, application/json):

PUT /connection/:connectionId

Secure connection

Captures:

  • connectionId: Recipient connection ID - unique connection ID to be used by connection recipient

Request:

  • Supported content types are:

    • application/json;charset=utf-8
    • application/json

  • Example (application/json;charset=utf-8, application/json):

{"senderKey":"XPaVEVNunkYKqqK0dnAT5Q"}

Response:

  • Status code 200

  • Headers: []

  • Supported content types are:

    • application/json;charset=utf-8
    • application/json

  • Example (application/json;charset=utf-8, application/json):

GET /connection/:connectionId/messages

Get messages

Captures:

  • connectionId: Recipient connection ID - unique connection ID to be used by connection recipient

GET Parameters:

  • fromMessageId
    • Values: message ID, e.g., p8PCiGPZ
    • Description: if set, the server will respond with the messages received starting from the message with server message ID (unique per server) passed in this parameter.

Response:

  • Status code 200

  • Headers: []

  • Supported content types are:

    • application/json;charset=utf-8
    • application/json

  • Example (application/json;charset=utf-8, application/json):

{"messages":[{"ts":"2020-03-15T19:58:33.695Z","msg":"OQLMXoEA4iv-aR46puPJuY1Rdoc1KY0gfq8oElJwtAs","msgId":"p8PCiGPZ"}],"nextMessageId":null}

DELETE /connection/:connectionId/messages/:messageId

Delete message

Captures:

  • connectionId: Recipient connection ID - unique connection ID to be used by connection recipient
  • messageId: Message ID - unique message ID to be used by connection recipient

Response:

  • Status code 200

  • Headers: []

  • Supported content types are:

    • application/json;charset=utf-8
    • application/json

  • Example (application/json;charset=utf-8, application/json):

POST /connection/:senderConnectionId/messages

Send message

Captures:

  • senderConnectionId: Sender connection ID - unique connection ID to be used by connection sender

Request:

  • Supported content types are:

    • application/json;charset=utf-8
    • application/json

  • Example (application/json;charset=utf-8, application/json):

{"msg":"OQLMXoEA4iv-aR46puPJuY1Rdoc1KY0gfq8oElJwtAs"}

Response:

  • Status code 201

  • Headers: []

  • Supported content types are:

    • application/json;charset=utf-8
    • application/json

  • Example (application/json;charset=utf-8, application/json):