Weave Messaging API
Two-way SMS/text messaging with patients.
Weave Messaging API is one of 8 APIs that Weave publishes 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, API documentation, and an API reference.
This API exposes 7 operations across 6 paths, and defines 4 schemas. It is described by OpenAPI 3.0.3, at version 1.0.
Requests are made against a single base URL, https://api.weaveconnect.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 2
Weave Messaging API declares
2 security schemes
for authenticating requests.
It supports OAuth 2.0 (oauth2) using the authorizationCode flow.
It accepts HTTP bearer tokens (bearerAuth).
By default, every request must be authenticated.
oauth2— OAuth 2.0 access token issued by Weave's OIDC provider. Authorization and token endpoints are served under https://auth.weaveconnect.com/oauth2/default (issuer…bearerAuth— OAuth 2.0 bearer access token passed as Authorization: Bearer ACCESSTOKEN.
Paths & Operations 7
Across 6 paths, the API surfaces 7 operations — 5 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.
Two-way SMS/text messaging with patients.
Schemas 4
The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Message (7 properties), MessageInput (3 properties), PhoneNumber (3 properties), Error (1 property). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Weave 7
Other APIs Weave publishes across the network.