
Security News
npm Adopts OIDC for Trusted Publishing in CI/CD Workflows
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
This is the Amply Python SDK that integrates with the v1 API.
Table of Contents
Obtain your access token from the Amply UI.
pip install amply-mail
Add domains you want to send from
via the Verified Domains tab on your dashboard.
Any emails you attempt to send from an unverified domain will be rejected. Once verified, Amply immediately starts warming up your domain and IP reputation. This warmup process will take approximately one week before maximal deliverability has been reached.
The following is the minimum needed code to send a simple email. Use this example, and modify the to
and from
variables:
import amply
import os
amply.set_access_token(os.environ.get('AMPLY_ACCESS_TOKEN'))
try:
response = amply.email.create({
'to': 'test@example.com',
'from': 'test@verifieddomain.com',
'subject': 'My first Amply email!',
'text': 'This is easy',
'html': '<strong>and fun :)</strong>'
})
except Exception as e:
if hasattr(e, 'errors'):
print('Validation or resource not found error')
print(e.errors)
elif hasattr(e, 'text'):
print('Generic API error: %s' %(e.text))
else:
raise e
Once you execute this code, you should have an email in the inbox of the recipient. You can check the status of your email in the UI from the Search, SQL, or Users page.
Parameter(s) | Description |
---|---|
to, cc, bcc | Email address of the recipient(s). This may be a string Test <test@example.com> , an object {name: 'Test', email: 'test@example.com'} , or an array of strings and objects. |
personalizations | For fine tuned access, you may override the to, cc, and bcc keys and use advanced personalizations. See the API guide here. |
from | Email address of the sender. This may be formatted as a string or object. An array of senders is not allowed. |
subject | Subject of the message. |
html | HTML portion of the message. |
text | Text portion of the message. |
content | An array of objects containing the following keys: type (required), value (required). |
template | The template to use. This may be a string (the UUID of the template), an array of UUID's (useful for A/B/... testing where one is randomly selected), or an object of the format {template1Uuid: 0.25, template2Uuid: 0.75} (useful for weighted A/B/... testing). |
dynamic_template_data | The dynamic data to be replaced in your template. This is an object of the format {variable1: 'replacement1', ...} . Variables should be defined in your template body using handlebars syntax {{variable1}} . |
reply_to | Email address of who should receive replies. This may be a string or an object with name and email keys. |
headers | An object where the header name is the key and header value is the value. |
ip_or_pool_uuid | The UUID of the IP address or IP pool you want to send from. Default is your Global pool. |
unsubscribe_group_uuid | The UUID of the unsubscribe group you want to associate with this email. |
attachments[][content] | A base64 encoded string of your attachment's content. |
attachments[][type] | The MIME type of your attachment. |
attachments[][filename] | The filename of your attachment. |
attachments[][disposition] | The disposition of your attachment (inline or attachment ). |
attachments[][content_id] | The content ID of your attachment. |
clicktracking | Enable or disable clicktracking. |
categories | An array of email categories you can associate with your message. |
substitutions | An object of the format {subFrom: 'subTo', ...} of substitutions. |
send_at | Delay sending until a specified time. An ISO8601 formatted string with timezone information. |
Example
amply.email.create({
'to': 'example@test.com',
'from': 'From <example@verifieddomain.com>',
'text': 'Text part',
'html': 'HTML part',
'personalizations': [{'to': [{'name': 'Override To', 'email': 'test@example.com'}]}],
'content': [{'type': 'text/testing', 'value': 'some custom content type'}],
'subject': 'A new email!',
'reply_to': 'Reply To <test@example.com>',
'template': 'faecb75b-371e-4062-89d5-372b8ff0effd',
'dynamic_template_data': {'name': 'Jimmy'},
'unsubscribe_group_uuid': '5ac48b43-6e7e-4c51-817d-f81ea0a09816',
'ip_or_pool_uuid': '2e378fc9-3e23-4853-bccb-2990fda83ca9',
'attachments': [{'content': 'dGVzdA==', 'filename': 'test.txt', 'type': 'text/plain', 'disposition': 'inline'}],
'headers': {'X-Testing': 'Test'},
'categories': ['Test'],
'clicktracking': True,
'substitutions': {'sub1': 'replacement1'},
'send_at': datetime.datetime.utcnow().replace(tzinfo=datetime.timezone.utc).isoformat()
})
FAQs
This is the Amply Python SDK that integrates with the v1 API.
We found that amply-mail demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
npm now supports Trusted Publishing with OIDC, enabling secure package publishing directly from CI/CD workflows without relying on long-lived tokens.
Research
/Security News
A RubyGems malware campaign used 60 malicious packages posing as automation tools to steal credentials from social media and marketing tool users.
Security News
The CNA Scorecard ranks CVE issuers by data completeness, revealing major gaps in patch info and software identifiers across thousands of vulnerabilities.