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

Antavo Async Events API

The Async Events API from Antavo — 2 operation(s) for async events.

Antavo Async Events API is one of 29 APIs that Antavo publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

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

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

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

2 operations 2 paths 12 schemas 1 GET1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0.0
Base URL
https://api.antavo.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Antavo Async Events API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 2

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

Async Events 2
GET
/v1/async/events/{correlation_id}
Query the status of async event processing
1 param → 200400
POST
/v1/async/events
Submit an async event
body → 200400401

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are CorrelationIDResponseCustomer (18 properties), CheckoutData (8 properties), CheckoutRequestBody (6 properties), PointAddRequestBody (6 properties). Each schema is shown below with its type and property counts.

PointAddRequestBody
object
6 properties 3 required
CorrelationIDResponse
object
3 properties 2 required
Account
object
2 properties
CorrelationIDResponsePayload
object
2 properties 2 required
CheckoutRequestBody
object
6 properties 3 required
ProcessingError
object
2 properties 2 required
ProcessingSuccess
object
2 properties 2 required
CorrelationIDResponseCustomer
object
18 properties
Event_response
object
Successful event submission
3 properties
CheckoutData
object
8 properties 1 required
SubmittedLoyaltyEvent
object
5 properties
PointAddData
object
3 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

antavo-async-events-api-openapi.yml Raw ↑

Other APIs Antavo publishes across the network.

Antavo Activities API
Antavo Authentication API
Antavo Cart API
Antavo Challenges API
Antavo Clubs API
Antavo Content consumption API
Antavo Contests API
Antavo Coupon pools API
Antavo Coupons API
Antavo Customer lists API
Antavo Customers API
Antavo Data extensions API
Where this information came from

This is an independent, third-party profile of Antavo Async Events 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.