API Key authentication should only be used to access your own account. To securely access the accounts of other Coinbase users, use Coinbase Business (OAuth2)
Coinbase Business APIs can be accessed using API Keys created on the Coinbase Development Platform (CDP). See CDP API keys.

​
CDP API keys

Keys created on the Coinbase Development Platform (CDP) may not yet be supported by all third-party applications.

​
Creating API Keys

  1. Navigate to the Coinbase Developer Platform and select Secret API Keys under the API Keys tab.
  2. Click the Create API key button.
  3. Enter an API key nickname and then expand API restrictions and Advanced Settings.
  4. Enter your IPs in the IP allowlist section (recommended but not required).
  5. Set portfolio and permission restrictions.
  6. Change signature algorithm to ECDSA if you’re not developing your own authentication code.
  7. Click Create & Download.
  8. Secure your private/public key pair in a safe location.

​
Making Requests

CDP API keys are used to generate a JSON Web Token (JWT) for an API. Once you’ve generated a JWT, set it as a Authorization Bearer header to make an authenticated request. 
# Example request to get account
curl -H "Authorization: Bearer $JWT" 'https://api.coinbase.com/v2/accounts/f603f97c-37d7-4e58-b264-c27e9e393dd9/addresses'

​
Generating a JWT

Regardless of which code snippet you use, follow these steps:
  1. Replace key name and key secret with your key name and private key. key secret is a multi-line key and newlines must be preserved to properly parse the key. Do this on one line with \n escaped newlines, or with a multi-line string.
  2. Replace the request method and the path you want to test. If the URI has a UUID in the path you should include that UUID here, e.g., /v2/accounts/f603f97c-37d7-4e58-b264-c27e9e393dd9/addresses.
  3. Run the generation script that prints the command export JWT=....
  4. Run the generated command to save your JWT.
Your JWT expires after 2 minutes, after which all requests are unauthenticated.
You must generate a different JWT for each unique API request.

​
Code Samples

The easiest way to generate a JWT is to use the built-in functions in our Python SDK as described below. Otherwise, use the code samples below to generate/export a JWT and make an authenticated request.
  1. Install the SDK. 
    pip3 install coinbase-advanced-py
  2. In the console, run: python main.py (or whatever your file name is).
  3. Set the JWT to that output, or export the JWT to the environment with export JWT=$(python main.py).
  4. Make your request, example curl -H "Authorization: Bearer $JWT" 'https://api.coinbase.com/api/v3/brokerage/accounts' 
from coinbase import jwt_generator

api_key = "organizations/{org_id}/apiKeys/{key_id}"
api_secret = "-----BEGIN EC PRIVATE KEY-----\nYOUR PRIVATE KEY\n-----END EC PRIVATE KEY-----\n"

request_method = "GET"
request_path = "/api/v3/brokerage/accounts"

def main():
    jwt_uri = jwt_generator.format_jwt_uri(request_method, request_path)
    jwt_token = jwt_generator.build_rest_jwt(jwt_uri, api_key, api_secret)
    print(jwt_token)

if __name__ == "__main__":
    main()

​
Security Best Practices

​
Storing Credentials Securely

Store your credentials securely. If someone obtains your api_secret with the transfer permission, they will be able to send all the digital currency out of your account. Avoid storing API keys in your code base (which gets added to version control). The recommended best practice is to store them in environment variables. Learn more about environment variables here. Separating credentials from your code base and database is always good practice. API Key access is turned off by default on all accounts. To implement an API Key integration, you therefore must first enable it,and then take necessary precautions to store the API Key securely. You can always regenerate your API Key (or disable it) if you feel it has been compromised.

​
Validating SSL Certificates

It is also very important that your application validates our SSL certificate when it connects over https. This helps prevent a man in the middle attack. If you are using a client library, this may be turned on by default, but you should confirm this. Whenever you see ‘verify SSL’ you should always ensure it is set to true.

​
Additional Security for API Keys

For enhanced API Key security, we recommend that you allowlist IP addresses that are permitted to make requests with a particular API Key. You can specify IP addresses to allowlist when creating a new API Key or editing an existing one.