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

Disco Partner Integration API

The API used by Disco partners that provide their own UI experience. Returns Disco advertiser recommendations for post-purchase placements and accepts the widget, brand, product and element events (single and batched) that record user actions against those placements. Authenticated with an x-api-key header.

This API exposes 3 operations across 3 paths, organized into 2 resource areas, and defines 25 schemas. It is described by OpenAPI 3.0.0, at version 1.0.0.

Requests are made against 2 base URLs: https://partners.disconetwork.com, https://partners.disconetwork-staging.com.

3 operations 3 paths 25 schemas 3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
1.0.0
Base URL
https://partners.disconetwork.com
Authentication
API Key
Resource Areas
2

Authentication & Security 1

Disco Partner Integration API declares 1 security scheme for authenticating requests. An API key is passed in the header as x-api-key (ApiKey).

  • ApiKey — Key Auth: Requests contain a valid x-api-key in the request headers.

Paths & Operations 3

Across 3 paths, the API surfaces 3 operations — 3 POST. They span 2 resource areas: Events, Recommendations. Each is listed below with its method, path, parameters, and response codes.

Events 2
POST
/events
Create an event used to record user actions
createAnEventUsedToRecordUserActions 1 param body → 201400401403500
POST
/events/batch
Create a batch of events used to record user actions
createABatchOfEventsUsedToRecordUserActions 1 param body → 202207400401403500502
Recommendations 1
POST
/recommendations
Get Disco Advertiser Recommendations
getDiscoAdvertiserRecommendations 1 param body → 200400401403500

Schemas 25

The contract defines 25 schemas that model the data the API accepts and returns. The most detailed are CommonRequestProperties (9 properties), ProductSummaryDto (8 properties), RecommendationsResponse (7 properties), UserDetails (7 properties). Each schema is shown below with its type and property counts.

CommonRequestProperties
object
The properties shared between the recommendations and event request payloads
9 properties 2 required
UserDetails
object
7 properties
PlacementDetailsObject
object
Contains details about the placement of the offers within the UI
5 properties 2 required
ResolvedWidget
object
Selected widget configuration. Null when unavailable.
6 properties 5 required
RecommendationsRequest
The body of the request for the /recommendations endpoint
RecommendationsResponse
object
The response body from the recommendations endpoint
7 properties 4 required
BaseEventProperties
object
The properties shared on all events
3 properties 3 required
BrandEventProperties
object
3 properties 3 required
RequiredBrandEventProperties
object
1 property 1 required
ProductEventProperties
object
1 property 1 required
WidgetEventRequest
BrandDisplayRequest
BrandClickRequest
ProductDisplayRequest
ProductClickRequest
ElementClickRequest
EventRequest
Request body for hitting the /event endpoint
BatchEventRequest
object
Request body for hitting the /events/batch endpoint
1 property 1 required
BatchEventResult
object
The processing result for a single event in the batch
2 properties 2 required
BatchEventResponse
object
The result of processing a batch of events
3 properties 3 required
AddressRequestDto
object
The structure of an address in our request bodies
6 properties
ProductSummaryDto
object
A description of a purchased item, to be provided in our requests
8 properties
PurchaseAttributes
object
Free-form attributes for a purchased item
2 properties
ExperimentSummaryDTO
object
Properties describing an actively running product experiment
2 properties 2 required
CostDetailsSummary
object
Contains all details pertaining to the cost of the parent container item
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

disconetwork-partner-api.yml Raw ↑
Where this information came from

This is an independent, third-party profile of Disco Partner Integration 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.