Skip to main content
GET
/
api
/
v1
/
agents
/
discord
/
bot-metadata
Discord signal bot metadata (signal-group setup)
curl --request GET \
  --url https://mcp.echozero.app/api/v1/agents/discord/bot-metadata \
  --header 'Authorization: Bearer <token>'
{
  "success": true,
  "data": {
    "applicationId": "1234567890123456789",
    "inviteUrl": "<string>",
    "botUsername": "EchoZeroSignalBot"
  }
}

Authorizations

​
Authorization
string
header
required

User JWT access token issued by POST /api/auth/verify or POST /api/auth/social/verify. Routes that accept both auth modes declare api-key and bearer-jwt security schemes.

Headers

​
x-signature
string

HMAC-SHA256 signature: HMAC-SHA256(secretKey, timestamp + METHOD + path + body). Optional -- when omitted, HMAC verification is skipped.

​
x-timestamp
string

Request timestamp in epoch milliseconds. Required when x-signature is provided. Rejected if drift exceeds 5 minutes.

Response

Discord bot metadata for in-portal setup.

​
success
boolean
required
Example:

true

​
data
object
required

Endpoint-specific payload