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

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.2.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.2.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 ↑
Where this information came from

This is an independent, third-party profile of The Interaction Company Of California Messaging 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.