## Get a delivery service

`GET /v1/delivery-services/:id`

Look up a delivery service by its ID to check its settings before updating the service or using it in an integration.

## Parameters

| Parameter | Type | Required | Description |
|-----------|------|:--------:|-------------|
| `id` (path) | integer | yes | Positive integer no greater than `9007199254740991`. Obtain it from the [delivery service list](/docs/entities/delivery-services/list) |

Query parameters are not supported.

## Examples

### curl — personal key

```bash
curl -g "https://vibecode.bitrix24.com/v1/delivery-services/85" \
  -H "X-Api-Key: YOUR_API_KEY"
```

### curl — OAuth app

```bash
curl -g "https://vibecode.bitrix24.com/v1/delivery-services/85" \
  -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/delivery-services/85', {
  headers: {
    'X-Api-Key': 'YOUR_API_KEY',
  },
})

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

### JavaScript — OAuth app

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

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

## Response fields

| Field | Type | Description |
|-------|------|-------------|
| `success` | boolean | Always `true` on success |
| `data` | object | Delivery service record |
| `data.id` | integer | Delivery service ID |
| `data.parentId` | integer \| null | Parent service ID from the [delivery service list](/docs/entities/delivery-services/list). May be `null` |
| `data.name` | string \| null | Delivery service name |
| `data.active` | string \| null | Activity flag: `Y` or `N` |
| `data.description` | string \| null | Delivery service description |
| `data.currency` | string \| null | Currency code from the [currency list](/docs/entities/currencies/list) |
| `data.sort` | integer \| null | Sort order |
| `data.logotype` | integer \| null | Logo file ID, not a URL. May be `null` |

## Response example

```json
{
  "success": true,
  "data": {
    "id": 85,
    "parentId": null,
    "name": "Courier delivery",
    "active": "N",
    "description": "",
    "currency": "USD",
    "sort": 100,
    "logotype": null
  }
}
```

## Error response example

404 — delivery service not found:

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

## Errors

| HTTP | Code | Description |
|------|------|-------------|
| 400 | `INVALID_PARAMS` | The path ID is not a positive safe integer, or the request contains query parameters |
| 404 | `ENTITY_NOT_FOUND` | No delivery service with this ID was found |
| 502 | `BITRIX_RESPONSE_INVALID` | The response does not match the delivery service format |
| 422 | `BITRIX_ERROR` | Bitrix24 rejected the operation. The original error message is preserved |
| 403 | `BITRIX_ACCESS_DENIED` | Bitrix24 denied access |
| 403 | `SCOPE_DENIED` | The API key lacks the `delivery` scope |
| 401 | `TOKEN_MISSING` | No Bitrix24 credentials are configured for the key |

For common API errors, see [Errors](/docs/errors).

## See also

- [List delivery services](/docs/entities/delivery-services/list)
- [Create a delivery service](/docs/entities/delivery-services/create)
- [Update a delivery service](/docs/entities/delivery-services/update)
- [Delivery service fields](/docs/entities/delivery-services/fields)
- [Delivery services](/docs/entities/delivery-services)