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

Dream Sports Journeys API

Journey management operations — create, read, update, and delete journeys

Dream Sports Journeys API is one of 62 APIs that Dream Sports publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Journeys. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

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

Requests are made against a single base URL, http://localhost:8080.

5 operations 3 paths 5 schemas 3 GET1 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://auth.dream11.com/
Authentication
API Key
Contact
Raven Team
Resource Areas
1

Authentication & Security 1

Dream Sports Journeys API declares 1 security scheme for authenticating requests. An API key is passed in the header as TENANT-ID (TenantIdHeader). By default, every request must be authenticated.

Paths & Operations 5

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

Journeys 5

Journey management operations — create, read, update, and delete journeys

GET
/thunder/filters/
Get Filter Options
getFilters → 200401
GET
/thunder/ctas
List Journeys
listJourneys 6 params → 200401
POST
/thunder/ctas
Create Journey
createJourney 1 param body → 200400401
GET
/thunder/ctas/{ctaId}
Get Journey by ID
getJourney 1 param → 200401404
PUT
/thunder/ctas/{ctaId}
Update Journey
updateJourney 2 params body → 200400401404

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are RuleRequest (10 properties), JourneyRequest (7 properties), JourneyUpdateRequest (6 properties), ApiResponse (3 properties). Each schema is shown below with its type and property counts.

RuleRequest
object
10 properties 7 required
ErrorResponse
object
1 property
JourneyRequest
object
7 properties 3 required
JourneyUpdateRequest
object
6 properties
ApiResponse
object
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

dream-sports-journeys-api-openapi.yml Raw ↑

Other APIs Dream Sports publishes across the network.

Odin MCP Server
Dream Sports Access Keys API
Dream Sports Access Keys API
Dream Sports Account API
Dream Sports Acquisition API
Dream Sports Admin API
Dream Sports Admin - Console Users API
Dream Sports Apps API
Dream Sports Auth API
Dream Sports Authentication API
Dream Sports Behaviour Tags API
Dream Sports Cache Management API
Where this information came from

This is an independent, third-party profile of Dream Sports Journeys 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.