Unable to Create Developer Test Account - Internal Server Error (500)
SOLVE
Hi HubSpot Community,
I'm experiencing an issue when trying to create a new developer test account and would appreciate any guidance.
Issue Description
When I attempt to create a developer test account, I receive the following error message: "Something went wrong creating your developer test account. Please try again later or contact support."
Current Setup
Plan: Free
Existing developer test accounts: 1
Attempting to create: Additional test account
Steps Taken
Enter account name in the creation form
Click the "Create" button
Error message appears immediately
Browser Testing
I've tested this across multiple browsers to rule out browser-specific issues:
Google Chrome v139.0.7258.139: Failed
Safari v18.6(no extensions): Failed
Technical Details
OS: macOS Sequoia v15.6.1 M4 Pro
Console Error:
POST https://app.hubspot.com/api/integrators/test-portals/v2 500 (Internal Server Error)
Unable to Create Developer Test Account - Internal Server Error (500)
SOLVE
Hi,
this looks like a backend hiccup, not something you’re doing wrong. A few practical things that helped me in a similar case:
Creation from your Developer account dashboard -> Test accounts -> Create test account (not from a normal CRM portal).
Quota/cap: there’s a hard cap on active test portals per dev account (varies by program). If you recently deleted one, it can linger for a bit and still count. Try archiving/fully deleting any unused test portals and wait some time.
Make sure your developer profile email is verified, no pending TOS prompts, and no required 2FA setup is outstanding. Those can silently block creation.
Disable VPN/Private Relay, ad‑blockers, strict tracking protection, and try an incognito window. Test from a different network if you can.
Sign out of HubSpot completely, clear cookies for app.hubspot.com, sign back in to the developer portal, and retry.
That POST to /api/integrators/test-portals/v2 is HubSpot’s internal endpoint. A 500 with a correlationId almost always means a server-side failure (rate limit, validation bug, or a transient outage).
If you just need a throwaway environment, you can spin up a free CRM portal and add your app there for quick testing (not identical to a dev test account, but fine for API calls that don’t require special dev‑portal features).
If you’re on Pro/Ent elsewhere, a sandbox is another option, just not available on Free.
Unable to Create Developer Test Account - Internal Server Error (500)
SOLVE
Hi AlbertBer,
Thank you so much for your detailed and helpful response! I really appreciate you taking the time to provide such comprehensive troubleshooting steps.
I tried the method you suggested, but the developer test account still doesn't appear at https://app.hubspot.com/developer-test-accounts/[id]. However, I noticed that an account (though I'm not sure if it's a developer test account) has been added to https://app.hubspot.com/myaccounts. Since I can see the account there, I'm marking this as resolved for now.
Your explanation about the backend hiccup and the internal API endpoint makes a lot of sense. I'll keep your troubleshooting tips in mind for future reference, especially the points about quota caps and clearing cookies.
Unable to Create Developer Test Account - Internal Server Error (500)
SOLVE
Hi,
this looks like a backend hiccup, not something you’re doing wrong. A few practical things that helped me in a similar case:
Creation from your Developer account dashboard -> Test accounts -> Create test account (not from a normal CRM portal).
Quota/cap: there’s a hard cap on active test portals per dev account (varies by program). If you recently deleted one, it can linger for a bit and still count. Try archiving/fully deleting any unused test portals and wait some time.
Make sure your developer profile email is verified, no pending TOS prompts, and no required 2FA setup is outstanding. Those can silently block creation.
Disable VPN/Private Relay, ad‑blockers, strict tracking protection, and try an incognito window. Test from a different network if you can.
Sign out of HubSpot completely, clear cookies for app.hubspot.com, sign back in to the developer portal, and retry.
That POST to /api/integrators/test-portals/v2 is HubSpot’s internal endpoint. A 500 with a correlationId almost always means a server-side failure (rate limit, validation bug, or a transient outage).
If you just need a throwaway environment, you can spin up a free CRM portal and add your app there for quick testing (not identical to a dev test account, but fine for API calls that don’t require special dev‑portal features).
If you’re on Pro/Ent elsewhere, a sandbox is another option, just not available on Free.