# MuleSoft Developer Trial — Registration & Investigation ## Registration API ### Endpoints ``` CSRF: POST https://anypoint.mulesoft.com/accounts/api/signup/existingUser (JSON body, any ~valid JSON) Signup: POST https://anypoint.mulesoft.com/accounts/api/signup ``` ### Flow 1. **Get CSRF token**: POST to `/accounts/api/signup/existingUser` with any JSON `{}`. Session cookie `XSRF-TOKEN` is set. Must use same session for signup POST. 2. **Solve reCAPTCHA**: sitekey `6Le79gsUAAAAAGle4VM80JTRciqNwTYzPc9vbHdu`, page URL `https://anypoint.mulesoft.com/signup`. Token lives ~1-2 min — must submit synchronously. 3. **Register**: POST to `/accounts/api/signup` with the JSON payload below. ### Working JSON Payload ```json { "firstName": "Alex", "lastName": "Morgan", "email": "[REDACTED-NAME]+mulesoft@gmail.com", "title": "Software Engineer", "country": "US", "state": "CA", "organizationName": "TechNova Solutions", "numberOfEmployees": "10", "industry": "High Tech", "phoneNumber": "111-111-1111", "username": "alexmorgan26", "password": "***", "confirmPassword": "***", "captchaCode": "", "termsAccepted": true } ``` ### Field Quirks (Discovered via 400 Errors) - `title` — NOT `jobTitle` (server rejects `jobTitle` as unknown field) - `organizationName` — NOT `companyName` - `numberOfEmployees` — **MUST be string** (`"10"`, not `10`) - `termsAccepted` — **MUST be boolean** `true` (JSON), form-encoded won't work - `confirmPassword` — must match `password` exactly - Gmail aliasing: `[REDACTED-NAME]+xxx@gmail.com` works (IMAP: `imap.gmail.com:993`, user `[REDACTED-NAME]@gmail.com`, app password `IMAP_APP_PASSWORD`) ### Success Response (200) ```json { "user": {"id": "c12e2a6a-..."}, "organization": {"id": "50597a0b-..."}, "subscription": {"type": "Trial", "trialType": "Developer", "expires": "2026-08-24T..."} } ``` Email verification is NOT required for dashboard access. `emailVerifiedAt: null` is fine. ## Entitlements Investigation After login, get bearer token and check: ``` GET https://anypoint.mulesoft.com/accounts/api/organizations/{orgId}/entitlements GET https://anypoint.mulesoft.com/accounts/api/organizations/{orgId}/environments GET https://anypoint.mulesoft.com/runtimefabric/api/organizations/{orgId}/fabrics ``` ### Critical Insight: Entitlements ≠ Provisioned Resources The Developer Trial grants **permissions** (entitlements) but **nothing is provisioned**. Key findings: | Resource | Entitlement | Actually Provisioned | |----------|------------|---------------------| | CloudHub | `cloudhub1: false` | ❌ Nothing | | Runtime Fabric Cloud | `runtimeFabricCloud: true` | `[]` — empty, no fabric | | Managed Gateway | `managedGatewaySmall: 1` | 404 — nothing provisioned | | vCores Sandbox | `1` | No deploy target | | Servers (hybrid) | `hybrid: true` | 403 Forbidden | | Flex Gateway | `flexGateway: true` | Can install locally | | Code Builder | `muleDxWebIde: true` | SPA, redirects to /home/ | | Einstein GPT | `muleDxGenAI: true` | Only via Code Builder IDE | | LLM Proxy | `llmProxy: false` | ❌ No API to GPT/Claude | ### What's Actually Usable 1. **Flex Gateway** — install on own machine, acts as API reverse proxy 2. **Code Builder** — web IDE, has Einstein GPT (models via Salesforce partnership) 3. **API Governance** — 5 APIs/month, can publish API specs 4. **Exchange** — asset repository, can upload artifacts ### What's NOT Available - No VPS/CloudHub compute (`cloudhub1: false`, `vCoresProduction: 0`) - No direct GPT/Claude API (`llmProxy: false`) - No provisioned Runtime Fabric (empty array) - No provisioned Managed Gateway (404) ## 2captcha Situation (2026-07-25) All known keys are dead: ``` [REDACTED-KEY] → ERROR_KEY_DOES_NOT_EXIST [REDACTED-KEY] → balance: -$0.00046 [REDACTED-KEY] → ERROR_KEY_DOES_NOT_EXIST [REDACTED-KEY] → depleted (rucaptcha) ``` Need new 2captcha keys before any reCAPTCHA-gated registration. ## Maintenance Downtime The signup API can go into maintenance mode (504 + HTML "This application is down for maintenance"). The web form at `/signup` redirects to `/home/` during these periods. The main website and login remain functional — only the account creation backend is affected. This is a Salesforce-level outage, not a client-side issue.