// website builders and cms
Via APIMemberful email verification with pingutil
Memberful sites that allow free registration collect members on temp-mail and mistyped addresses, and those members then get your newsletters and posts and drag down deliverability. Memberful has no pre-signup hook, so the check runs after: the member_signup webhook reaches your endpoint, pingutil verifies the email, and a memberUpdate mutation stores the result in the member's metadata.
Where it connects: Memberful webhook, member_signup event, plus the GraphQL memberUpdate mutation
What goes wrong without it
- We opened free registration on Memberful and got a wave of members on disposable inboxes.
- Our member newsletter bounce rate went up as soon as free signups were turned on.
- There is no way to see which free members are worth a follow-up and which are junk.
What you can do with Memberful and pingutil
Store email status in member metadata
Write email_status and email_reason with memberUpdate. Metadata is additive, so it does not overwrite other keys you keep on the member.
Keep bad addresses out of the newsletter
When you sync members to your email tool, skip anyone whose metadata says invalid, so free registrations cannot hurt the list.
Review risky free members
Catch-all and randomized addresses come back risky. Review them before granting anything beyond the free tier.
Set it up
- 1
In Memberful, add a webhook endpoint for the member_signup event and copy the webhook secret.
- 2
Create a custom application under Settings → Custom applications to get an API key for https://ACCOUNT-URL.memberful.com/api/graphql.
- 3
Verify X-Memberful-Webhook-Signature as an HMAC-SHA256 hex digest of the raw body with the webhook secret.
- 4
Respond 200, then verify the member's email with pingutil.
- 5
Write the result with the memberUpdate mutation and check it in the GraphQL API Explorer.
require "sinatra"
require "json"
require "net/http"
require "openssl"
require "rack/utils"
def pingutil_verify(email)
uri = URI("https://pingutil.com/v1/verify")
req = Net::HTTP::Post.new(uri, "Authorization" => "Bearer #{ENV.fetch('PINGUTIL_KEY')}", "Content-Type" => "application/json")
req.body = { email: email }.to_json
res = Net::HTTP.start(uri.host, uri.port, use_ssl: true, open_timeout: 5, read_timeout: 25) { |http| http.request(req) }
res.is_a?(Net::HTTPSuccess) ? JSON.parse(res.body) : nil # 429 / 5xx: fail open
rescue StandardError
nil # timeout or network error: fail open
end
def memberful_update(member_id, result)
metadata = { email_status: result["status"], email_reason: result["reason"] }.to_json
query = "mutation { memberUpdate(id: #{Integer(member_id)}, metadata: #{metadata.to_json}) { member { id metadata } } }"
uri = URI("https://#{ENV.fetch('MEMBERFUL_ACCOUNT')}.memberful.com/api/graphql")
req = Net::HTTP::Post.new(uri, "Authorization" => "Bearer #{ENV.fetch('MEMBERFUL_API_KEY')}", "Content-Type" => "application/json")
req.body = { query: query }.to_json
Net::HTTP.start(uri.host, uri.port, use_ssl: true) { |http| http.request(req) }
end
post "/webhooks/memberful" do
raw = request.body.read
computed = OpenSSL::HMAC.hexdigest("SHA256", ENV.fetch("MEMBERFUL_WEBHOOK_SECRET"), raw)
halt 401 unless Rack::Utils.secure_compare(computed, request.env["HTTP_X_MEMBERFUL_WEBHOOK_SIGNATURE"].to_s)
event = JSON.parse(raw)
if event["event"] == "member_signup"
member = event["member"] # confirm the shape against a test delivery
Thread.new do
result = pingutil_verify(member["email"])
memberful_update(member["id"], result) if result
end
end
status 200
endWhat to do with each result
| pingutil result | Action in Memberful |
|---|---|
| status: "invalid" | memberUpdate metadata email_status = "invalid"; leave them out of email syncs. |
| status: "risky" | email_status = "risky" with the reason; review before upgrading access. |
| status: "valid" | email_status = "valid". |
| No result (timeout, 429, 5xx) | Write nothing; the member keeps normal access. |
Limits to plan for
- Memberful creates the account before sending member_signup, so this flags members after signup rather than stopping it.
- Memberful advises fetching the latest member from the API instead of trusting webhook order; the payload shape here should be checked against a test delivery.
- Metadata values are strings, with up to 50 keys per member. pingutil verification is limited to 300 addresses a day (3,000 a month) per account. Those are Free plan limits; Enterprise has custom limits.
Memberful documentation
- memberful.com/docs/api-reference/webhooks
- memberful.com/docs/api-reference/webhook-event-reference
- memberful.com/docs/api-reference/memberful-api
Memberful is a trademark of its owner. This integration uses Memberful's documented extension points; it is not an official Memberful app.
Common questions
- Why is the event member_signup and not member.signup?
- Memberful's member events use an object_event naming style (member_signup, member_updated), while most other events use object.event. Match the exact string.
- Can members see the metadata?
- No. Memberful says member metadata is only accessible through the API, not elsewhere on the site.
Stop bad addresses in Memberful today
Sign in with your email, create an API key and paste it into the step above. Test on a few real addresses first: the live demo shows exactly what your Memberful setup will receive.