Emailing api subscribers

As a site administrator, you can use the email API subscribers wizard to send messages to all subscribers of all product plans that contain a specific API on your Developer Portal.

Before you begin

You must have administrator access to the Developer Portal to complete this task.

About this task

You can use the email API subscribers wizard to send messages to all subscribers of all product plans that contain a specific API in your Developer Portal community. For each consumer org, you can select whether to email just the owner or all members. Each recipient receives an individual email.

Procedure

  1. If the administrator dashboard is not displayed, click Manage to display it.
  2. Navigate to People > Email subscribers.
  3. Select API subscribers, and click Save.
  4. In the text box, enter the name of the API whose subscribers you want to email. If you start typing in the text box, you can choose from the options that you are given. Click Next.
  5. Select the role of the recipients that you want to send the email to, then click Next.
    • Owners - sends the email to the relevant consumer organization owners.
    • Members - sends the email to all members of the relevant consumer organizations.
  6. Enter the content of the email, subject, and body, and set the Text Format of the email:
    • Basic HTML
    • Plain text
  7. Expand the REPLACEMENTS drop-down, and click Browse available tokens to view which tokens can be added to the subject and body fields for replacement.

    You can select a token to use by either typing it directly, or by clicking in the subject or body field. You are then given a list of available tokens, and you can insert the token that you want. For a reference list of tokens, see Token reference.

  8. Expand the ADDITIONAL EMAIL OPTIONS drop-down to configure any additional settings:
    • Priority: Set the priority of the email. Many email programs ignore a priority setting.
    • Request receipt: Request a read receipt from your emails. Many email programs ignore these requests so it is not a definitive indication of how many people read your email.
    • Additional headers: Set any additional headers to be sent with the email.
  9. Use the remaining check boxes to configure what messages are to be sent and how:
    • Send the message directly by using the Batch API. This option sends the emails directly by the Batch API. If not selected, then the emails are added to the spool and sent out by cron.
    • Send a copy of all messages to the sender. Because emails might contain context-specific tokens, a new email is generated for each recipient with the correct token replacement. This option sends a copy of all generated emails to the sender.
    • Send a copy of the original message to the sender. This option sends a single copy of the original email, subject, and body, without the replacement of any specified tokens.
  10. Click Next.
  11. Confirm that the email is ready to send, then click Next.
  12. If you chose to send the emails by the Batch API, you see a progress page that indicates how many emails were sent. You are then redirected to a summary page that shows the total number of emails that were sent.

    If you chose to spool the delivery of the emails, you are redirected to the summary page that shows the total number of emails that are spooled.

  13. Click Finish.

Results

You successfully sent an email to all members or all owners of each consumer org that contained a subscription to all product plans that contain the chosen API on your Developer Portal.