-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathapis.yml
More file actions
233 lines (233 loc) · 8.32 KB
/
Copy pathapis.yml
File metadata and controls
233 lines (233 loc) · 8.32 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
aid: artera
name: Artera
description: >-
Artera is a healthcare technology company providing an AI-powered patient
communication and engagement platform used by hospitals, health systems, and
medical practices to unify how they reach and care for patients. The platform
orchestrates SMS, voice, email, and chat across the patient journey —
appointment scheduling and reminders, patient intake, payments, referral
management, care-gap closure, prescription refills, multilingual engagement,
and after-hours call routing and triage — increasingly through agentic AI.
Artera connects to the EHR and patient-facing vendors via API, FHIR, and
HL7v2 integrations with major systems including Epic, Oracle Health, MEDITECH,
athenahealth, eClinicalWorks, Veradigm, NextGen, Greenway, ModMed, AdvancedMD,
and Netsmart. The company maintains a strong security and compliance posture
(SOC 2 Type 2, HITRUST, ISO 27001/27017/27018/27701, FedRAMP, HIPAA). It was
surfaced as a Techstars portfolio company and added to the API Evangelist
network.
url: https://raw.githubusercontent.com/api-evangelist/artera/refs/heads/main/apis.yml
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: false
label: Hosted service · you call their endpoint
confidence: medium
source:
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: unknown
onboarding: unknown
trial: false
try_now: false
public: false
label: Unknown
confidence: low
source: []
generated: '2026-07-22'
method: derived
image: https://artera.io/wp-content/uploads/2024/03/cropped-favicon-300x300.png
x-type: company
x-source: vc-portfolio
x-backed-by:
- techstars
x-tier: stub
x-tier-reason: portfolio-lead
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-18'
tags:
- Company
- Healthcare
- Patient Communication
- Patient Engagement
- Health IT
- EHR Integration
- FHIR
- Agentic AI
apis:
- name: Artera Messaging API (MAPI)
description: >-
Artera's outbound SMS API, marketed to health systems and Artera Marketplace
vendors as the SendMessage API. It sends real-time text messages to patients
from the health system's trusted Artera number, authenticated with OAuth 2.0
plus an API key and restricted by IP allowlist. It optionally returns a
Deliverability Webhook carrying the message status (received, sent, delivered,
undelivered, failed) and a Patient Response Webhook when a patient replies
through the Secure Messaging Portal. MAPI is SMS-only — not voice or email —
delivers immediately with no advance scheduling, permits and auto-shortens
URLs, and deliberately does NOT apply Artera's TCPA quiet-hours or Holiday
Hours adjustments, leaving send-time compliance to the caller. The full
specification is published only inside Artera's registration-gated developer
portal.
humanURL: https://knowledge.artera.io/en_US/use-cases-and-add-ons/messaging-api-mapi
baseURL: https://api.artera.io
tags:
- Messaging
- SMS
- Patient Communication
- Healthcare
- Webhook
tags_raw:
- Messaging
- SMS
- Patient Communication
- Healthcare
- Webhooks
properties:
- type: Documentation
url: https://knowledge.artera.io/en_US/use-cases-and-add-ons/messaging-api-mapi
- type: APIReference
url: https://apidocs.artera.io/docs/0dbfeef0-de7e-4dee-8435-09c5cffd7ed1/specification
- type: DeveloperPortal
url: https://apidocs.artera.io/login
- type: Webhooks
url: asyncapi/artera-webhooks.yml
- type: Authentication
url: authentication/artera-authentication.yml
- type: ErrorCatalog
url: errors/artera-problem-types.yml
- type: StatusPage
url: https://status.artera.io/
- name: Artera Extended Data API
description: >-
A Marketplace-vendor API that attaches custom partner content to a patient's
upcoming or past appointment or encounter, including post-discharge content.
Vendors call Artera with Appointment and/or Encounter IDs that must match the
EMR records already stored in Artera, together with the corresponding Location
ID, and the supplied content is rendered into Artera messages through named
Smart Phrase tokens — {eventPartnerPreCheckIn}, {eventPartnerPostApptRx},
{eventPartnerRescheduling}, {eventPartnerTelehealth}, {eventPartnerCheckIn} for
appointments and {dischargePartnerRx} for encounters. The tokens can be used in
manual messages, Quick Responses, Triggers, Conversation Flows and Broadcasts;
missing data renders blank and the message still sends. Specification access
requires developer-portal registration.
humanURL: https://knowledge.artera.io/en_US/marketplace/extended-data-api-appointments-and-encounters
baseURL: https://api.artera.io
tags:
- Appointments
- Encounters
- Healthcare
- Marketplace
- Patient Engagement
properties:
- type: Documentation
url: https://knowledge.artera.io/en_US/marketplace/extended-data-api-appointments-and-encounters
- type: DeveloperPortal
url: https://apidocs.artera.io/login
- type: Authentication
url: authentication/artera-authentication.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
- FN: APIs.json
email: info@apis.io
common:
- type: Website
url: https://artera.io/
- type: Blog
url: https://artera.io/blog/
- type: Integrations
url: https://artera.io/integrations/
- type: Support
url: https://artera.io/contact-us/
- type: TermsOfService
url: https://artera.io/terms-of-service/
- type: PrivacyPolicy
url: https://artera.io/privacy-policy/
- type: TrustCenter
url: https://safebase.artera.io/
- type: Compliance
url: https://artera.io/trust-center/
- type: Security
url: https://artera.io/vulnerability-disclosure/
- type: VulnerabilityDisclosure
url: security/artera-vulnerability-disclosure.yml
- type: DomainSecurity
url: security/artera-domain-security.yml
- type: Documentation
url: https://knowledge.artera.io/
- type: DeveloperPortal
url: https://apidocs.artera.io/login
- type: APIReference
url: https://apidocs.artera.io/docs/0dbfeef0-de7e-4dee-8435-09c5cffd7ed1/specification
- type: GettingStarted
url: https://knowledge.artera.io/en_US/get-started
- type: HelpCenter
url: https://support.wellapp.com/s/
- type: StatusPage
url: https://status.artera.io/
- type: ChangeLog
url: changelog/artera-changelog.yml
- type: ReleaseNotes
url: https://knowledge.artera.io/en_US/release-notes/2026-releases
- type: Deprecation
url: lifecycle/artera-lifecycle.yml
- type: Lifecycle
url: lifecycle/artera-lifecycle.yml
- type: Authentication
url: authentication/artera-authentication.yml
- type: Conventions
url: conventions/artera-conventions.yml
- type: ErrorCatalog
url: errors/artera-problem-types.yml
- type: Webhooks
url: asyncapi/artera-webhooks.yml
- type: Conformance
url: conformance/artera-conformance.yml
- type: Sandbox
url: sandbox/artera-sandbox.yml
- type: Plans
url: plans/artera-plans-pricing.yml
- type: RateLimits
url: rate-limits/artera-rate-limits.yml
- type: Packages
url: packages/artera-packages.yml
- type: LLMsTxt
url: llms/artera-llms.txt
- type: SignUp
url: https://artera.io/request-a-demo/
- type: Login
url: https://app.wellapp.com/login
- type: TechnicalSpecifications
url: https://knowledge.artera.io/en_US/technical-specifications/1239793-technical-specifications
x-enrichment:
date: '2026-08-15'
status: minimal
artifacts_added: 14
pass: local-v1
x-coverage:
state: gated
reason: partner-login
detail: >-
Artera runs a real API program — a Messaging API (MAPI) and an Extended Data
API, both named in its public knowledge base and monitored as "SendMessage
API" on its status page — but every specification sits behind account
registration at apidocs.artera.io, whose own TLS certificate expired
2026-01-27, so the documented portal link fails certificate validation and
only resolves over plain http to an SPA that returns the same HTML shell for
/openapi.json as for every other path.
evidence:
- url: https://apidocs.artera.io/docs/0dbfeef0-de7e-4dee-8435-09c5cffd7ed1/specification
status: 000
- url: https://apidocs.artera.app/openapi.json
status: 200
- url: https://api.artera.io/openapi.json
status: 404
- url: https://api.artera.io/health
status: 200
- url: https://knowledge.artera.io/en_US/use-cases-and-add-ons/messaging-api-mapi
status: 200
checked: '2026-08-15'