ShopEazydevelopers
API referenceMerchant API BetaStudio

How a make is going

Beta
Credentials
  • OAuth access token
Scopes
store:read
GET
/v1/merchant/stores/{storeId}/studio/jobs/{jobId}

Running, done (with the result and files) or failed (nothing charged).

Access: OAuth scope store:read; not write-gated.

Authorization

merchantOAuth store:read
headerAuthorizationBearer <token>

OAuth 2.1 (authorization code + PKCE S256, public clients, dynamic registration) for connected AI apps. Effective power is scopes granted AND the person's role today AND the plan. orders:refund, billing:write and team:write are opt-in on the consent screen. Write implies read for marketing:read and messages:read, so a grant holding marketing:write passes a marketing:read check, and messages:send passes messages:read.

Scope: store:read

Path Parameters

storeId*string

A store the person can reach. Any other id answers 404, never 403.

jobId*string

A make's job id, from POST /studio/makes.

Response Body

OK

application/json
  1. response
data*
Example Request
curl -X GET 'https://api.shopeazy.co/v1/merchant/stores/<storeId>/studio/jobs/<jobId>' \  -H 'Authorization: Bearer <access_token>'
Example Response
{  "data": {    "id": "string",    "kind": "string",    "status": "running",    "label": "string",    "result": null,    "files": [      {        "id": "string",        "kind": "string",        "media": "image",        "category": "string",        "url": "string",        "posterUrl": "string",        "about": "string",        "versionOf": "string",        "usedIn": [          {            "kind": "string",            "id": "string"          }        ],        "uses": 0,        "createdAt": 0      }    ],    "error": "string",    "createdAt": 0  }}