Skip to main content
Signup sessions manage the lifecycle of an agentic signup flow — from creation by the CLI, through browser consent, to credential delivery.

​
Endpoints

  • POST /v1/gate/sessions — Create a signup session
  • GET /v1/gate/sessions/{gateSessionId} — Poll session status
  • GET /v1/gate/sessions/{gateSessionId}/consent — Get consent page data
  • POST /v1/gate/sessions/{gateSessionId}/approve — Submit approval
  • POST /v1/gate/sessions/{gateSessionId}/cancel — Cancel a pending session
  • POST /v1/gate/sessions/{gateSessionId}/ack — Acknowledge credential delivery

​
Notes

  • POST /v1/gate/sessions requires service_id.
  • New signup sessions can only be created for services that are active and publicly discoverable in the registry.
  • Existing sessions keep working even if their service is later disabled or made private; Gate resolves those session-owned service configs internally.
See the OpenAPI spec for full request/response schemas.
Approved credentials are delivered exactly once. Gate stores the company secret encrypted until the first successful delivery, then clears the secret material.