---
title: "Get a OTLP integration"
method: GET
path: "/v1/integrations/otlp/{id}"
tags: ["OpenTelemetry Integration"]
---

# Get a OTLP integration

`GET /v1/integrations/otlp/{id}`

## Request

- Base URL: `https://docs.grepr.ai` (the document declares no server; this is the origin it was published from)
- URL: `https://docs.grepr.ai/v1/integrations/otlp/{id}`
- Auth: one of:
  - API key in header `GREPR-API-KEY`
  - OpenID Connect (`https://grepr-prod.us.auth0.com/.well-known/openid-configuration`)

Get an integration to connect to OTLP.

## Path parameters

- `id` string, required

## Response `200`

Integration retrieved successfully

- ReadOtlp
  - `createdAt` string, date-time, required: Timestamp when the integration was created.
  - `id` string, required: The integration id
  - `jobIds` string[], required: List of job IDs associated with the integration.
  - `name` string, required: Name of the integration.
  - `organizationId` string, required: Organization ID of the integration.
  - `payload` Otlp, required: The payload containing integration data.
    - `attributeHeaders` AttributeHeaderMapping[]: Headers whose values are dynamically extracted from log event attributes. Each mapping specifies a header name and the attribute path to read the value from.
      - `attributePath` string[]: Attribute path segments to extract the header value from. Each segment represents one level of nesting in the log event attributes.
      - `headerName` string, required: HTTP header name to set from the attribute value
    - `endpoint` string, required: The base OTLP endpoint. Signal-specific paths will be appended automatically (e.g., /v1/logs for logs, /v1/traces for traces) unless overridden by signal-specific endpoint fields.
    - `headers` Header[]: Non-secret HTTP headers for writing to an OTLP sink. Headers can contain multiple values.
      - `name` string, required: Header name
      - `value` string, required: Header value
    - `logsEndpoint` string: Optional override for the logs endpoint. If specified, this will be used instead of appending /v1/logs to the base endpoint.
    - `outputEncoding` 'proto' | 'json': Wire encoding for outbound OTLP HTTP requests.
    - `plainTextToken` string: A unique token generated by Grepr in plain-text
    - `secretHeaders` object: Secret HTTP headers for writing to an OTLP sink. Headers are single-valued.
    - `token` string: A unique token generated by Grepr to authenticate for an OTLP integration at ingestion
    - `tracesEndpoint` string: Optional override for the traces endpoint. If specified, this will be used instead of appending /v1/traces to the base endpoint.
  - `teamIds` string[]: The team IDs that this integration is associated with.
  - `type` 'otlp', required: The type of the integration. This is used to determine the payload type.
  - `updatedAt` string, date-time, required: Timestamp when the integration was last updated.
  - `version` integer, required: Version of the integration. Should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.

## Other responses

- `401`: Unauthorized
- `404`: Integration not found.

---

[API](https://skmtc.dev/grepr/apis/grepr-api.md) - [All operations](https://skmtc.dev/grepr/apis/grepr-api/llms.txt) - [OpenAPI document](https://skmtc.dev/grepr/apis/grepr-api/revisions/2a5ce03a0bf0?raw)