> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Get Codex sign-in status

> Check the status of a Codex sign-in started by this organization: code_shown (with the URL and code) while the person approves, then approved, expired or failed.



## OpenAPI

````yaml /openapi.json post /integrations/codex/device-login/status
openapi: 3.1.1
info:
  title: Sazabi Public API
  version: 1.0.0
  description: >
    Public REST API for Sazabi. Authenticate using a secret API key in the
    Authorization header.


    ## Pagination


    This API uses two pagination strategies depending on the endpoint type:


    ### Cursor-Based Pagination (List Endpoints)


    List endpoints (threads, messages, keys) use cursor-based pagination for
    efficient, consistent results:


    - **Parameters**: `limit` (items per page, default 50, max 100), `cursor`
    (opaque pagination token)

    - **Response**: Includes `nextCursor` field - pass this as `cursor` in the
    next request

    - **End of results**: When `nextCursor` is `null`, there are no more results

    - **Example**: `GET
    /v1/threads?limit=20&cursor=01234567-89ab-cdef-0123-456789abcdef`


    ### Page-Based Pagination (Search Endpoints)


    Search endpoints use page-based pagination due to the underlying search
    engine:


    - **Parameters**: `limit` (items per page, default 20, max 100), `page`
    (1-indexed page number)

    - **Response**: Includes `pagination` object with `page`, `limit`,
    `totalResults`, `totalPages`

    - **Example**: `GET /v1/search/threads?q=error&limit=10&page=2`
servers:
  - url: https://api.sazabi.com/v1
    description: Production
security: []
paths:
  /integrations/codex/device-login/status:
    post:
      tags:
        - Integrations
      summary: Get Codex sign-in status
      description: >-
        Check the status of a Codex sign-in started by this organization:
        code_shown (with the URL and code) while the person approves, then
        approved, expired or failed.
      operationId: integrations.codexDeviceLogin.getStatus
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                organizationId:
                  type: string
                  minLength: 1
                loginId:
                  type: string
                  format: uuid
              required:
                - organizationId
                - loginId
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                type: object
                properties:
                  status:
                    enum:
                      - code_shown
                      - approved
                      - rejected_device_auth_disabled
                      - expired
                      - failed
                    type: string
                  verificationUrl:
                    type: string
                    format: uri
                  userCode:
                    type: string
                    minLength: 1
                  expiresAt:
                    type: string
                    format: date-time
                  connectionId:
                    type: string
                    format: uuid
                  message:
                    type: string
                required:
                  - status

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.