API keys are a great way to access your account data programmatically, however, it is important to permission the keys properly. When creating an API key on the API settings page, you will first select the scope of the key. The scope determines which account your key will have access to. Most third party applications require an account-specific key instead of a master-scoped key. The default name of your Gemini account is “Primary”.

Once you select the scope it is important to properly permission the key to only access account data that is necessary. Most tax software only requires view-only access, in that case the “Auditor” role is appropriate. If the third-party is going to be placing trades on your behalf, then the “Trader” role is appropriate. If the third-party is moving funds for you then the “Fund Manager” role allows for crypto movement on your account.

It is extremely important that you trust any third-party that you are granting access to your account. Please be sure to enable Approved Addresses on your account. We recommend that you closely read the third-party application’s terms of service and privacy policy before using their services. Gemini is not responsible for the acts or practices of any third-party applications to which you give access.

You can also check out our Partners page to see any approved third-party applications.

Note for UK customers:

To ensure compliance with the UK Travel Rule, outbound crypto transfers cannot be initiated via API. Inbound crypto transfers will also require the user to complete the appropriate attestation via mobile or web UI.

All other API functionalities are available.