Skip to main content
Three pages under Admin cover the developer and oversight side of your organization: API for keys and webhooks, Notifications for alert emails, and Audit Logs for a running record of what happened. This page walks through each one.

​
Who sees Admin

The Admin section of the sidebar shows only the pages your role allows. Each page below has its own permission, so two people on the same team can see different items. If you hold only one of the API permissions, the API page shows only the matching tabs. If you cannot see a page you need, ask an organization owner to adjust your role. See Organizations and memberships.

​
API keys

Open Admin > API and stay on the API keys tab. A summary at the top shows your total keys, how many are active, and total requests. You can search keys by name and filter by Active or Revoked.

​
Create a key

  1. Choose to create a new key.
  2. Enter a Key Name, such as “Production API Key”, and an optional description of what the key is for.
  3. Pick at least one permission:
    • Read lists and views resources.
    • Write creates and updates resources.
    • Delete deletes resources.
  4. Create the key. The full key appears once, with a Copy button and a sample request.
Save the key somewhere secure before you press Done. We cannot show it again. Afterward the table shows only the key prefix, so use the prefix to tell keys apart. New keys are limited to 100 requests per hour. Send the key in the X-API-Key header; see the API reference introduction for everything you can call.

​
Review, edit, and revoke

  • Open a key to see its prefix, status, rate limit, created and last used dates, permissions, usage statistics (total requests, success rate, rate-limited requests, average response time), and its last ten requests.
  • Edit a key to change its name or description.
  • Revoke a key to block every request that uses it, immediately. This cannot be undone. Create a new key to replace it, then update the system that used the old one.
To rotate a key, create the new one first, switch your integration over, then revoke the old one so nothing breaks in between.

​
Webhook endpoints

Webhooks send events to your own system as they happen. Open the Webhooks tab on Admin > API. The top of the tab shows your endpoint count and, for the last 24 hours, deliveries, success rate, and failures.

​
Add an endpoint

  1. Choose to add an endpoint.
  2. Enter an Endpoint Name (for example “Production”) and the Webhook URL that will receive events.
  3. Select the events you want. The list covers message sent, delivered, failed and replied; link clicked; email delivered, bounced, complained, unsubscribed and clicked; and contact list analyzed.
  4. Leave Enabled on and save.

​
The signing secret

When the endpoint is created, a Webhook Secret appears once. Save it now, store it in your environment variables, never commit it to version control, and use it to verify each event’s signature. The signature validation guide shows how. To replace a secret, choose Rotate Secret on the endpoint. The old secret stops working immediately, so update your receiver at the same moment.

​
Test, edit, and delete

  • Test sends a sample event so you can confirm your receiver responds.
  • Edit changes the name, URL, events, or enabled setting.
  • Delete removes the endpoint and all of its delivery history. This cannot be undone.

​
Endpoints that keep failing

If an endpoint fails repeatedly, we switch it off and mark it Disabled after repeated failures, with the date the failures began. Fix your URL, then choose Re-enable. Events that occurred while it was off are not resent. A successful test also clears the failure marker.

​
Deliveries

The Deliveries tab lists every event we tried to send, with its event type, status (pending, delivered, or failed), time, HTTP status, and number of attempts. Filter by event type or status. Open a delivery to see the URL, the payload we sent, and the response we got back. For a failed delivery, choose Retry to send it again.

​
Notifications

Admin > Notifications controls which alert emails your organization receives. Account sign-in and registration emails are not affected by these settings. In-app notifications, shown by the bell icon, continue independently of the email choices here.
  1. Under Recipients, add up to 10 email addresses.
  2. Under Events, switch on each address for each event it should receive. Events with no recipients added show a prompt to add one first.
  3. Choose Save changes. Send test email confirms your recipients can receive mail.
Events are grouped as follows: Some billing events always go to organization owners, whatever you choose here. Two events have extra settings:
  • Project report delivered sends automatically after a project finishes sending. Select up to three dispatch times of 1, 3, 6, 12, or 24 hours after the send completes. With none selected, no automatic report emails go out.
  • Low wallet balance fires when your balance drops below a dollar amount you set. Leave it blank to turn the alert off.

​
Audit Logs

Admin > Audit Logs opens the Activity Logs page, a newest-first feed of what has happened in your organization. Each entry has a description, how long ago it happened, and the organization it belongs to. The feed records these kinds of activity:
  • Project created
  • 10DLC campaign registered
  • Brand registered
  • Contact list uploaded
  • Organization created
  • User created
It shows 50 entries at a time; choose Load More to go further back. The page has no filters or export, so for a spreadsheet of your sending data, use Data exports.