Grepr Grepr Pipe Integration API
The Grepr Pipe Integration API from Grepr — 2 operation(s) for grepr pipe integration.
The Grepr Pipe Integration API from Grepr — 2 operation(s) for grepr pipe integration.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/grepr:grepr-grepr-pipe-integration-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
title: Grepr Pipe Integration API
version: 1.0.0
description: 'Operations tagged Grepr Pipe Integration across 2 of this provider''s published API definitions: grepr-openapi.json, grepr.json. Each path carries the servers of the definition it was published in.'
tags:
- name: Grepr Pipe Integration
paths:
/v1/integrations/grepr-pipe:
get:
description: Get all Grepr pipe integrations.
operationId: listGreprPipeIntegrations
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/ItemsCollectionReadGreprPipe'
description: Integrations retrieved successfully
'401':
description: Unauthorized
security:
- grepr-api-key: []
- grepr-oidc: []
summary: List all Grepr pipe integrations
tags:
- Grepr Pipe Integration
post:
description: Creates a pipe that pipelines write log events into with a pipe sink and read them from with a pipe source.
operationId: createGreprPipeIntegration
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/WriteGreprPipe'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/ReadGreprPipe'
description: Integration created successfully
'401':
description: Unauthorized
'409':
content:
application/json:
schema:
$ref: '#/components/schemas/ReadGreprPipe'
description: Integration already exists.
security:
- grepr-api-key: []
- grepr-oidc: []
summary: Create a Grepr pipe integration
tags:
- Grepr Pipe Integration
/v1/integrations/grepr-pipe/{id}:
delete:
description: Deletes a Grepr pipe integration and its topic. Rejected while a pipeline uses it. No-op if already deleted.
operationId: deleteGreprPipeIntegration
parameters:
- in: path
name: id
required: true
schema:
type: string
responses:
'204':
description: Integration deleted successfully
'401':
description: Unauthorized
security:
- grepr-api-key: []
- grepr-oidc: []
summary: Delete a Grepr pipe integration
tags:
- Grepr Pipe Integration
get:
description: Get a Grepr pipe integration.
operationId: getGreprPipeIntegration
parameters:
- in: path
name: id
required: true
schema:
type: string
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/ReadGreprPipe'
description: Integration retrieved successfully
'401':
description: Unauthorized
'404':
description: Integration not found.
security:
- grepr-api-key: []
- grepr-oidc: []
summary: Get a Grepr pipe integration
tags:
- Grepr Pipe Integration
put:
description: Updates a Grepr pipe integration. The version should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.
operationId: updateGreprPipeIntegration
parameters:
- in: path
name: id
required: true
schema:
type: string
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/WriteGreprPipe'
responses:
'200':
content:
application/json:
schema:
$ref: '#/components/schemas/ReadGreprPipe'
description: Integration updated successfully
'401':
description: Unauthorized
'404':
description: Integration not found.
'409':
description: Integration was modified or deleted concurrently.
security:
- grepr-api-key: []
- grepr-oidc: []
summary: Update a Grepr pipe integration
tags:
- Grepr Pipe Integration
components:
schemas:
ReadGreprPipe:
properties:
createdAt:
description: Timestamp when the integration was created.
format: date-time
readOnly: true
type: string
id:
description: The integration id
type: string
jobIds:
description: List of job IDs associated with the integration.
items:
description: List of job IDs associated with the integration.
type: string
type: array
uniqueItems: true
name:
description: Name of the integration.
example: my_integration
pattern: '[a-zA-Z0-9 _-]{1,128}'
type: string
organizationId:
description: Organization ID of the integration.
type: string
payload:
$ref: '#/components/schemas/GreprPipe'
teamIds:
description: The team IDs that this integration is associated with.
items:
description: The team IDs that this integration is associated with.
type: string
type: array
uniqueItems: true
type:
description: The type of the integration. This is used to determine the payload type.
enum:
- grepr-pipe
type: string
updatedAt:
description: Timestamp when the integration was last updated.
format: date-time
readOnly: true
type: string
version:
description: 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.
example: 0
format: int32
minimum: 0
type: integer
required:
- createdAt
- id
- jobIds
- name
- organizationId
- payload
- type
- updatedAt
- version
type: object
GreprPipe:
description: The payload containing integration data.
type: object
x-type:
type: grepr-pipe
ItemsCollectionReadGreprPipe:
properties:
items:
default: []
items:
$ref: '#/components/schemas/ReadGreprPipe'
type: array
type: object
WriteGreprPipe:
properties:
name:
description: Name of the integration.
example: my_integration
pattern: '[a-zA-Z0-9 _-]{1,128}'
type: string
payload:
$ref: '#/components/schemas/GreprPipe'
teamIds:
default: []
description: The team IDs that this integration is associated with.
items:
description: The team IDs that this integration is associated with.
type: string
type: array
uniqueItems: true
type:
description: The type of the integration. This is used to determine the payload type.
enum:
- grepr-pipe
type: string
version:
description: 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.
example: 0
format: int32
minimum: 0
type: integer
required:
- name
- payload
- type
- version
type: object
securitySchemes:
grepr-api-key:
in: header
name: GREPR-API-KEY
type: apiKey
grepr-oidc:
bearerFormat: JWT
openIdConnectUrl: https://grepr-prod.us.auth0.com/.well-known/openid-configuration
type: openIdConnect
x-refined-from:
- grepr-openapi.json
- grepr.json
x-tagGroups:
- name: Integrations
tags:
- Grepr-hosted Data Warehouse Integration
- External S3 Data Warehouse Integration
- Datadog Integration
- New Relic Integration
- Splunk Integration
- Sumo Logic Integration
- OpenTelemetry Integration
- name: Pipelines
tags:
- Jobs
- Templates
- Datasets
- Status Metrics
- External Triggers
- Job Actions
- Triggers
- name: Pipeline Components
tags:
- Operations
- Transforms
- Sources
- Sinks
- name: Administration
tags:
- Users
- Teams
- Roles
- Permission
- Invitations
- Activity Logs
- name: Organization
tags:
- Organizations
- Access Configuration
- Grepr API Key
- Service Accounts
- Signup
- name: Query & Analysis
tags:
- Job Anomalies
- Grok Parsing
- Query Parsing
- Validation
- name: System
tags:
- Manifest