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

Spruce Health Internal Endpoints API

The Internal Endpoints API from Spruce Health — 3 operation(s) for internal endpoints.

Spruce Health Internal Endpoints API is one of 15 APIs that Spruce Health publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, https://api.sprucehealth.com/v1.

3 operations 3 paths 14 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.sprucehealth.com/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Spruce Health Internal Endpoints API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (spruceAPIToken). By default, every request must be authenticated.

  • spruceAPIToken — API token provided by Spruce should be passed in an "Authorization" header with the value "Bearer "

Paths & Operations 3

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

Internal Endpoints 3
GET
/internalendpoints
List all internal endpoints
InternalEndpoints → 200500
POST
/internalendpoints/{internalEndpointId}/calls
Create an outbound proxy call
PostCreateProxyCall 2 params body → 200400422500
POST
/internalendpoints/{internalEndpointId}/conversations
Send a message from an internal endpoint
PostMessageFromEndpoint 2 params body → 200400422500

Schemas 14

The contract defines 14 schemas that model the data the API accepts and returns. The most detailed are teammate (7 properties), endpoint (7 properties), conversation_messagePost (5 properties), organization (4 properties). Each schema is shown below with its type and property counts.

objectType
string
String representing the object's type
internalEndpoint
object
4 properties 3 required
conversation_messagePost
object
5 properties 1 required
organization
object
4 properties 4 required
error
object
3 properties 3 required
team
object
4 properties 4 required
conversation_messageBodyElement
object
An element of a message body. This can be either a text or page type element. A text element is a string of text to be placed in the message. A page element is…
2 properties 2 required
conversation_messagePost_attachment
object
2 properties 2 required
teammate
object
7 properties 6 required
teammate_id
string
The id of the teammate
endpoint_id
string
The id of the endpoint. For secure (Spruce Link) endpoints, the id format depends on where the endpoint is returned: the list internal endpoints API returns th…
endpoint
object
7 properties 6 required
conversation_messagePost_secureConversationSelection
string
anyavailablesecureconversation: The system will first try to deliver messages using conversations from the specified internal endpoint. Then it will try to del…
asyncRequest_id
string
The id of an asynchronous request

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

spruce-health-internal-endpoints-api-openapi.yml Raw ↑

Other APIs Spruce Health publishes across the network.

Spruce Health Contact Fields API
Spruce Health Contact Tags API
Spruce Health Contacts API
Spruce Health Conversation Item API
Spruce Health Conversation Tags API
Spruce Health Conversations API
Spruce Health Media API
Spruce Health Organization API
Spruce Health Phone Lines API
Spruce Health Saved Messages API
Spruce Health Scheduled Messages API
Spruce Health Teams API
Where this information came from

This is an independent, third-party profile of Spruce Health Internal Endpoints 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.