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

PolyAPI Assistants API

Manage AI assistants and conversations for AI-powered document assistance and discovery.

PolyAPI Assistants API is one of 10 APIs that PolyAPI publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 10 JSON Schema definitions.

Tagged areas include Assistants. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 10 JSON Schemas.

This API exposes 4 operations across 2 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 2 base URLs: https://na1.polyapi.io, https://eu1.polyapi.io.

4 operations 2 paths 3 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Servers
https://na1.polyapi.io
https://eu1.polyapi.io
Authentication
HTTP Bearer
Contact
Terms of Service
Resource Areas
1

Authentication & Security 1

PolyAPI Assistants API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (API Key) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — PolyAPI uses Bearer token authentication. Include your API key in the Authorization header as 'Bearer {your-api-key}'.

Paths & Operations 4

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

Assistants 4

Manage AI assistants and conversations for AI-powered document assistance and discovery.

GET
/assistants/{slug}/conversations
PolyAPI List conversations
listConversations 1 param → 200401
POST
/assistants/{slug}/conversations
PolyAPI Create a conversation
createConversation 1 param body → 201401
GET
/assistants/{slug}/conversations/{conversationSlug}
PolyAPI Get a conversation
getConversation 2 params → 200401404
DELETE
/assistants/{slug}/conversations/{conversationSlug}
PolyAPI Delete a conversation
deleteConversation 2 params → 204401404

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are Conversation (5 properties), Error (3 properties), ConversationInput (1 property). Each schema is shown below with its type and property counts.

Error
object
3 properties
ConversationInput
object
1 property 1 required
Conversation
object
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

polyapi-assistants-api-openapi.yml Raw ↑

Other APIs PolyAPI publishes across the network.

PolyAPI API Functions API
PolyAPI Client Functions API
PolyAPI Environments API
PolyAPI Jobs API
PolyAPI Schemas API
PolyAPI Server Functions API
PolyAPI Triggers API
PolyAPI Variables API
PolyAPI Webhooks API
Where this information came from

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