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

Opply Agents API

The Agents API from Opply — 7 operation(s) for agents.

Opply Agents API is one of 47 APIs that Opply publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Agents. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 7 operations across 7 paths, and defines 22 schemas. It is described by OpenAPI 3.0.3, at version 0.0.0.

Requests are made against the base URL https://api.opply.com.

7 operations 7 paths 22 schemas 6 GET1 PATCH

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
0.0.0
Base URL
https://api.opply.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Opply Agents API declares 2 security schemes for authenticating requests. An API key is passed in the cookie as sessionid (cookieAuth). An API key is passed in the header as Authorization (tokenAuth).

  • tokenAuth — Token-based authentication with required prefix "Token"

Paths & Operations 7

Across 7 paths, the API surfaces 7 operations — 6 GET, 1 PATCH. Each is listed below with its method, path, parameters, and response codes.

Agents 7
GET
/api/v1/agents/admin/installations/
List installable agents for the current tenant (admin only)
api_v1_agents_admin_installations_list → 200
PATCH
/api/v1/agents/admin/installations/{agent_uuid}/
Set the installation status for an agent on the current tenant (admin only)
api_v1_agents_admin_installations_partial_update 1 param body → 200404
GET
/api/v1/agents/debug/system-tasks/
List agent (system) tasks for a company (staff cross-tenant; self otherwise)
api_v1_agents_debug_system_tasks_list → 200
GET
/api/v1/agents/fleet/
Fleet overview: all agents + per-agent install counts (MoR only)
api_v1_agents_fleet_list → 200
GET
/api/v1/agents/fleet/{slug}/
Fleet detail: one agent's run stats + install list (MoR only)
api_v1_agents_fleet_retrieve 1 param → 200
GET
/api/v1/agents/installations/me/
Get the active agent installation for the current tenant
api_v1_agents_installations_me_retrieve → 200204
GET
/api/v1/agents/mor-router/me/
Get the buyer's Merchant-of-Record tasks-router ('Opply')
api_v1_agents_mor_router_me_retrieve → 200

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are Task (30 properties), _FleetAgentDetailAgent (11 properties), FleetAgent (10 properties), _AgentRef (5 properties). Each schema is shown below with its type and property counts.

Task
object
30 properties 21 required
MorRouterMe
object
Whether the caller's MoR exposes an "Opply" tasks-router, and how to address it.
2 properties 2 required
_InstallationRef
object
4 properties 4 required
AgentFleetDetail
object
3 properties 3 required
_ShadowUserRef
object
2 properties 2 required
TaskPriorityEnum
string
low - Low medium - Medium high - High urgent - Urgent
Patched_SetStatusInput
object
1 property
UserMinimal
object
5 properties 5 required
_AgentRef
object
5 properties 5 required
_FleetAgentDetailAgent
object
11 properties 11 required
AgentInstallationStatusEnum
string
active - Active paused - Paused revoked - Revoked
RelatedItemInput
object
One write-side related-item: a target type + entity uuid.
2 properties 2 required
_CompanyRef
object
2 properties 2 required
_RunStats
object
5 properties 5 required
AgentInstallationMe
object
The shape the FE consumes — enough to address the agent and render its name.
4 properties 4 required
AgentInstallationAdminRow
object
2 properties 2 required
_InstalledBy
object
2 properties 2 required
TaskStatusEnum
string
open - Open inprogress - In Progress waitingapproval - Waiting Approval done - Done
_FleetInstallation
object
5 properties 5 required
_InstallCounts
object
4 properties 4 required
FleetAgent
object
One agent row on the fleet overview.
10 properties 10 required
_UserRef
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

opply-agents-api-openapi.yml Raw ↑

Other APIs Opply publishes across the network.

Opply Activity Feed API
Opply Admin panel API
Opply Agreements API
Opply api API
Opply App Orders API
Opply Brain API
Opply Brands API
Opply Buyer Documents API
Opply Buyer Financial Documents API
Opply Buyer Onboarding API
Opply Buyer self-onboarding API
Opply Buyers API
Where this information came from

This is an independent, third-party profile of Opply Agents 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.