Left Column: Action Steps #

1. Locate the Official Portal Navigate directly to https://gmgn.ai or use the official app store link. Crucially, the partnership API application process is initiated only after you have a fully verified account. Do not search for “GMGN API” directly, as this can lead to phishing sites mimicking developer portals.

2. Account Registration & Referral Application Click ‘Sign Up’ on the official website or within the app. Use a secure, unique email address. During registration, you will be prompted for a referral code. This is where you input: LH369. This code is essential as it can unlock initial partnership-tier benefits and flags your account for the API onboarding path.

3. Complete Identity Verification (KYC) This is the most critical step for API access. Navigate to your account settings or security center. You will need to provide:

   • A government-issued ID (Passport or Driver’s License).
   • A real-time selfie for liveness detection.
   • Proof of address (if required for your region).
   • Risk Tip: Never submit KYC documents through email or unofficial channels. The entire process must occur within the secured, encrypted environment of the official GMGN app or website.

4. Enable Advanced Security Features Before applying for API keys, fortify your account. Mandatory steps include:

   • Enabling Two-Factor Authentication (2FA) using an app like Google Authenticator or Authy.
   • Setting up withdrawal allowlists (whitelists).
   • Reviewing all connected devices and active sessions.

5. Navigate to the Developer/API Section Once your account is fully verified and secured (this may take 24-48 hours), look for “Developer Center,” “API Management,” or “Partnerships” in your account dashboard. This section is typically not visible to unverified or basic accounts.

6. Submit Your API Partnership Application Within the developer section, you will find an application form. Be prepared to detail:

   • Use Case: Are you building a trading bot, a portfolio dashboard, or a research tool?
   • Expected Volume: Estimate your API call frequency.
   • Data Requirements: Specify if you need real-time alerts, historical on-chain data, or social sentiment feeds.
   • Professional justification increases approval chances.

7. Key Generation, Testing, and Secure Storage Upon approval, you can generate API keys. You will likely be able to set specific permissions (e.g., “read-only”). Immediately restrict the key’s IP access if the platform allows it. Test the key using a simple GET request to a public endpoint (like /v1/ping) before integrating it into your main application. Never embed keys directly in client-side code or public repositories.

Right Column: Pro Tips & Critical Warnings #

• Screenshot/Placeholder: [Image: A screenshot showing the GMGN app interface with the ‘Security Center’ and ‘Developer Settings’ options highlighted.]

• Why This Order Matters: Platforms like GMGN gate API access behind KYC to prevent sybil attacks, data scraping, and ensure regulatory compliance for high-volume data usage. Skipping to step 5 without 1-4 is impossible.

• The Referral Code Advantage: Using LH369 during registration can sometimes expedite support tickets related to API access or provide a higher initial rate limit. It establishes your account’s provenance.

• Critical Security Protocol: Treat your API Secret Key with the same severity as your exchange withdrawal password. If you suspect a leak, revoke the key immediately in the developer dashboard and generate a new one. Use environment variables or dedicated secret management services in your code.

• Common Pitfall - The “Unofficial” SDK: Avoid third-party “wrapper” libraries or SDKs not published by GMGN’s official GitHub or documentation. These can contain malicious code that logs your keys.

• Risk Tip: Data Responsibility: With great API access comes great responsibility. Abusing the API (e.g., attempting to scrape the entire dataset) will result in immediate key revocation and account suspension. Always adhere to the documented rate limits.

• Risk Tip: Dependency Risk: Building a critical business or trading system solely on one platform’s API creates single-point-of-failure risk. Design your systems with fallbacks and abstract the API layer where possible.