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

# [Projects] List the connections of a project

> List every external provider a project can connect (Cloudflare today), whether it is connected, and a summary of the connection: the first account name, how many accounts and linked resources it has, who connected it and when, and whether it must be reauthorized. Who connected it is only shown to the organization's owners: it is null for other members, project guests and project-scoped API keys. A provider the platform does not offer right now is listed with `disabled: true`. Read from the database only: no provider is called. Each provider is managed under `…/integrations/{key}`.



## OpenAPI

````yaml https://api.onetsolutions.net/schema get /v1/organizations/{organization_id}/projects/{project_id}/integrations
openapi: 3.0.3
info:
  title: OnetSolutions API
  version: v1 (v1)
  description: >

    ## Overview


    The OnetSolutions API provides programmatic access to manage your cloud
    infrastructure, domains, and web hosting services.


    ## Authentication


    All API requests require authentication using one of the following methods:


    - **JWT Token**: Obtain a token via login endpoints and include it in the
    `Authorization: Bearer <token>` header

    - **API Key**: Generate an API key from your account settings and use it as
    `Authorization: Bearer sk-onetsolutions-...`


    ## Rate Limiting


    API requests are rate-limited to ensure fair usage:

    - **Anonymous**: 60 requests per minute, per client IP address

    - **Authenticated**: 5000 requests per hour, per user


    Some endpoints, such as login and sign-up, apply stricter limits of their
    own.

    A request over the limit gets a `429` response whose `Retry-After` header
    gives the wait in seconds.


    ## Pagination


    Most list endpoints return paginated results. Use the `page` and `page_size`
    query parameters

    (at most 100 results per page). The response carries `count`, `next`,
    `previous`, `page`, `page_size`,

    `total_pages` and the `results` themselves.


    ## Error Handling


    The API uses standard HTTP status codes:

    - `200` Success

    - `201` Created

    - `204` No Content

    - `400` Bad Request

    - `401` Unauthorized

    - `403` Forbidden

    - `404` Not Found

    - `409` Conflict

    - `429` Too Many Requests

    - `500` Internal Server Error

    - `503` Service Unavailable


    Error responses carry a JSON body with `detail`, a human-readable message,
    and `code`, a stable

    machine-readable error code. Some errors add `context` with structured
    details, and `error`

    repeats `detail` for older clients. A request whose fields fail validation
    gets a `400` whose body maps each

    invalid field to its list of messages. A few older endpoints still answer
    with `error` alone.
servers:
  - url: https://api.onetsolutions.net
    description: Production
security: []
tags:
  - name: Authentication
    description: >-
      Login, passwordless authentication, MFA, OAuth providers, and token
      management.
  - name: Organizations
    description: >-
      Organization management, members, roles, modules, audit logs, and
      notification settings.
  - name: Projects
    description: Project management, team members, and project-scoped resources.
  - name: Compute
    description: >-
      Cloud instances, volumes, snapshots, backups, VPCs, firewalls, SSH keys,
      uptime monitors, and instance tasks.
  - name: Billing
    description: >-
      Shopping cart, orders, invoices, payments, payment methods, gateways,
      promo codes, and balance management.
  - name: Domains
    description: >-
      Domain availability, registration, transfers, DNS zones, DNS records, and
      TLD information.
  - name: Web Hosting
    description: >-
      cPanel-based web hosting, emails, databases, subdomains, FTP accounts,
      addon domains, and SSL certificates.
paths:
  /v1/organizations/{organization_id}/projects/{project_id}/integrations:
    get:
      tags:
        - Projects
      summary: '[Projects] List the connections of a project'
      description: >-
        List every external provider a project can connect (Cloudflare today),
        whether it is connected, and a summary of the connection: the first
        account name, how many accounts and linked resources it has, who
        connected it and when, and whether it must be reauthorized. Who
        connected it is only shown to the organization's owners: it is null for
        other members, project guests and project-scoped API keys. A provider
        the platform does not offer right now is listed with `disabled: true`.
        Read from the database only: no provider is called. Each provider is
        managed under `…/integrations/{key}`.
      operationId: list_project_integrations
      parameters:
        - in: path
          name: organization_id
          schema:
            type: string
            format: uuid
          required: true
        - in: query
          name: page
          schema:
            type: integer
          description: A page number within the paginated result set.
        - in: query
          name: page_size
          schema:
            type: integer
          description: Number of results to return per page (at most 100).
        - in: path
          name: project_id
          schema:
            type: string
            format: uuid
          required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PaginatedIntegrationProviderList'
          description: ''
        '401':
          description: Authentication credentials were not provided or are invalid
        '404':
          description: >-
            Organization or project not found (code: project_not_found), or the
            project is outside the caller's reach
      security:
        - BearerAuth: []
components:
  schemas:
    PaginatedIntegrationProviderList:
      type: object
      required:
        - count
        - results
      properties:
        count:
          type: integer
          example: 123
        next:
          type: string
          nullable: true
          format: uri
          example: http://api.example.org/accounts/?page=4
        previous:
          type: string
          nullable: true
          format: uri
          example: http://api.example.org/accounts/?page=2
        page:
          type: integer
          example: 3
        page_size:
          type: integer
          example: 20
        total_pages:
          type: integer
          example: 7
        results:
          type: array
          items:
            $ref: '#/components/schemas/IntegrationProvider'
    IntegrationProvider:
      type: object
      properties:
        key:
          type: string
        name:
          type: string
        description_key:
          type: string
        disabled:
          type: boolean
        connected:
          type: boolean
        account_name:
          type: string
          nullable: true
        account_count:
          type: integer
        linked_count:
          type: integer
        connected_by:
          allOf:
            - $ref: '#/components/schemas/IntegrationConnectedBy'
          nullable: true
        connected_at:
          type: string
          format: date-time
          nullable: true
        needs_reauthorization:
          type: boolean
      required:
        - account_count
        - account_name
        - connected
        - connected_at
        - connected_by
        - description_key
        - disabled
        - key
        - linked_count
        - name
        - needs_reauthorization
    IntegrationConnectedBy:
      type: object
      properties:
        id:
          type: string
          format: uuid
        email:
          type: string
          format: email
      required:
        - email
        - id
  securitySchemes:
    BearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT or API Key
      description: >-
        Use `Authorization: Bearer <token>` header. Token can be a JWT token or
        an API key (format: `sk-onetsolutions-...`).

````

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