Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

The Interaction Company Of California Messaging API

Send messages to Poke programmatically.

The Interaction Company Of California Messaging API is published by The Interaction Company Of California on the APIs.io network, described by a machine-readable OpenAPI specification.

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

This API exposes 2 operations across 2 paths, and defines 2 schemas. It is described by OpenAPI 3.1.0, at version v1.

Requests are made against a single base URL, https://poke.com.

2 operations 2 paths 2 schemas 2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
v1
Base URL
https://poke.com
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

The Interaction Company Of California Messaging API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — V2 API key generated in Kitchen, sent as Authorization: Bearer YOURAPIKEY. Legacy pk-prefixed V1 keys work only with the deprecated inbound-sms webhook.

Paths & Operations 2

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

Messaging 2

Send messages to Poke programmatically.

POST
/api/v1/inbound/api-message
Send a message to Poke
sendInboundMessage body → 200401
POST
/api/v1/inbound-sms/webhookdeprecated
Legacy inbound SMS webhook (deprecated)
sendInboundSmsWebhook → 200401

Schemas 2

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

MessageResult
object
2 properties 1 required
InboundMessage
object
Any JSON object; the entire body is forwarded to the agent as context. The documented convention is a single message field.
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

the-interaction-company-of-california-messaging-api-openapi.yml Raw ↑