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

BotSociety Conversations API

Manage conversations (legacy apisociety 2.0 API)

BotSociety Conversations API is one of 4 APIs that BotSociety publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, https://app.botsociety.io.

4 operations 3 paths 2 schemas 1 DELETE2 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://app.botsociety.io
Authentication
API Key, API Key
Contact
License
ISC
Resource Areas
1

Authentication & Security 2

BotSociety Conversations API declares 2 security schemes for authenticating requests. An API key is passed in the header as user_id (user_id). An API key is passed in the header as api_key_public (api_key_public). By default, every request must be authenticated.

  • user_id — The Botsociety user id, obtained from the Botsociety app.
  • api_key_public — The Botsociety public API key, obtained from the Botsociety app.

Paths & Operations 4

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

Conversations 4

Manage conversations (legacy apisociety 2.0 API)

GET
/apisociety/2.0/npm/
Verify credentials
authCheck → 200401
POST
/apisociety/2.0/npm/conversations/
Create a conversation
createConversation body → 200401
GET
/apisociety/2.0/npm/conversations/{conversationId}
Get a conversation
getConversations 1 param → 200401404
DELETE
/apisociety/2.0/npm/conversations/{conversationId}
Delete a conversation
deleteConversation 1 param → 200401404

Schemas 2

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

Conversation
object
A conversation (design).
2 properties
Error
object
Error response body.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

botsociety-conversations-api-openapi.yml Raw ↑

Other APIs BotSociety publishes across the network.

BotSociety Designs API
BotSociety Messages API
BotSociety Variables API
Where this information came from

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