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

Uplika Automations API

The Automations API from Uplika — 14 operation(s) for automations.

Uplika Automations API is one of 10 APIs that Uplika publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

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

20 operations 14 paths 1 schemas 2 DELETE8 GET1 PATCH8 POST1 PUT

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.uplika.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Uplika Automations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (apiKey). By default, every request must be authenticated.

  • apiKey — An API key from the dashboard.

Paths & Operations 20

Across 14 paths, the API surfaces 20 operations — 2 DELETE, 8 GET, 1 PATCH, 8 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Automations 20
GET
/v1/automations/templates
Every template: its id, channels, parameters (JSON Schema) and the reviewed…
getV1AutomationsTemplates → default
GET
/v1/automations/capabilities
Per channel: which triggers and steps a flow may use there
getV1AutomationsCapabilities → default
POST
/v1/automations/quick/{template}
Create a flow from a template and its parameters. The usual way
postV1AutomationsQuickByTemplate 1 param body → default
POST
/v1/automations
Create a flow from a full document
postV1Automations body → default
GET
/v1/automations
Every flow in the workspace, newest first
getV1Automations → default
POST
/v1/automations/validate
Check a document without saving it.
postV1AutomationsValidate → default
GET
/v1/automations/{id}
One flow with its document, version, run counts and the channel's capabilities
getV1AutomationsById 1 param → default
PUT
/v1/automations/{id}
Replace the document.
putV1AutomationsById 1 param body → default
PATCH
/v1/automations/{id}
Rename, or turn on and off with enabled
patchV1AutomationsById 1 param → default
DELETE
/v1/automations/{id}
Delete the flow, its runs and its versions
deleteV1AutomationsById 1 param → default
POST
/v1/automations/{id}/enable
Turn it on. From this moment messages go to real people
postV1AutomationsByIdEnable 1 param → default
POST
/v1/automations/{id}/disable
Turn it off. Runs that are waiting do not continue
postV1AutomationsByIdDisable 1 param → default
POST
/v1/automations/{id}/duplicate
Copy it as a new draft, with the same document and template parameters
postV1AutomationsByIdDuplicate 1 param → default
POST
/v1/automations/{id}/past-comments/preview
Count without sending: how many comments would get the flow, and why the others…
postV1AutomationsByIdPastCommentsPreview 1 param → default
POST
/v1/automations/{id}/past-comments
Start sending. Answers 202 with the job; one job per flow at a time
postV1AutomationsByIdPastComments 1 param body → default
GET
/v1/automations/{id}/past-comments
The most recent job: its status, how many were sent, and how many are queued.
getV1AutomationsByIdPastComments 1 param → default
DELETE
/v1/automations/{id}/past-comments
Stop the running job. Comments already answered stay answered
deleteV1AutomationsByIdPastComments 1 param → default
GET
/v1/automations/{id}/runs
What happened each time it fired: status, the reason it stopped, and a step log
getV1AutomationsByIdRuns 3 params body → default
GET
/v1/automations/{id}/versions
Saved versions of the document, newest first
getV1AutomationsByIdVersions 1 param → default
GET
/v1/automations/{id}/versions/{version}
One saved version of the document
getV1AutomationsByIdVersionsByVersion 2 params → default

Schemas 1

The contract defines 1 schema that model the data the API accepts and returns. The most detailed is Error (1 property). Each schema is shown below with its type and property counts.

Error
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

uplika-com-automations-api-openapi.yml Raw ↑

Other APIs Uplika publishes across the network.

Uplika API
Uplika Connecting channels API
Uplika Errors API
Uplika Inbox and contacts API
Uplika Media API
Uplika Platforms API
Uplika Posts API
Uplika Replies and insights API
Uplika Troubleshooting and FAQ API
Where this information came from

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