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

AppsMax Campaigns API

Рассылки и их запуск.

AppsMax Campaigns API is one of 9 APIs that AppsMax publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Campaigns. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a getting-started guide, authentication docs, rate-limit docs, and pricing.

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

Requests are made against a single base URL, https://telegram.appsmax.ru/api/v1.

4 operations 3 paths 7 schemas 2 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1.1
Base URL
https://telegram.appsmax.ru/api/v1
Authentication
HTTP Bearer, API Key
Contact
Resource Areas
1

Authentication & Security 2

AppsMax Campaigns API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (AppsMax API token) (bearerAuth). An API key is passed in the header as X-Api-Token (apiTokenHeader). By default, every request must be authenticated.

  • bearerAuth — Рекомендуемый вариант: Authorization: Bearer YOURAPITOKEN
  • apiTokenHeader — Fallback для клиентов без Bearer auth. Не передавайте токен в URL.

Paths & Operations 4

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

Campaigns 4

Рассылки и их запуск.

GET
/campaigns
Получить кампании
listCampaigns 10 params → 200401403404422429500
POST
/campaigns
Создать кампанию
createCampaign 1 param body → 200201400401403404409413
GET
/campaigns/{campaign}
Получить кампанию
getCampaign 1 param → 200401403404429500
POST
/campaigns/{id}/run
Запустить кампанию
runCampaign 1 param → 200400401403404413415422

Schemas 7

The contract defines 7 schemas that model the data the API accepts and returns. The most detailed are Campaign (15 properties), CampaignCreateRequest (5 properties), CollectionEnvelope (3 properties), ResourceEnvelope (1 property). Each schema is shown below with its type and property counts.

CampaignCollection
CampaignCreateRequest
object
5 properties 4 required
ApiError
object
1 property 1 required
CollectionEnvelope
object
3 properties 1 required
ResourceEnvelope
object
1 property 1 required
CampaignResponse
Campaign
object
15 properties 5 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

appsmax-rest-api-v1-campaigns-api-openapi.yml Raw ↑

Other APIs AppsMax publishes across the network.

AppsMax Access API
AppsMax Applications API
AppsMax Bots API
AppsMax Funnels API
AppsMax Interactive menu API
AppsMax Miniapps API
AppsMax Organizations API
AppsMax Subscribers API
Where this information came from

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