How to Get a GPTMail API Key: Public Test Keys, Domain Rewards, and Credit Quotas

GPTMail's API Key acquisition methods have been updated: the public test Key changes daily, rewards for submitting public domains differ depending on login status, and personal quotas are managed through credits.

Content verified: November 15, 2026. Original publication date retained; for current pricing, quotas, and availability, please refer to the current descriptions at the linked pages.

Official GPTMail product image; check the API page for quotas and keys.
Official GPTMail product image; check the API page for quotas and keys. Click the image to view the original.

First, choose the option that suits you

  • Temporary trial: get the public test key of the day fromthe latest GPTMail API documentation. It is a test quota shared by all users and is not suitable as a stable production credential.
  • Personal or project use: log in to GPTMail and check your personal key, credits, and redeemable quota on the API page. Do not put the key in web front-ends, public repositories, or blog examples.
  • Have an idle root domain: configure MX records according to the rules and submit the public domain. Public submission means this suffix can be used by other users.

Submitting a domain: don't confuse the two rewards

Under the current rules, submitting a new public domain while logged out earns a key with a 20,000-call quota; submitting while logged in earns 200 credits. Each domain can only be rewarded once. The MX target is now email.chatgpt.org.uk. For the full steps, see theBring Your Own Domain guide。

Credits and LDC

The current page offers ways to earn credits such as daily check-ins and public domain contributions, and also supports earning credits through LDC. The specific exchange rate, purchasable quota, and eligibility are subject to what the API page displays. The former store.chatgpt.org.uk store has been discontinued; do not follow the old article to buy GPTMail keys there.

Things to keep in mind after getting the key

  • The public test key changes daily; running out of the shared quota does not mean the entire email service is unavailable.
  • Call count, API rate limits, and email retention time are three different limits. On a 429, wait for Retry-After instead of retrying in an immediate loop.
  • The public API key does not grant access to private domains or login-exclusive domains.
  • Store the key only on your own server or in controlled scripts; always use placeholders in examples and never expose real keys.

Latest access point and usage lookup:the latest GPTMail API documentation. Emails are retained for at most 24 hours; save important information promptly according to your own security requirements.

阅读中文原文 / Read the Chinese original

上一篇 下一篇

评论与讨论

还没有评论,欢迎留下第一条讨论

有想法?一起聊聊
欢迎补充信息、提出问题或分享你的使用体验。
写下评论
comment url