Participant Page

Site A Sender Participant Page

Loading Site A authentication readiness...

1 Site A Auth2 Send Edoc3 Send Message4 Sender Timeline

Site A Implementation Checklist

Store Site A credentials, including consumer key, consumer secret, auth hash secret, system ID, and message address, on the server.Request a Site A token through /api/v1/auth/token and cache it server-side before sender calls.Prepare EDXML from the server-owned template, keeping raw XML edits visible for advanced validation.Submit the Active Edoc Transaction through /api/v1/edoc/send.Submit the Active Message Transaction through /api/v1/message/send.Inspect the Site A Participant Timeline for Auth, Edoc, Message, and error entries.

Edoc Flow

Customize example.edxml, preview the outgoing XML, then send from Site A.

draft

Editing signed fields or attachment content may invalidate XML signature or digest verification in strict environments.

Implementation Hint: Your service prepares EDXML, validates required fields, preserves attachment metadata, then submits the outbound document as Site A.

Loading example.edxml...

Authenticate Site A before sending the Active Edoc Transaction.

docId

pending

Notation

Received

Decoded XML

Message Flow

Site A sends a safe JSON fixture through the demo server boundary.

draft

Implementation Hint: Your service builds the message payload, chooses the receiver address, sends through Site A credentials, and stores the returned message identifier.

Authenticate Site A before sending the Active Message Transaction.

message_id

pending

Listed

Decoded content

Demo Backend Route Examples

These are app-owned demo server boundaries, not public GDX API routes.

server boundary

POSTAuthenticate Site A/api/v1/auth/token

Request shape

{
  "site": "siteA"
}

Response shape

{
  "site": "siteA",
  "tokenType": "Bearer",
  "expiresIn": 3600,
  "accessToken": "*** masked server-side ***"
}

POSTSend Edoc/api/v1/edoc/send

Request shape

{
  "site": "siteA",
  "xml": "<edXML>...</edXML>"
}

Response shape

{
  "docId": "DOC-...",
  "status": "sent"
}

POSTSend Message/api/v1/message/send

Request shape

{
  "site": "siteA",
  "payload": {
    "from": "00.00.W00:415",
    "tos": [
      "14.00.W00:827"
    ],
    "message_code": "DEMO-YYYYMMDD",
    "message_type": "240183.0.0",
    "content": "{ ... }",
    "contentMode": "json"
  }
}

Response shape

{
  "message_id": "MSG-...",
  "status": "sent"
}