How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Bigeye Config Service API

The ConfigService API from Bigeye — 2 operation(s) for configservice.

Bigeye Config Service API is one of 45 APIs that Bigeye publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include ConfigService. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 2 operations across 2 paths, and defines 7 schemas. It is described by OpenAPI 3.2.0, at version version not set.

Requests are made against a single base URL, https://app.bigeye.com.

2 operations 2 paths 7 schemas 1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
version not set
Base URL
https://app.bigeye.com
Authentication
HTTP Basic, API Key, API Key
Resource Areas
1

Authentication & Security 3

Bigeye Config Service API declares 3 security schemes for authenticating requests. It accepts HTTP basic authentication (basicAuth). An API key is passed in the header as Authorization (Agent_API_Key). An API key is passed in the header as Authorization (Personal_API_Key). By default, every request must be authenticated.

  • Agent_API_Key — Add 'apikey ' to the beginning of your api key
  • Personal_API_Key — Add 'apikey ' to the beginning of your api key

Paths & Operations 2

Across 2 paths, the API surfaces 2 operations — 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

ConfigService 2
POST
/api/v1/configs/fetch
Get configs
ConfigService_GetConfigs body → 200default
PUT
/api/v1/configs
Update configs
ConfigService_UpdateConfigs body → 200default

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are generatedConfigValue (5 properties), runtimeError (4 properties), protobufAny (2 properties), generatedUpdateConfigRequest (1 property). Each schema is shown below with its type and property counts.

generatedEmpty
object
generatedConfigValue
object
5 properties
generatedGetConfigListResponse
object
1 property
generatedConfigValueType
string
runtimeError
object
4 properties
protobufAny
object
2 properties
generatedUpdateConfigRequest
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

bigeye-configservice-api-openapi.yml Raw ↑

Other APIs Bigeye publishes across the network.

Bigeye MCP Gateway
Bigeye Agent Service API
Bigeye API Key Service API
Bigeye Catalog Rebuilds Service API
Bigeye Classifier Service API
Bigeye Collection Service API
Bigeye Collection V2 Service API
Bigeye Column Service API
Bigeye Company Service API
Bigeye Comparison Table Service API
Bigeye Custom Rule Service API
Bigeye Dashboard Service API
Where this information came from

This is an independent, third-party profile of Bigeye Config Service API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.