create-signup-session

dci create-signup-session <signupRequestId> [body]

Exchanges the one-time activationToken returned by verifySignupRequest for a Firebase custom token once the request is completed, so the browser that entered the code lands in the new tenant without a second email. The token is bound to the request, single-use and valid for 10 minutes. Sign in with signInWithCustomToken against tenantId, then open consoleUrl.

• signupRequestId — Public signup request id (sr_ prefix).

Pass the request body as name: value arguments or pipe JSON on stdin — see Command structure.

Request

Content-Type: application/json

Field	Type	Required	Description
activationToken	string	yes	The one-time token returned by verifySignupRequest.

Raw JSON schema

{
  "type": "object",
  "required": [
    "activationToken"
  ],
  "properties": {
    "activationToken": {
      "type": "string",
      "description": "The one-time token returned by verifySignupRequest."
    }
  }
}

Output

OK - a session for the tenant admin.

By default dci renders the result as a table. Use --output json to get the full structure described below — see Output formats.

Field	Type	Description
customToken	string	Firebase custom token for the tenant admin; exchange it with signInWithCustomToken.
tenantId	string
customerId	string
consoleUrl	string (uri)

Raw JSON schema

{
  "type": "object",
  "required": [
    "customToken",
    "tenantId",
    "customerId"
  ],
  "properties": {
    "customToken": {
      "type": "string",
      "description": "Firebase custom token for the tenant admin; exchange it with signInWithCustomToken."
    },
    "tenantId": {
      "type": "string"
    },
    "customerId": {
      "type": "string"
    },
    "consoleUrl": {
      "type": "string",
      "format": "uri"
    }
  }
}

Errors

On failure, dci prints a single error message — with a hint when one is available — and exits with a typed code your scripts can branch on. See Errors and exit codes for the full contract.

HTTP status to exit code mapping

HTTP status	Exit code	Error code	Meaning
400	30	VALIDATION_ERROR	The arguments or request body were rejected. Review the command's flags and payload.
404	20	RESOURCE_NOT_FOUND	The requested resource does not exist. Check the identifier argument.
409	21	RESOURCE_CONFLICT	The operation conflicts with the resource's current state.
410	1	API_ERROR	The request failed; the printed error message has details.

Related

• create-signup-request — Create a signup request
• get-signup-request — Get a signup request
• resend-signup-verification — Resend the verification code
• verify-signup-request — Verify a signup request with the emailed code
• API reference: POST /signup/v1/requests/{signupRequestId}/session

Aliases: createsignupsession