See llms.txt for all machine-readable content.
Save yourself the work of writing custom integrations for Mailersend and SimpleHash and use n8n instead. Build adaptable and scalable Communication, workflows that work with your technology stack. All within a building experience you will love.


In n8n, click the "Add workflow" button in the Workflows tab to create a new workflow. Add the starting point – a trigger on when your workflow should run: an app event, a schedule, a webhook call, another workflow, an AI chat, or a manual trigger. Sometimes, the HTTP Request node might already serve as your starting point.
| POST | Send email | This endpoint allows you to send an asynchronous email. /v1/email |
|---|---|---|
| POST | Send email | This endpoint allows you to send an email message. /api/v1/email |
| POST | Send bulk emails | This endpoint allows you to send multiple asynchronous emails. /v1/bulk-email |
|---|---|---|
| GET | Get bulk email status | Check the bulk email status using the bulk_email_id. /v1/bulk-email/{bulk_email_id} |
| POST | Send bulk email | Send multiple emails in a single request. /api/v1/email/send-bulk |
|---|
| GET | Get activity | Retrieve the activity logs of sent emails. /api/v1/activity |
|---|---|---|
| GET | List activities | Get a list of email activities using the API. /v1/activity |
| GET | Get analytics | Fetch analytics data for your sent emails. /api/v1/analytics |
|---|
| GET | List domains | Get a list of validated domains for your account. /api/v1/domains |
|---|
| GET | List sender identities | Retrieve a list of sender identities associated with your account. /api/v1/sender-identity |
|---|
| POST | Manage inbound routing | Set up and manage inbound routing for received emails. /api/v1/inbound |
|---|---|---|
| GET | List inbound routes | Retrieve information about multiple inbound routes. /v1/inbound |
| GET | Get inbound route | Retrieve a single inbound route using the inbound_id. /v1/inbound/{inbound_id} |
| POST | Add inbound route | Add a new inbound route to a domain. /v1/inbound |
| PUT | Update inbound route | Update the information of an existing inbound route. /v1/inbound/{inbound_id} |
| DELETE | Delete inbound route | Use this request to delete an inbound route. /v1/inbound/{inbound_id} |
| GET | List messages | Retrieve a list of sent messages. /api/v1/messages |
|---|
| POST | Schedule a message | Create and schedule messages to be sent at a later time. /api/v1/message-schedules |
|---|
| GET | List recipients | Get a list of recipients for the emails you've sent. /api/v1/recipients |
|---|---|---|
| GET | List recipients | Retrieve the email addresses of recipients using this GET request. /v1/recipients |
| GET | Get a single recipient | Retrieve the information of a single recipient and its domain. /v1/recipients/{recipient_id} |
| DELETE | Delete recipient | Delete the information of a single recipient and its domain using this DELETE request. /v1/recipients/{recipient_id} |
| POST | Create recipient | Add a recipient to the block list using a specified domain ID and recipient email. /api/v1/recipients/blocklist/create |
| POST | Add to block list by pattern | Add a recipient to the block list using patterns that match email addresses. /api/v1/recipients/blocklist/add |
| POST | Add to hard bounces | Add a recipient to hard bounces under a specified domain ID. /api/v1/recipients/hardbounces/add |
| POST | Add to spam complaints | Add a recipient to spam complaints using their email address and domain ID. /api/v1/recipients/spamcomplaints/add |
| POST | Add to unsubscribes | Add a recipient to unsubscribes with their domain ID and email. /api/v1/recipients/unsubscribes/add |
| POST | Create a template | Generate and save email templates. /api/v1/templates |
|---|
| POST | Manage webhooks | Set up and configure webhooks for your application. /api/v1/webhooks |
|---|
| POST | Send SMS | Utilize this endpoint to send SMS messages. /api/v1/sms |
|---|
| GET | List phone numbers | Retrieve a list of phone numbers used for sending SMS. /api/v1/sms-numbers |
|---|
| GET | List SMS messages | Get a record of SMS messages sent from your account. /api/v1/sms-messages |
|---|
| GET | List users | Retrieve a list of users in your MailerSend account. /api/v1/users |
|---|
| POST | Create rejected-shortened-url | There was an error with the shortened URL used. /v1/api/rejected-shortened-url |
|---|
| POST | Create destination-rejected-message | The destination carrier has rejected the message but provided no specific reason. /v1/api/destination-rejected-message |
|---|
| POST | Create destination-rejected-message-size-invalid | Carrier has rejected for message length is invalid or too long. /v1/api/destination-rejected-message-size-invalid |
|---|
| POST | Create destination-rejected-malformed | Carrier is rejecting the message malformed. /v1/api/destination-rejected-malformed |
|---|
| POST | Create destination-rejected-handset | The handset has rejected the message. /v1/api/destination-rejected-handset |
|---|
| POST | Create destination-spam-detected | The Carrier is reporting this message as blocked for SPAM. /v1/api/destination-spam-detected |
|---|
| POST | Create destination-rejected-due-to-user-opt-out | User has opted out of receiving messages from a particular sender. /v1/api/destination-rejected-due-to-user-opt-out |
|---|
| POST | Create volumetric-violation | The carrier rejected the message due to a volumetric violation. /v1/api/volumetric-violation |
|---|
| POST | Create tfn-not-verified | The message was blocked due to the toll free number not being verified. /v1/api/tfn-not-verified |
|---|
| POST | Create temporary-app-error | An application within the MailerSend service is experiencing a temporary error. /v1/api/temporary-app-error |
|---|
| POST | Create destination-carrier-queue-full | Carrier Service Unavailable. /v1/api/destination-carrier-queue-full |
|---|
| POST | Create destination-app-error | The carrier is reporting a general error associated with their application processing the message. /v1/api/destination-app-error |
|---|
| POST | Create message-send-failed | The destination carrier has reported a general service failure with sending the message. /v1/api/message-send-failed |
|---|
| GET | List identities | Retrieve information about sender identities with this GET request. /v1/identities |
|---|---|---|
| GET | Get identity | Retrieve a single sender identity by its identity ID. /v1/identities/{identity_id} |
| GET | Get identity by email | Retrieve a single sender identity by email. /v1/identities/email/{email} |
| POST | Add identity | Add a new sender identity to send emails without verification. /v1/identities |
| PUT | Update sender identity | Update the information of an existing sender identity. /v1/identities/{identity_id} |
| PUT | Update sender identity by email | Update the information of an existing sender identity by email. /v1/identities/email/{email} |
| DELETE | Delete identity | If you want to delete a sender identity, use this DELETE request. /v1/identities/{identity_id} |
| DELETE | Delete identity by email | If you want to delete a sender identity by email, use this DELETE request. /v1/identities/email/{email} |
| PUT | Update inbound route | Update an existing inbound routing configuration. /api/v1/inbound/update |
|---|
| GET | Get recipients | Retrieve the recipients in a blocklist of an account or domain by passing the blocklist ID with this GET request. /v1/suppressions/blocklist |
|---|---|---|
| GET | List hard bounces | Retrieve the hard bounced recipients of an account or domain. /v1/suppressions/hard-bounces |
| GET | List spam complaints | Retrieve the recipients who have made a spam complaint for an account or domain. /v1/suppressions/spam-complaints |
| GET | List unsubscribes | Retrieve the unsubscribed recipients from an account or domain. /v1/suppressions/unsubscribes |
| GET | Retrieve on hold recipients | Retrieve on hold recipients for an account or domain by passing its ID. /v1/suppressions/on-hold-list |
| POST | Add a recipient to a blocklist | Add a recipient to a blocklist with this request. /v1/suppressions/blocklist |
| POST | Add hard bounce | Add a hard bounce for one or more recipients. /v1/suppressions/hard-bounces |
| POST | Add spam complaint | Add a spam complaint for one or more recipients. /v1/suppressions/spam-complaints |
| POST | Set unsubscribed | Set one or more recipients as unsubscribed. /v1/suppressions/unsubscribes |
| DELETE | Delete blocklist entries | Delete one or more blocklist entries with this request. /v1/suppressions/blocklist |
| DELETE | Delete hard bounces | Delete one or more hard bounces from recipients by passing the hard bounces IDs. /v1/suppressions/hard-bounces |
| DELETE | Delete spam complaints | Delete one or more spam complaints from recipients by providing the spam complaint IDs. /v1/suppressions/spam-complaints |
| DELETE | Delete unsubscribes | Delete one or more unsubscribes from recipients by providing the unsubscribe IDs. /v1/suppressions/unsubscribes |
To set up Mailersend integration, add the HTTP Request node to your workflow canvas and authenticate it using a generic authentication method. The HTTP Request node makes custom API calls to Mailersend to query the data you need using the API endpoint URLs you provide.
See the example hereThese API endpoints were generated using n8n
n8n AI workflow transforms web scraping into an intelligent, AI-powered knowledge extraction system that uses vector embeddings to semantically analyze, chunk, store, and retrieve the most relevant API documentation from web pages. Remember to check the Mailersend official documentation to get a full list of all API endpoints and verify the scraped ones!
| GET | Get NFT by Token ID | Retrieve a specific NFT using its Token ID. /reference/nft-by-token_id-1 |
|---|---|---|
| GET | Get NFT by Inscription Number | Retrieve a specific NFT using its Inscription Number. /reference/nft-by-inscription-number |
| GET | Get NFTs by Token List | Retrieve NFTs using a list of token identifiers. /reference/nfts-by-token-list |
| GET | Get NFTs by Collection ID / Mint | Retrieve NFTs associated with a specific Collection ID or Mint. /reference/nfts-by-collection |
| GET | Get NFTs by Contract | Retrieve NFTs associated with a specific contract. /reference/nfts-by-contract |
| GET | Get NFTs by Contract Owner(s) | Retrieve NFTs owned by specific contract owners. /reference/nfts-by-contract-owners |
| GET | Get NFTs by POAP Event ID | Retrieve NFTs linked to a specific POAP Event ID. /reference/nfts-by-poap-event-id |
| GET | Get NFTs by Wallet(s) | Retrieve NFTs owned by specific wallets. /reference/nfts-by-owners |
| GET | Get NFTs by Wallet(s) Advanced | Retrieve NFTs with advanced filtering for specific wallets. /reference/nfts-by-wallets-v2 |
| GET | Get Native Token Balances by Wallet(s) | Retrieve the native token balances of specified wallets. /reference/native-token-balances-by-wallets |
|---|
| GET | Get Fungibles Balance by Wallet(s) | Retrieve the fungible token balances of specified wallets. /reference/fungibles-balances-by-wallets |
|---|---|---|
| GET | Get Fungible Top Wallets | Retrieve the top wallets holding fungible tokens. /reference/fungible-top-wallets |
| GET | Get fungible sales & transfers by wallets | Retrieve sales and transfers of fungible tokens associated with specific wallets. /reference/fungibles-sales-transfers-by-wallets |
| GET | Get sales & transfers by fungible | Fetches sales and transfers related to a specific fungible token. /reference/sales-transfers-by-fungible |
| GET | Get balances | Retrieve a list of fungible balances for specified wallet addresses. /api/v0/fungibles/balances?chains={chains}&wallet_addresses={wallet_addresses} |
| GET | Get fungible sales & transfers by wallet(s) | Provides sales and transfers information for the specified wallet(s). /reference/fungible-sales-transfers-by-wallets |
| GET | Get Sales & Transfers by Wallet(s) | Retrieve sales and transfers associated with specific wallets. /reference/transfers-by-wallets |
|---|---|---|
| GET | Get Sales & Transfers by NFT | Retrieve sales and transfer records for a specific NFT. /reference/transfers-by-nft |
| GET | Get sales & transfers by contract owners | Retrieve sales and transfer records associated with specific contract owners. /reference/sales-transfers-by-contract-owners |
| GET | Get Collections by ID(s) | Retrieve collections using their identifiers. /reference/collections-by-ids |
|---|---|---|
| GET | Get Collections by Wallet(s) | Retrieve collections associated with specific wallets. /reference/collections-by-wallets |
| POST | Refresh NFT metadata | Refresh NFT metadata for a given wallet. /reference/refresh-nft-metadata |
|---|---|---|
| POST | Refresh Collection metadata | Refresh metadata for a given collection. /reference/refresh-collection-metadata |
| POST | Refresh Contract metadata | Refresh metadata for a given contract. /reference/refresh-contract-metadata |
| POST | Refresh Wallet metadata | Refresh metadata for a given wallet. /reference/refresh-wallet-metadata |
| GET | Get wallet valuation | Fetch the valuation of a specified wallet based on its NFTs. /reference/wallet-value |
| GET | Get wallet valuation batch | Retrieve the valuation for multiple wallets in a single request. /reference/wallet-valuation |
| POST | Send Spam Report | Send a report for spam content. /reference/send-spam-report |
|---|
| GET | List Webhook | Get a list of all webhooks. /reference/list-webhook |
|---|---|---|
| POST | Create Webhook | Create a new webhook subscription. /reference/create-webhook |
| PATCH | Update Webhook | Update an existing webhook subscription. /reference/update-webhook |
| DELETE | Delete Webhook | Delete an existing webhook subscription. /reference/delete-webhook |
| GET | Get Kafka Topic Schema | Fetch the schema for a given Kafka topic. /reference/get-kafka-topic-schema |
|---|
| GET | Get contracts by deployer | This endpoint provides a list of EVM-based NFT contracts deployed by an address. /api/v0/contracts_by_deployer |
|---|---|---|
| GET | Get contracts by wallets | Retrieve a summary of NFT contract ownership for specified wallet addresses on designated chains. /reference/contracts-by-wallets |
| GET | Get contracts by wallets | Retrieve NFT contracts associated with specified wallet addresses. /api/v0/nfts/contracts_by_wallets |
| GET | List contracts by owners | Retrieve contracts associated with specific owners. /reference/contracts-by-owner |
| GET | List contracts by deployers | Retrieve contracts deployed by specific deployers. /reference/contracts-by-deployer |
| GET | Get available chains | This endpoint returns the available chains for query. /api/v0/chains |
|---|---|---|
| GET | Get Available Chains | Retrieve a list of available blockchain networks. /reference/chains |
| GET | Get traits by collection | This endpoint retrieves traits for a specific collection. /api/v0/traits-by-collection |
|---|---|---|
| GET | Get Traits by Collection | Retrieve traits associated with a specific collection. /reference/traits-by-collection |
| GET | Get trait floor prices by NFT | This endpoint provides the floor prices for specific traits associated with an NFT. /api/v0/trait-floor-prices-by-nft |
|---|---|---|
| GET | Get trait floor prices by NFT | Obtain the floor prices for specific traits within NFTs. /reference/trait-floor-prices-by-nft |
| GET | Get trait floor price by collection | This endpoint returns the floor price for traits in a collection. /api/v0/trait-floor |
|---|
| GET | Get active listings by NFT | This endpoint provides active listings for a specific NFT. /api/v0/listings-by-nft |
|---|---|---|
| GET | Get active listings by collection | This endpoint provides active listings for a specific collection. /api/v0/listings-by-collection |
| GET | Get active listings by contract | This endpoint returns active listings related to a specific contract. /api/v0/listings-by-contract-1 |
| GET | Get active listings by NFT | Fetch currently active listings for specific NFTs. /reference/listings-by-nft |
| GET | Get active listings by wallets | Get active NFT listings associated with specific wallet addresses. /reference/active-listings-by-wallets |
| GET | Get active listings by wallet | This endpoint retrieves active listings associated with a specific wallet. /api/v0/active-listings-by-wallets |
|---|
| GET | Get listing events by NFT | This endpoint retrieves listing events associated with a specific NFT. /api/v0/listing-events-by-nft |
|---|---|---|
| GET | Get listing events by wallet | This endpoint provides listing events for a specific wallet. /api/v0/listing-events-by-wallets |
| GET | Get listing events by collection | This endpoint retrieves listing events for a specific collection. /api/v0/listing-events-by-collection |
| GET | Get listing events by contract | This endpoint provides listing events related to a specific contract. /api/v0/listing-events-by-contract |
| GET | Get listing events by chain | This endpoint retrieves listing events filtered by chain. /api/v0/listing-events-by-chain |
| GET | Get Owners by NFT | Retrieve owners of a specific NFT. /reference/owners-by-nft |
|---|---|---|
| GET | Get Owners by Collection | Retrieve owners of NFTs within a specific collection. /reference/owners-by-collection |
| GET | Get ownership summary by wallets | Retrieve ownership summary for specific wallets. /reference/ownership-summary-by-wallets |
| GET | Get Owners by Contract | Retrieve owners associated with a given contract. /reference/owners-by-contract |
| GET | Get Active Bids By Wallet | Retrieve active bids associated with a specific wallet. /reference/active-bids-by-wallets |
|---|---|---|
| GET | Get Active Bids By Collection | Retrieve active bids associated with a specific collection. /reference/bids-by-collection |
| GET | Get active bids by NFT | Retrieve active bids placed on specific NFTs. /reference/active-bids-by-nft |
|---|
| GET | List sales and transfers by collection | Retrieve sales and transfer data associated with a specific collection. /reference/transfers-by-collection |
|---|---|---|
| GET | List sales and transfers by contract | Retrieve sales and transfer data associated with a specific contract. /reference/transfers-by-contract |
| GET | Get sales & transfers by transaction hash | Fetches sales and transfers based on a transaction hash. /reference/sales-transfers-by-tx-hash |
| GET | Get native token balances | Supports all the same chains as our NFT endpoints, including Bitcoin, Ethereum, Solana, Tezos, Flow, and other EVM chains. /api/v0/native_tokens/balances?chains={chains}&wallet_addresses={wallet_addresses} |
|---|
To set up SimpleHash integration, add the HTTP Request node to your workflow canvas and authenticate it using a generic authentication method. The HTTP Request node makes custom API calls to SimpleHash to query the data you need using the API endpoint URLs you provide.
See the example hereThese API endpoints were generated using n8n
n8n AI workflow transforms web scraping into an intelligent, AI-powered knowledge extraction system that uses vector embeddings to semantically analyze, chunk, store, and retrieve the most relevant API documentation from web pages. Remember to check the SimpleHash official documentation to get a full list of all API endpoints and verify the scraped ones!

