QUICKTXN / DOCUMENTATION

Access and API keys

Get an account scoped to QuickTxn, with explicit chain access and a fee policy that matches your integration.

Request access

Contact the Hello Moon team through the official Discord or your existing account contact. Include application name, desired chain and network, application region, expected requests per second, and whether you already use QuickTxn. Never post credentials, signed private transactions, or wallet secrets in a public channel.

What onboarding provides

• Your assigned endpoint and verified physical region.
• A customer API credential delivered securely.
• Approved chain IDs, submission enablement, limits, and fee terms.
• A tested fallback, if available, and a support contact.

hmqt- and hmse-

New QuickTxn credentials use the hmqt-<customer>-<random> format as the product migration rolls out. Sherwood Express retains hmse- credentials. A prefix is a product identifier, not a wallet or blockchain license. Use a separately issued key for each product. Existing QuickTxn customers should keep their current assigned credential until a replacement has been tested and the migration confirmed.

Send the key in a header

X-Api-Key: hmqt-YOUR_CUSTOMER-YOUR_SECRET

Store credentials in a secret manager and inject them into server-side requests. Do not put them in query strings, static sites, source control, analytics, or support screenshots. This documentation makes no API calls from your browser and never asks for a key.

Rotate and revoke

1. Request a replacement with the same explicitly approved product, chain and fee policy.
2. Validate discovery and a controlled integration using the new credential.
3. Switch clients and confirm the old key is no longer in use.
4. Have support revoke the old credential and verify rejection at every assigned endpoint.

Edge caches refresh asynchronously. Do not assume instantaneous revocation or a fixed propagation SLA; support must confirm completion across your regions. If a key leaks, request immediate revocation and stop using it. Never undo a revocation as part of endpoint rollback.

Commercial terms

Access, rate limits, and chain-specific fees are confirmed during onboarding. Existing untipped agreements are preserved only for the accounts explicitly granted that capability. There is no published universal price or success-based fee guarantee in this release.