OPERATION-500 - Return a single Operation by ID

get

https://example.com/v1/shop/operations/{operationId}

Returns the details of a single Operation visible to the caller's account on the effective store.

Feature flag

Requires OPERATIONS to be active.

User scoping

Only ACCOUNT users are allowed.

Store scoping

Effective store is the dj-store header if provided, otherwise the tenant default store.
Caller must be attached to the effective store; otherwise 403.

Visibility

Operation must be ACTIVE and currently in time window (now within [startDate, endDate], inclusive).
PUBLIC are visible to all accounts on the effective store.
PRIVATE require an explicit association with the caller's account.
If the Operation is not visible under these rules, the API returns 404.

Locales

Optional locale query param (IETF, e.g. en-GB). If unknown for the store, the store default locale is used (fallback).

Scope

This endpoint returns Operation metadata only (no product lines). Use /v1/shop/operations/{operationId}/lines for items.

Recent Requests

Time	Status	User Agent
Retrieving recent requests…

Loading…

Path Params

operationId

string

required

Unique identifier of the Operation

Query Params

locale

string

Locale to use for localized fields (e.g., name).
The provided locale must belong to the allowed locales of the store bound to the Operation.
If the provided locale is unknown for that store, the store default locale is used (fallback).

Headers

dj-client

string

enum

required

Specifies the client type making the request.

OPERATOR: Platform operator user.
ACCOUNT: Customer account user.
SUPPLIER: Supplier managing orders.

Allowed:

dj-api-key

string

required

API key required for authentication. Must be valid and linked to the requesting user.

dj-store

string

(Optional) Store ID in multi-store environments.

dj-store-view

string

(Optional) Store view ID in multi-store environments.

customer-account-id

string

(Optional) Customer account ID in multi-account customer user.

Responses

401

Authentication required.

403

Forbidden. Either unauthorized user type, feature disabled, or store membership denied.

404

Operation not found or not visible to the caller on the effective store.

422

One or more query parameters are invalid.

500

Unexpected server error.

200Operation details successfully retrieved.