Splunk On-Call (BYOK)

Splunk On-Call (BYOK) — connector documentation

• MCP endpoint: https://byok-victorops.connectorbay.com/mcp
• REST API: POST https://byok-victorops.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-victorops.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own Splunk On-Call Splunk On-Call API key, sent in the X-Upstream-Key header and the Splunk On-Call API ID in X-Upstream-Key-2 of every request (never stored, logged or cached)
• Health: https://byok-victorops.connectorbay.com/health · Tool schemas: https://byok-victorops.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-victorops · agent@connectorbay.com

What Splunk On-Call (BYOK) is for

Splunk On-Call (BYOK) lets an AI assistant read your own Splunk On-Call data through the Splunk On-Call API with a key you supply (Splunk On-Call API key). Read-only: 12 tools (list_current_incidents, get_incident, search_incident_history, list_teams, list_team_members, list_users, get_org_on_call_now, get_team_on_call_schedule, list_escalation_policies, get_escalation_policy, list_routing_keys, get_maintenance_mode). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.victorops.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Splunk On-Call. Splunk On-Call and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which incidents are open in Splunk On-Call right now?"
• "Show the details and history of Splunk On-Call incident 42"
• "Which Splunk On-Call incidents on service 'disk' started after 1 October 2026?"
• "What teams exist in Splunk On-Call?"
• "Who is on the Splunk On-Call team team-abc123?"
• "List the users in our Splunk On-Call organization"

What it does

• list_current_incidents: List the incidents that are currently open (triggered or acknowledged) with phase, alert count, host, service and who was paged.
• get_incident: Get one incident by number, including its state transitions (who acknowledged or resolved it and when).
• search_incident_history: Search past incidents (reporting API) by time range, host, service, phase or routing key. Returns up to 100 per call; page with offset.
• list_teams: List all teams with name, slug, member count and whether it is the default team.
• list_team_members: List the members of a team with username and name.
• list_users: List users in the organization with username, name, creation time and verification flag (email addresses are left out).
• get_org_on_call_now: List who is on call right now for every team.
• get_team_on_call_schedule: Get a team's on-call schedule per escalation policy for the coming days, including overrides.
• list_escalation_policies: List escalation policies with their team. Optionally filter by policy name.
• get_escalation_policy: Get one escalation policy with its steps and timeouts.
• list_routing_keys: List routing keys with the teams and policies each routes to.
• get_maintenance_mode: Show whether maintenance mode is active and which routing targets it silences.

BYOK key

You bring your own Splunk On-Call Splunk On-Call API key (https://portal.victorops.com/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.victorops.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://portal.victorops.com/public/api-docs.html (the API this connector calls, with a BYOK key)

Live from the Splunk On-Call API (api.victorops.com) with a BYOK key; documentation: https://portal.victorops.com/public/api-docs.html. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Splunk On-Call. Splunk On-Call and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Splunk On-Call account.

Built for: Worldwide. Languages: English.

Splunk On-Call (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What Splunk On-Call (BYOK) is. Splunk On-Call (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own Splunk On-Call data: Read your Splunk On-Call (VictorOps) incidents, on-call schedules, teams, users, escalation policies and routing keys with your own API ID and API key. You bring your own Splunk On-Call Splunk On-Call API key; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one Splunk On-Call call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to api.victorops.com, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If Splunk On-Call rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What Splunk On-Call receives. The request we make on your behalf, including the key and the arguments, under Splunk On-Call's own terms and privacy policy. Splunk On-Call acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer Splunk On-Call gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your Splunk On-Call data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. Splunk On-Call (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at Splunk On-Call at any time to end all access.

Children. Splunk On-Call (BYOK) is a general-audience service operated by the adult using the assistant, under Splunk On-Call's own age rules.

Changes. We will post changes here with a new effective date.

Splunk On-Call (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the Splunk On-Call (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. Splunk On-Call (BYOK) provides: Read your Splunk On-Call (VictorOps) incidents, on-call schedules, teams, users, escalation policies and routing keys with your own API ID and API key. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own Splunk On-Call credentials and only access data you are allowed to access. Splunk On-Call's terms apply to your use of Splunk On-Call; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Splunk On-Call. Splunk On-Call and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data Splunk On-Call returns, lightly trimmed; it may be incomplete, delayed or changed by Splunk On-Call. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your Splunk On-Call account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent Splunk On-Call's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; Splunk On-Call may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your Splunk On-Call key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action Splunk On-Call takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-victorops

Splunk On-Call (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-victorops.connectorbay.com/mcp
• REST API: https://byok-victorops.connectorbay.com/openapi.json
• Live status: https://byok-victorops.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. Splunk On-Call (BYOK) never asks for them.