Skip to content
  • There are no suggestions because the search field is empty.

Developer Portal. How To Log In

The DNA Behavior Developer Portal is used by external customers and partner developers to manage API access, subscription keys, and integration settings.

Access to the portal is not public by default and must be enabled by the DNA Behavior support team.

Who Can Access the Developer Portal

Access is provided to:

  • External customers integrating DNA APIs or SDKs

  • Partner and ISV developers building integrations

  • Approved technical contacts within an organization

Only named users with approved access can log in.


Step 1. Request Developer Portal Access

Before you can log in, you must request access.

How to request access

  1. Contact the DNA Behavior Support team (dnacare@dnabehavior.com)

  2. Provide the following details:

    • Company name

    • Primary account email

    • Name and email of the developer who should be granted access

    • Brief description of what you are building (API, SDK, webhook, integration)

Access is typically granted to one primary developer contact per organization.


Step 2. Receive Your Login Invitation

Once access is approved:

  • You will receive an email invitation from DNA Behavior

  • The email will contain instructions to activate your Developer Portal account

  • Follow the link in the email to set your password

If you do not receive the email, check spam or contact support.


Step 3. Log In to the Developer Portal

After activation, you can log in anytime at:

https://developers.dnabehavior.com

 


Step 4. Confirm Access and Locate Your Keys

After logging in:

  1. Navigate to the Profile tab

  2. Locate your Subscription Keys

    • Primary Key

    • Secondary Key

These keys are required for API authentication and SDK integrations.


Important Notes on Credentials

  • Subscription keys are account-specific

  • Keys must be stored securely on your side

  • Never expose keys in client-side code or public repositories

  • If you regenerate a key, the previous key is immediately invalidated

Plan key rotation carefully to avoid breaking live integrations.


Common Issues

I can’t log in

  • Your email may not have been approved yet

  • Contact DNA Behavior Support to confirm access

I don’t see any keys

  • Ensure you are logged in as the approved developer contact

  • Keys are only visible in the Developer Portal Profile tab


Need Access or Help?

If you need Developer Portal access or are unsure who in your organization should be the named user, contact the DNA Behavior Support team.

Submit a ticket here:
Submit a ticket