Partner API keys are issued on request. The keyless public endpoints need no key; everything else requires a Bearer gma_api_... key with a read or write scope, optionally restricted to specific vaults and a single wallet.
How to request
Email support@gma.fi with your request. Include:
| Field | Description |
|---|---|
| Name | Your name or organization. |
| The contact email for the key. | |
| Use case | What you are building and which endpoints you need. |
| Contact handle | A handle we can reach you on (X, Discord, or Telegram). |
You can also reach the team on X, Discord, or Telegram.
What to tell us
So we can scope the key correctly, mention:
- Whether you need read only, or write (deposit/withdraw transaction building and activity recording).
- Whether the key should be limited to specific vaults.
- Whether it should be bound to a single wallet.
- Your expected request volume, so we can set an appropriate per-key rate limit.
After you receive a key
The raw key is shown once — store it as a server-side secret. Never embed it in a browser bundle. Browser-wallet applications should proxy requests through their own backend, which attaches the key. See Authentication for scopes, vault allowlists, and wallet binding.
Next: AI / LLM integration