> For the complete documentation index, see [llms.txt](https://docs.pyck.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pyck.cloud/graphql-api/queries/companies.md).

# Companies

Companies Query

Returns a paginated list of Company objects, with optional filtering and ordering.

## Arguments

| Name      | Type                | Description                                                            |
| --------- | ------------------- | ---------------------------------------------------------------------- |
| `after`   | `Cursor`            | Returns the elements in the list that come after the specified cursor  |
| `first`   | `Int`               | Returns the first *n* elements from the list                           |
| `before`  | `Cursor`            | Returns the elements in the list that come before the specified cursor |
| `last`    | `Int`               | Returns the last *n* elements from the list                            |
| `orderBy` | `CompanyOrder`      | Ordering options for companies returned from the connection            |
| `where`   | `CompanyWhereInput` | Filtering options for companies returned from the connection           |

## Return Type

`CompanyConnection!` - A connection to a list of Company objects with pagination information.

## Usage Example

```graphql
query {
  # Search companies by name
  companies(
    where: {
      nameContains: "Tech"
    },
    orderBy: { direction: ASC, field: NAME }
  ) {
    edges {
      node {
        id
        name
        organizationID
        tenantID
        createdAt
        companyusers {
          id
          name
          email
        }
      }
      cursor
    }
    totalCount
  }
}
```

```graphql
query {
  # Get companies for specific organization
  companies(
    where: {
      organizationID: "org-123"
    },
    first: 20
  ) {
    edges {
      node {
        id
        name
        organizationID
        tenantID
        companyusers {
          id
          name
          email
        }
      }
    }
    pageInfo {
      hasNextPage
      hasPreviousPage
      startCursor
      endCursor
    }
  }
}
```

## Common Filters

* `nameContains` - Search by company name substring
* `name` - Find by exact company name
* `organizationID` - Filter by organization ID
* `tenantID` - Filter by tenant ID
* `hasCompanyUsers` - Filter companies that have users
* `hasCompanyUsersWith` - Filter by user criteria

## Notes

* Companies represent organizations within the pyck system
* Each company belongs to a tenant and organization
* Companies can have multiple users associated with them
* Support for multi-tenant architecture through tenantID field
* organizationID links companies to external organization systems


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.pyck.cloud/graphql-api/queries/companies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.