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

Hilos WhatsApp API

The WhatsApp API from Hilos — 3 operation(s) for whatsapp.

Hilos WhatsApp API is one of 6 APIs that Hilos publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

Requests are made against a single base URL, https://api.hilos.io.

4 operations 3 paths 12 schemas 1 DELETE2 GET1 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.hilos.io/api/
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Hilos WhatsApp API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (tokenAuth). By default, every request must be authenticated.

  • tokenAuth — Token-based authentication with required prefix "Token"

Paths & Operations 4

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

WhatsApp 4
GET
/api/channels/whatsapp/template
List WhatsApp Templates
List WhatsApp Templates 10 params → 200
DELETE
/api/channels/whatsapp/template/{id}
Delete WhatsApp Template
Delete WhatsApp Template 1 param → 204
GET
/api/channels/whatsapp/template/{id}
Get WhatsApp Template
Get WhatsApp Template 1 param → 200
POST
/api/channels/whatsapp/template/{id}/send
Send a WhatsApp Template
Send a WhatsApp Template Message 1 param body → 201

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are WhatsAppTemplateRead (10 properties), WhatsAppTemplateSimpleRead (9 properties), SimpleChannel (8 properties), PaginatedWhatsAppTemplateSimpleReadList (4 properties). Each schema is shown below with its type and property counts.

SimpleChannel
object
8 properties 2 required
LanguageEnum
string
ChannelTypeEnum
string
ChannelStatusEnum
string
ChannelProviderEnum
string
CategoryEnum
string
WhatsAppTemplateRead
object
10 properties 5 required
WhatsAppTemplateSend
object
2 properties 1 required
WhatsAppTemplateStatusEnum
string
WhatsAppTemplateSimpleRead
object
9 properties 5 required
PaginatedWhatsAppTemplateSimpleReadList
object
4 properties
WhatsAppTemplateSendPublicResponse
object
2 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hilos-whatsapp-api-openapi.yml Raw ↑

Other APIs Hilos publishes across the network.

Hilos Contact API
Hilos Conversation API
Hilos Flow Execution API
Hilos Flow Execution Contact API
Hilos User API
Where this information came from

This is an independent, third-party profile of Hilos WhatsApp 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.