Mailersend is an email delivery service that provides developers with a simplified platform to send transactional emails. It offers features like built-in analytics, SMTP integration, email templates, and deliverability optimization, allowing businesses to efficiently manage their email communications.

SimpleHash API grants access to comprehensive NFT data across 40+ chains, encompassing information such as media, floor prices, sales, listings, and additional details.
Yes, Mailersend can connect with SimpleHash using n8n.io. With n8n, you can create workflows that automate tasks and transfer data between Mailersend and SimpleHash. Configure nodes for Mailersend and SimpleHash in the n8n interface, specifying actions and triggers to set up their connection.
Yes, with n8n, you can programmatically interact with Mailersend’s API via pre-defined supported actions or raw HTTP requests. With the HTTP Request node, you create a REST API call. You need to understand basic API terminology and concepts.
Yes, with n8n, you can programmatically interact with SimpleHash’s API via pre-defined supported actions or raw HTTP requests. With the HTTP Request node, you create a REST API call. You need to understand basic API terminology and concepts.
Yes, it is safe to use n8n to integrate Mailersend and SimpleHash. n8n offers various features to ensure the safe handling of your data. These include encrypted data transfers, secure credential storage, RBAC functionality, and compliance with industry-standard security practices (SOC2 compliant). For hosted plans, data is stored within the EU on servers located in Frankfurt, Germany. You can also host it on your own infrastructure for added control.
Learn more about n8n’s security practices here.
To start integrating Mailersend and SimpleHash in n8n, you have different options depending on how you intend to use it:
Unlike other platforms that charge per operation, step, or task, n8n charges only for full workflow executions. This approach guarantees predictable costs and scalability, no matter the complexity or volume of your workflows.

Handle branching, merging and iteration easily. Pause your workflow to wait for external events.
Re-run single steps to test changes in no time. And pin your data to avoid generating trigger events every time you execute.
Your data is displayed alongside your settings, making edge cases easy to track down.
Use 1000+ workflow templates available from our core team and our community.
Copy and paste, easily import and export workflows.
n8n makes complex workflows easy to build, and versatile enough for me to add my own 'secret sauce.'

I have found the holy grail of automation.

n8n’s integration with third-party services is absolutely mind-blowing. It’s like a Swiss army knife for automation.
n8n is the tool that turns 'I have an idea' into 'it's running in production' faster than anything else.

Anything is possible with n8n. I think the cloud version is great, they are doing amazing stuff.
n8n’s integration with third-party services is absolutely mind-blowing. It’s like a Swiss army knife for automation.

Thank you to the n8n community. I did the beginners course and promptly took an automation WAY beyond my skill level.
I love the flexibility of n8n and how it lets different applications work together in a single workflow.
n8n is the glue that holds many of our systems together.
I can move fast, go deep when things get complex, and never feel boxed in.
