GET
Get event details by ID

Authorizations

X-API-Key
string
header
required

ISV / partner credential — public half. Required on every request.

Identifies the integration partner (ISV) making the call. Issued by Dime Trades when the ISV is onboarded and sent on every /partner/* endpoint:

  • On the two partner endpoints that create accounts or issue tokens (POST /partner/customers, POST /partner/customers/login), it is accompanied by X-API-Secret and is the only authentication — there is no user token yet.
  • On every other partner endpoint it is sent alongside the user's Authorization: Bearer <token>: the API key says which platform is calling, the bearer token says which user it is calling for.

Credentials are scoped to one or more brands; using a key with a brandId outside that scope returns 403. Staging and production keys are separate. The key identifies your platform — treat it as a backend credential.

Query Parameters

Id
string
required

Event ID. Note the capital I — id will not work.

Pattern: ^[0-9]+$
Example:

"5454"

marketGroupId
string

Restrict markets to one sport-scoped category/tab (e.g. "Player Props") — the id from GET /market-groups. This filters markets only — the requested event is always returned if it exists, regardless of its category. If it has no markets in the requested group (which is always true for non-sports events, since their marketGroupId is always null and can never match), markets comes back as [] rather than the event being dropped or erroring.

Pattern: ^[0-9]+$
Example:

"48"

Response

Event details returned.

data
object

Note the shape: the event is returned inside an events array, exactly as on GET /events, even though this endpoint only ever resolves a single event. Read it as data.events[0], not data. There is no pagination object here — that is the only structural difference between the two endpoints' payloads.

errors
array