Get information about the member associated with the current API key (the bot itself).
Use your API key as the Bearer token. You can view your API key and secret in your Zenzap organization API key settings.
HMAC-SHA256 signature for request verification.
HMAC signature of the request.
The signature payload differs by HTTP method:
The signature is calculated as:
/v2/members?limit=10&offset=0)Example for GET request to /v2/members?limit=10:
payload = "/v2/members?limit=10"
signature = HMAC-SHA256(secret, payload)
X-Signature: hex(signature)
Example for POST request with body {"topicId":"123","text":"Hello"}:
payload = '{"topicId":"123","text":"Hello"}'
signature = HMAC-SHA256(secret, payload)
X-Signature: hex(signature)
"a3d5f8e7c2b1d4f6a8e9c7b5d3f1a2e4b6c8d0f2e4a6b8c0d2e4f6a8b0c2d4e6"
Member information retrieved successfully
The member ID
"u@550e8400-e29b-41d4-a716-446655440001"
The member's name
"John Doe"
The member's email address
The member's phone number
"+1234567890"
Optional external identifier if set by your integration
"emp-001"
Unix timestamp in milliseconds when the member was created
1699564800000
Unix timestamp in milliseconds when the member was last updated
1699564800000
The member's status
Pending, Active, Deleted, Archived "Active"