## Get company

`GET /v1/companies/:id`

Returns a company by ID. 

## Parameters

| Parameter | Type | Req. | Description |
|----------|-----|:-----:|---------|
| `id` (path) | number | yes | Company ID |

## Examples

### curl — personal key

```bash
curl "https://vibecode.bitrix24.com/v1/companies/1" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth application

```bash
curl "https://vibecode.bitrix24.com/v1/companies/1" \
  -H "X-Api-Key: YOUR_APP_KEY" \
  -H "Authorization: Bearer USER_SESSION_TOKEN"
```

### JavaScript — personal key

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/companies/1', {
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

const { success, data } = await res.json()
console.log('Company:', data.title)
```

### JavaScript — OAuth application

```javascript
const res = await fetch('https://vibecode.bitrix24.com/v1/companies/1', {
  headers: {
    'X-Api-Key': 'YOUR_APP_KEY',
    'Authorization': 'Bearer USER_SESSION_TOKEN',
  },
})

const { success, data } = await res.json()
```

More about includes: [Related data](/docs/includes).

## Response fields

A company object with all fields — see [Company fields](/docs/entities/companies/fields).

## Related data

 (include)

```
GET /v1/companies/1?include=requisite
```

Available includes: `requisite`. The result is in the `_included` field.


## Response example

```json
{
  "success": true,
  "data": {
    "id": 1,
    "title": "Acme Inc.",
    "industry": "IT",
    "typeId": "CUSTOMER",
    "assignedById": 1,
    "phone": "+12025550123",
    "phoneWork": "+12025550123",
    "email": "info@example.com",
    "emailWork": "info@example.com",
    "emailHome": "home@example.com",
    "hasPhone": true,
    "hasEmail": true,
    "fm": [
      { "id": 65, "typeId": "PHONE", "valueType": "WORK", "value": "+12025550123" },
      { "id": 67, "typeId": "EMAIL", "valueType": "WORK", "value": "info@example.com" },
      { "id": 69, "typeId": "EMAIL", "valueType": "HOME", "value": "home@example.com" }
    ],
    "createdTime": "2020-05-08T10:48:20+00:00",
    "updatedTime": "2025-08-22T13:01:31+00:00"
  }
}
```

Phone and email in the response are strings with the primary value, and per-type values are in the `phoneWork`, `phoneMobile`, `emailWork`, `emailHome` fields. The full list with types is in the `fm[]` array (`{ id, typeId, valueType, value }`, where `id` is the entry identifier). Check presence via `hasPhone`/`hasEmail`: when there is no phone, `phone` comes back as an empty string. A specific `fm[]` entry cannot be modified or removed by its `id` through the API — PATCH adds new records.

## Error response example

404 — company not found:

```json
{
  "success": false,
  "error": {
    "code": "ENTITY_NOT_FOUND",
    "message": "Item not found"
  }
}
```


## Errors

| HTTP | Code | Description |
|------|-----|---------|
| 404 | `ENTITY_NOT_FOUND` | Company not found |
| 403 | `ACCESS_DENIED` | No access |
| 403 | `SCOPE_DENIED` | The API key does not have the `crm` scope |
| 401 | `TOKEN_MISSING` | The API key has no configured tokens |

Full list of common API errors — [Errors](/docs/errors).

## See also

- [Working with files in CRM fields](/docs/recipes/crm-files)
- [Update company](/docs/entities/companies/update) — modify fields
- [Company fields](/docs/entities/companies/fields) — field descriptions
- [Contacts](/docs/entities/contacts) — linked via `companyId`
- [Limits and optimization](/docs/optimization) — rate limits