mutation CreateShop($request: CreateShopCommandRequestInput!) {
CreateShop(request: $request) {
salesChannelId
}
}{
"request": {
"name": "string",
"url": "string",
"username": "string",
"password": "string",
"apiKey": "string",
"companyId": "id"
}
}{
"data": {
"CreateShop": {
"salesChannelId": "string"
}
}
}CreateShop
Creates a new JTL-Wawi-managed online shop account. The request is validated first; then a live connection and credentials test is run against the shop. If either fails, no shop is created. The customer group, currency and language with the lowest ID are assigned as defaults; they can be changed afterwards via “PUT /v2/sales-channels//shop/customer-groups” or “SaveShopCustomerGroups”, “PUT /v2/sales-channels//shop/currencies” or “SaveShopCurrencies”, and the corresponding language endpoint. Running the connection test updates the stored connection state, also when simulating. When “simulate” is true, only validation and the connection test run; no shop is created and no sales channel id is returned (“salesChannelId” is omitted in the REST response and null in GraphQL). The sales channel id is assigned by the server and cannot be supplied.
If a request with this mutation’s Idempotency-Key was already completed, the response’s extensions contains an idempotency.{responseName} entry with wasReplayed: true.
CreateShop(request: CreateShopCommandRequestInput!): CreateShopResult!Arguments
Returns
Sales channel id of the created shop. Opaque, tenant-local composite identifier (not a UUID); use this value to address the shop in follow-up calls. Omitted in the REST response (null in GraphQL) when "simulate" is true, because no shop was created.
mutation CreateShop($request: CreateShopCommandRequestInput!) {
CreateShop(request: $request) {
salesChannelId
}
}{
"request": {
"name": "string",
"url": "string",
"username": "string",
"password": "string",
"apiKey": "string",
"companyId": "id"
}
}{
"data": {
"CreateShop": {
"salesChannelId": "string"
}
}
}Was this page helpful?