GET STARTED
TOOLS
COMMUNITY
Explore APIs in this category. Connect any of them to your AI agent through Jentic.
Filters
Jentic publishes the only available OpenAPI specification for GitHub v3 REST API, keeping it validated and agent-ready. The GitHub REST API is the developer-tools surface for the world's largest source-control and software collaboration platform - repositories, branches, pull requests, issues, code reviews, GitHub Actions workflows, security advisories, packages, and Apps. With 1,099 endpoints across themes including actions, billing, checks, code-scanning, dependabot, and dependency-graph, it powers most software development automation in use today.
Query and mutate issues, projects, cycles, teams, and workflows through Linear's GraphQL endpoint. Supports Bearer token authentication with personal API keys and OAuth 2.0 for third-party integrations. The single /graphql endpoint provides typed access to all Linear data including issues, comments, labels, milestones, roadmaps, and team configurations.
Octopus Server API powers Octopus Deploy, a release orchestration and continuous deployment platform used to ship software to any environment. The API exposes 1,775 endpoints covering projects, releases, deployments, runbooks, environments, accounts, certificates, build information, tenants, and audit streams. Use it to automate release creation, trigger deployments to dev/staging/production, manage variable sets and accounts across spaces, and enforce compliance and approval policies.
The GitHub v3 REST API for GitHub Enterprise Cloud (GHEC) exposes the full developer-platform surface - repositories, issues, pull requests, Actions workflows, code scanning, Dependabot, billing, and enterprise-level admin operations. Agents can manage source control, drive CI/CD, audit security alerts, and administer organisations and enterprise accounts. Authentication is a Bearer token (personal access token, GitHub App installation token, or fine-grained token) and the spec covers more than 1,000 endpoints across 70+ tag groups.
The Roblox API. See https://create.roblox.com/docs/cloud/open-cloud for more details. The API exposes 855 endpoints secured with apiKey, oauth2 authentication.
Tolgee Platform REST API reference. The API exposes 623 endpoints.
Track issues, plan sprints, configure workflows, and query project data across Jira Cloud instances through 588 REST endpoints. Supports OAuth 2.0 (3LO) and basic auth with API tokens for automation scenarios. Covers issue lifecycle from creation through custom workflow transitions, sprint planning with boards and backlogs, and advanced JQL-based search across projects.
Kibana is the Elastic Stack's analytics, search, and observability UI, and these REST APIs expose its administration and operational surface so workflows can run without clicking through the Kibana UI. The 582 endpoints cover alerting and connectors, agent builder and conversations, cases and APM configuration, data views and saved objects, Elastic Agent and Fleet management, security detections and exceptions, observability SLOs, and many more domains. Authentication is either an API key in the Authorization header or HTTP basic auth - and per-space variants of most endpoints support multi-space deployments.
RingCentral API specification. The API exposes 487 endpoints secured with oauth2 authentication.
This document describes the PagerDuty REST APIs. For guides and examples please visit our [Documentation.](https://developer.pagerduty.com/docs/get-started/getting-started/) Our REST APIs are defined in OpenAPI v3.x. You can view the schema at [github.com/PagerDuty/api-schema](https://github.com/PagerDuty/api-schema). Note that properties in some schemas have fields not shown by default such as `readOnly`, `format`, and `default`. Hover your cursor over the right column that looks like `optional+1` to see the full list of fields.
Jentic publishes the only available OpenAPI specification for Sumo Logic API, keeping it validated and agent-ready. Sumo Logic is a cloud-native log management and observability platform; the API exposes account, content, dashboard, monitor, role, and app installation surfaces across more than 400 operations. Use it to install apps, manage monitors, run admin operations, and query the platform state without using the Sumo UI. Note that endpoint hostnames vary by deployment region - pick the correct base URL for your account.
This API allows developers to communicate with the REALCUBE platform. Admins can also access the [admin area](https://api.realcube.com). The API exposes 390 endpoints secured with apiKey, oauth2 authentication.
Revenium Metering API. The API exposes 377 endpoints secured with apiKey authentication.
Sinao API for account management, apps administration and network exploration. The API exposes 367 endpoints secured with basic, bearer authentication.
Interact with GitLab projects, merge requests, issues, CI/CD pipelines, and container registries through 358 REST endpoints. Supports personal access tokens, OAuth 2.0, and project-level deploy tokens for granular access. Covers the complete DevOps lifecycle from source control and code review through automated testing, deployment pipelines, and package publishing.
Jentic publishes the only available OpenAPI specification for LaunchDarkly REST API, keeping it validated and agent-ready. The LaunchDarkly REST API (v2) covers feature flag and experimentation management - projects, environments, feature flags, segments, contexts, AI Configs, approvals, audit logs, code references, account members, custom roles, applications, and Data Export destinations. It is the platform-wide control plane for releasing software safely behind flags and running experiments. The spec covers 355 operations across the entire LaunchDarkly product surface.
The Microsoft Visual Studio App Center API gives mobile DevOps teams programmatic access to App Center's build, test, distribute, codepush, crash, analytics, and account management surfaces. The 351 endpoints cover app provisioning, release distribution, crash group inspection, audience analytics, in-app event logs, and team membership so end-to-end mobile delivery can run from external tooling. Authentication accepts an X-API-Token header or HTTP basic, and the API is organised around the {owner_name}/{app_name} addressing scheme.
Use [/v2/auth/login](https://api.packetfabric.com) endpoint to get the token. Use that token and "Authorize" button to authenticate your requests. You can also use that token to authorize your `curl` request: ``` curl -X GET "https://api.packetfabric.com/v2/activity-logs" -H "accept: */*" -H "Authorization: Bearer 12a30d30-20c0-4f62-a982-eb1424631094" ``` Python code to authenticate and utilize the [Bearer token](https://swagger.io/docs/specification/authentication/bearer-authentication/): ``` import requests login_url = 'https://api.packetfabric.com/v2/auth/login' login_payload = { 'login': 'admin', 'password': 'p4ssw0rd' } r = requests.post(login_url, json=login_payload) auth_token = r.json()['token'] request_header = { 'Authorization': f'Bearer {auth_token}' } contacts_url = 'https://api.packetfabric.com/v2/contacts' r = requests.get(contacts_url, headers=request_header) ``` *For resellers only*: To make the request on behalf of reseller's customer - add `On-Behalf: customer UUID` header to the request: ``` curl -X GET "https://api.packetfabric.com/v2/activity-logs" -H "accept: */*" -H "Authorization: Bearer 12a30d30-20c0-4f62-a982-eb1424631094" -H "On-Behalf: 11111111-2222-3333-4444-eb1424631094" ``` *For API Key Authentication* To utilize an API Key instead of login/password, you will need to generate a key and save the token. Using that token, as the Bearer token, you can then login. ``` api_key = <TOKEN> request_header = { 'Authorization': f'Bearer {api_key}' } contacts_url = 'https://api.packetfabric.com/v2/contacts' r = requests.get(contacts_url, headers=request_header) ```
XTRF Home Portal API enables you to perform operations on Projects, Quotes, Customers, Vendors etc. as a XTRF Home Portal user. <br>The documentation is generated from OpenAPI specification 3.0 available <a href="/home-api/openapi.json">here</a> <br> The API client/consumer code may be easily generated in 60+ programming languages using an open source code generator available at the time of writin. The API exposes 326 endpoints secured with apiKey authentication.
Jentic publishes the only available OpenAPI specification for Beamable, keeping it validated and agent-ready. Beamable is a live game services platform that provides ready-to-use backend systems for player accounts, leaderboards, tournaments, in-game mail, virtual economies, cloud saves, and content management. The API exposes 325 operations across resources like Account, Leaderboard, Tournament, Payment, Group, Mail, Cloudsaving, and Content, letting studios add LiveOps features without standing up custom microservices. Authentication uses Beamable's signed-request scheme with X-DE-SIGNATURE, X-DE-SCOPE, and X-DE-GAMERTAG headers, plus bearer player access tokens for user-context calls.
TeamViewer Web API - OpenAPI Specification. The API exposes 259 endpoints secured with apiKey authentication.
Self hosted FLOSS workout and fitness tracker. The API exposes 256 endpoints secured with apiKey, bearer authentication.
Jentic publishes the only available OpenAPI specification for App Store Connect API, keeping it validated and agent-ready. The App Store Connect API automates iOS, macOS, watchOS, and tvOS app distribution on Apple's App Store, covering app metadata, builds uploaded from Xcode, beta testing through TestFlight, in-app purchases, sales and finance reports, and provisioning profiles. Authentication uses signed JWT bearer tokens generated from an App Store Connect API key. The spec covers 252 operations across app records, builds, beta groups, customer reviews, pre-release versions, and pricing.
Jentic publishes the only available OpenAPI specification for App Store Connect API, keeping it validated and agent-ready. The App Store Connect API exposes 252 operations covering iOS, macOS, watchOS, and tvOS app distribution: app records, builds, TestFlight beta groups, App Store version submissions, in-app purchases, sales and finance reports, and provisioning profiles. Authentication uses signed JWT bearer tokens generated from a private key issued in App Store Connect. This is the same surface area surfaced under Apple's app-store-connect slug, indexed under an alternate path for discoverability.
API Reference provides programmatic access to developer tools functionality. The API exposes 237 endpoints secured with bearer authentication.
Radarr provides programmatic access to developer tools functionality. The API exposes 237 endpoints secured with apiKey authentication.
Sonarr API docs - The v3 API docs apply to both v3 and v4 versions of Sonarr. Some functionality may only be available in v4 of the Sonarr application. The API exposes 234 endpoints secured with apiKey authentication.
SmartOnboard Public API. The API exposes 234 endpoints secured with apiKey, oauth2 authentication.
Soldo Business API v2.0 OpenAPI specification. The API exposes 217 endpoints secured with oauth2 authentication.
Pipedrive API v1 provides programmatic access to developer tools functionality. The API exposes 213 endpoints.
remote.com/main version 1.0.0. The API exposes 206 endpoints secured with basic, bearer, oauth2 authentication.
Client library for accessing the Square Connect APIs. The API exposes 200 endpoints secured with apiKey, oauth2 authentication.
BOOK A DEMO
Browse thousands of APIs and connect them all to your agent with Jentic One. One layer, one credential — every API your agent needs.