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

# Get complete chip catalog

> Get the complete chip/SIM catalog from Emnify API.

    This endpoint acts as a secure backend proxy to the Emnify API,
    keeping API tokens safe and providing consistent data format.

    **Chip Item Fields:**
    - sim_id: Emnify SIM ID
    - phone_number (msisdn): Phone number
    - iccid: SIM card ICCID
    - status_id: Status ID (1=enabled, 2=disabled, etc.)
    - status_description: Status description
    - endpoint_id: Associated endpoint ID (if any)
    - last_connection: Last connection timestamp (if available)
    - operator: Network operator name (if available)
    - network_type: Network type like "4G" (if available)

    **Notes:**
    - This can be a slow operation for large catalogs (1000+ SIMs)
    - Results should be cached on the frontend
    - Pagination with Emnify API is handled automatically



## OpenAPI

````yaml /generated/specs/diagnostics.json get /api/v1/catalog/chips
openapi: 3.0.0
info:
  title: Raul API - Diagnostico
  description: Health, consumo, conectividad, SIMs, webhooks fallidos y estados tecnicos.
  version: 2.0.0
  contact: {}
servers:
  - url: https://api.raul.ugps.io
    description: Production
security: []
tags: []
paths:
  /api/v1/catalog/chips:
    get:
      tags:
        - Chip Catalog
      summary: Get complete chip catalog
      description: |-
        Get the complete chip/SIM catalog from Emnify API.

            This endpoint acts as a secure backend proxy to the Emnify API,
            keeping API tokens safe and providing consistent data format.

            **Chip Item Fields:**
            - sim_id: Emnify SIM ID
            - phone_number (msisdn): Phone number
            - iccid: SIM card ICCID
            - status_id: Status ID (1=enabled, 2=disabled, etc.)
            - status_description: Status description
            - endpoint_id: Associated endpoint ID (if any)
            - last_connection: Last connection timestamp (if available)
            - operator: Network operator name (if available)
            - network_type: Network type like "4G" (if available)

            **Notes:**
            - This can be a slow operation for large catalogs (1000+ SIMs)
            - Results should be cached on the frontend
            - Pagination with Emnify API is handled automatically
      operationId: ChipCatalogController_getChipCatalog
      parameters: []
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EmnifyChipCatalogResponseDto'
        '500':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/EmnifyErrorDto'
      security:
        - bearerAuth: []
components:
  schemas:
    EmnifyChipCatalogResponseDto:
      type: object
      properties:
        data:
          type: array
          items:
            $ref: '#/components/schemas/ChipCatalogItemDto'
        total_count:
          type: number
        timestamp:
          type: string
      required:
        - data
        - total_count
        - timestamp
    EmnifyErrorDto:
      type: object
      properties:
        error:
          type: string
        message:
          type: string
        details:
          type: string
      required:
        - error
        - message
    ChipCatalogItemDto:
      type: object
      properties:
        sim_id:
          type: number
        phone_number:
          type: string
        iccid:
          type: string
        status_id:
          type: object
        status_description:
          type: object
        endpoint_id:
          type: object
        last_connection:
          type: object
        operator:
          type: object
        network_type:
          type: object
      required:
        - sim_id
        - phone_number
        - iccid
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: Bearer token authentication

````