Skip to content
v1.0.0
OpenAPI 3.0.3

Comments Notification API

This API specification describes the webhook endpoint that plugin servers must implement to receive notification events from the Stripo Email Editor.

The editor will POST notification events to the configured plugin URL when specific actions occur (e.g., comments created, replied, resolved, or viewed).

Authentication: HTTP Basic Authentication is required. The editor will send credentials configured in the plugin settings.

Important: All event type and subtype values use UPPERCASE with underscores.

Server:https://{YOUR_PLUGIN_NOTIFICATION_URL}

Plugin notification webhook endpoint (configure in plugin settings)

Client Libraries

Receive plugin notification events

​

Endpoint to receive notification events from the Stripo Email Editor.

Your plugin server must implement this endpoint and respond with either:

  • 200 OK (with optional response body)
  • 204 No Content (no response body)

Any other status code will be treated as an error.

Body·

required
application/json
  • Unix timestamp in milliseconds when the event was created

  • Event-specific details. The structure depends on the type and subtype.

    Details for a comment creation event

    • User ID of the comment author (string format)

    • Unique identifier of the created comment

    • Text content of the comment

    • Unique identifier of the email template

    • List of user IDs tagged in the comment (optional, string array)

  • Unique identifier of the plugin this event is for

  • Specific event type within the category

    values
    COMMENT_CREATEDCOMMENT_REPLIEDCOMMENT_RESOLVEDCOMMENT_VIEWED
  • High-level event category (always "EDITOR_COMMENTS" for comment events)

Responses

  • Event received and processed successfully

    application/json
  • Event received and processed successfully (no content)

  • Bad request - invalid event format or missing required fields

    Standard error response format

    • Error type or category

    • Detailed error message

    application/json
  • Unauthorized - invalid or missing credentials

    Standard error response format

    • Error type or category

    • Detailed error message

    application/json
  • Internal server error

    Standard error response format

    • Error type or category

    • Detailed error message

    application/json
Request Example for post/notifications
curl 'https://{YOUR_PLUGIN_NOTIFICATION_URL}/notifications' \
  --request POST \
  --header 'Content-Type: application/json' \
  --header 'Authorization: Basic username:password' \
  --data '{
  "createdOn": 1699564800000,
  "type": "EDITOR_COMMENTS",
  "subtype": "COMMENT_CREATED",
  "pluginId": "my-plugin-123",
  "details": {
    "emailId": "email-456",
    "commentId": "comment-789",
    "commentAuthorId": "user-001",
    "commentText": "This looks great!",
    "taggedUserIds": [
      "user-002",
      "user-003"
    ]
  }
}'
{
  "message": "Event processed successfully"
}

Models

​
  • Unix timestamp in milliseconds when the event was created

  • Event-specific details. The structure depends on the type and subtype.

    Details for a comment creation event

    • User ID of the comment author (string format)

    • Unique identifier of the created comment

    • Text content of the comment

    • Unique identifier of the email template

    • List of user IDs tagged in the comment (optional, string array)

  • Unique identifier of the plugin this event is for

  • Specific event type within the category

    values
    COMMENT_CREATEDCOMMENT_REPLIEDCOMMENT_RESOLVEDCOMMENT_VIEWED
  • High-level event category (always "EDITOR_COMMENTS" for comment events)

​

Details for a comment creation event

  • User ID of the comment author (string format)

  • Unique identifier of the created comment

  • Text content of the comment

  • Unique identifier of the email template

  • List of user IDs tagged in the comment (optional, string array)

​

Details for a comment reply event

  • Unique identifier of the reply comment

  • Text content of the reply

  • Unique identifier of the email template

  • User ID of the author who created the initial comment (string format)

  • Unix timestamp in milliseconds when the initial comment was created

  • Text content of the initial comment in the thread

  • Total number of replies in the thread

  • User ID of the reply author (string format)

  • Unique identifier of the parent comment thread

  • List of user IDs tagged in the reply (optional, string array)

  • List of all user IDs participating in the thread (optional, string array)

​

Details for a comment resolution event

  • User ID of the original comment author (string format)

  • Unique identifier of the resolved comment

  • Text content of the resolved comment

  • Unique identifier of the email template

  • User ID of the person who resolved the comment (string format)

  • Unique identifier of the comment thread

  • List of all user IDs participating in the thread (optional, string array)

​

Details for a comment view event

  • Unique identifier of the viewed comment

  • Unique identifier of the email template

  • Unique identifier of the comment thread

  • User ID of the person who viewed the comment (string format)

​

Standard error response format

  • Error type or category

  • Detailed error message