I have setup a new account and not verified my domain. I would like to test and confirm mail-send before proceeding with verification and adding payment information.
For anyone else trying to figure out what "Mailgun Magnificent API" means in a Mailgun HTTP 200-OK API response, it occurs when posting to https://api.mailgun.net/v3/YOUR_DOMAIN_NAME/some/api/endpoint
when /some/api/endpoint
is not a valid Mailgun API endpoint.
If you are using a client library, there's probably a mistake in your Mailgun sender domain setting. Say you've verified the domain mg.example.com with Mailgun. Examples that can result in "Mailgun Magnificent API" (the exact setting name depends on the library):
MAILGUN_DOMAIN = mg.example.com # comment
—this is a common mistake in dotenv files, which don't usually support inline comments; move the # comment
to its own lineMAILGUN_DOMAIN = mg.example.com/mysite
—get rid of the /mysite
partIf you are posting directly to the Mailgun API (or developing a client library), there are some additional ways you might get "Mailgun Magnificent API":
https://api.mailgun.net/v3/mg.example.com
(as noted in another response)https://api.mailgun.net/v3/mg.example.com/massages
(that should be messages with an e)#
or ?
after your domain: https://api.mailgun.net/v3/mg.example.com #/messages
(see the note above about comments in config files)https://api.mailgun.net/v3/mg.example.com/route/to/my/app/messages
Note that you won't see "Mailgun Magnificent API" if YOUR_DOMAIN_NAME is not a valid sending domain you've registered with Mailgun. (In that case, Mailgun instead responds 404-Not Found).
Faced the same issue while sending emails via api by php curl. I solved it by changing API Base URL https://api.mailgun.net/v3/YOUR_DOMAIN_NAME to https://api.mailgun.net/v3/YOUR_DOMAIN_NAME/messages. It's because their api is not only for sending. Hope this helps.