* Fix issue on fixed total amount discount when using includes tax (#3472) The calculation of the fixed discount amount breaks when having includes_tax setting active, due to the line item totals are incorrect and returning everything as 0, thus the totalItemPercentage will be Infinitiy due to the division by a subtotal of 0 * chore: Add missing changeset for @medusajs/medusa * feat(medusa): Improve performance of Products domain (#3417) * feat(medusa): Improve product update performances * fix tests and update * update mock repo * improve repo * cleanup * fix * cleanup + bulk emit + unit test fix * improvements * improve * fix unit tests * fix export * fix product update handler * enhance mock repo * fix import integration * fix end point tests * revert mock repo product variant * fix unit * cleanup * cleanup * address feedback * fix quotes in tests * address feedback * Create new-tips-mate.md * use types * chore: Remove integration-tests from changeset * chore(release): v1.7.14 * chore(docs): Generated Docs Announcement Bar (automated) (#3489) Co-authored-by: olivermrbl <olivermrbl@users.noreply.github.com> * fix(medusa): EventBusService.emit using Redis mock (#3491) * Fix eventBusService.emit using redis mock * revert gitignore * enqueuer * unit test add redis_url * fix test * chore(docs): Generated Services Reference (automated) (#3490) Co-authored-by: olivermrbl <olivermrbl@users.noreply.github.com> * docs: publish restructure (#3496) * docs: added features and guides overview page * added image * added version 2 * added version 3 * added version 4 * docs: implemented new color scheme * docs: redesigned sidebar (#3193) * docs: redesigned navbar for restructure (#3199) * docs: redesigned footer (#3209) * docs: redesigned cards (#3230) * docs: redesigned admonitions (#3231) * docs: redesign announcement bar (#3236) * docs: redesigned large cards (#3239) * docs: redesigned code blocks (#3253) * docs: redesigned search modal and page (#3264) * docs: redesigned doc footer (#3268) * docs: added new sidebars + refactored css and assets (#3279) * docs: redesigned api reference sidebar * docs: refactored css * docs: added code tabs transition * docs: added new sidebars * removed unused assets * remove unusued assets * Fix deploy errors * fix incorrect link * docs: fixed code responsivity + missing icons (#3283) * docs: changed icons (#3296) * docs: design fixes to the sidebar (#3297) * redesign fixes * docs: small design fixes * docs: several design fixes after restructure (#3299) * docs: bordered icon fixes * docs: desgin fixes * fixes to code blocks and sidebar scroll * design adjustments * docs: restructured homepage (#3305) * docs: restructured homepage * design fixes * fixed core concepts icon * docs: added core concepts page (#3318) * docs: restructured homepage * design fixes * docs: added core concepts page * changed text of different components * docs: added architecture link * added missing prop for user guide * docs: added regions overview page (#3327) * docs: added regions overview * moved region pages to new structure * docs: fixed description of regions architecture page * small changes * small fix * docs: added customers overview page (#3331) * docs: added regions overview * moved region pages to new structure * docs: fixed description of regions architecture page * small changes * small fix * docs: added customers overview page * fix link * resolve link issues * docs: updated regions architecture image * docs: second-iteration fixes (#3347) * docs: redesigned document * design fixes * docs: added products overview page (#3354) * docs: added carts overview page (#3363) * docs: added orders overview (#3364) * docs: added orders overview * added links in overview * docs: added vercel redirects * docs: added soon badge for cards (#3389) * docs: resolved feedback changes + organized troubleshooting pages (#3409) * docs: resolved feedback changes * added extra line * docs: changed icons for restructure (#3421) * docs: added taxes overview page (#3422) * docs: added taxes overview page * docs: fix sidebar label * added link to taxes overview page * fixed link * docs: fixed sidebar scroll (#3429) * docs: added discounts overview (#3432) * docs: added discounts overview * fixed links * docs: added gift cards overview (#3433) * docs: added price lists overview page (#3440) * docs: added price lists overview page * fixed links * docs: added sales channels overview page (#3441) * docs: added sales overview page * fixed links * docs: added users overview (#3443) * docs: fixed sidebar border height (#3444) * docs: fixed sidebar border height * fixed svg markup * docs: added possible solutions to feedback component (#3449) * docs: added several overview pages + restructured files (#3463) * docs: added several overview pages * fixed links * docs: added feature flags + PAK overview pages (#3464) * docs: added feature flags + PAK overview pages * fixed links * fix link * fix link * fixed links colors * docs: added strategies overview page (#3468) * docs: automated upgrade guide (#3470) * docs: automated upgrade guide * fixed vercel redirect * docs: restructured files in docs codebase (#3475) * docs: restructured files * docs: fixed eslint exception * docs: finished restructure loose-ends (#3493) * fixed uses of backend * docs: finished loose ends * eslint fixes * fixed links * merged master * added update instructions for v1.7.12 * docs: fixed discount details (#3499) * docs: fix trailing slash causing 404 (#3508) * docs: fix error during navigation (#3509) * docs: removed the gatsby storefront guide (#3527) * docs: removed the gatsby storefront guide * docs: fixed query value * chore(docs): Removed Docs Announcement Bar (automated) (#3536) Co-authored-by: shahednasser <shahednasser@users.noreply.github.com> * fix(medusa): Variant update should include the id for the listeners to be able to identify the entity (#3539) * fix(medusa): Variant update should include the id for the listeners to be able to identify the entity * fix unit tests * Create brave-seahorses-film.md * docs: fix admin redirects (#3548) * chore(release): v1.7.15 * chore(docs): Generated Docs Announcement Bar (automated) (#3550) Co-authored-by: olivermrbl <olivermrbl@users.noreply.github.com> * chore(docs): Generated Services Reference (automated) (#3551) Automated changes by [create-pull-request](https://github.com/peter-evans/create-pull-request) GitHub action Co-authored-by: Oliver Windall Juhl <59018053+olivermrbl@users.noreply.github.com> * chore: updated READMEs of plugins (#3546) * chore: updated READMEs of plugins * added notice to plugins * docs: added a deploy guide for next.js storefront (#3558) * docs: added a deploy next.js guide * docs: fix image zoom * docs: fixes to next.js deployment guide to vercel (#3562) * chore(workflows): Enable manual workflow in pre-release mode (#3566) * chore(docs): Removed Docs Announcement Bar (automated) (#3598) Co-authored-by: shahednasser <shahednasser@users.noreply.github.com> * fix(medusa): Rounding issues on line item adjustments (#3446) * chores(medusa): Attempt to fix discount rounding issues * add migration * update entities * apply multipler factor properly * fix discount service * WIP * fix rounding issues in discounts * fix some tests * Exclude raw_discount_total from responses * fix adjustments * cleanup response * fix * fix draft order integration * fix order integration * fix order integration * address feedback * fix test * Create .changeset/polite-llamas-sit.md * remove comment --------- Co-authored-by: Oliver Windall Juhl <59018053+olivermrbl@users.noreply.github.com> * chore(workflows): Add release notification (#3629) --------- Co-authored-by: pepijn-vanvlaanderen <pepijn@webbers.com> Co-authored-by: olivermrbl <oliver@mrbltech.com> Co-authored-by: Adrien de Peretti <adrien.deperetti@gmail.com> Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: olivermrbl <olivermrbl@users.noreply.github.com> Co-authored-by: Carlos R. L. Rodrigues <37986729+carlos-r-l-rodrigues@users.noreply.github.com> Co-authored-by: shahednasser <shahednasser@users.noreply.github.com> Co-authored-by: Oliver Windall Juhl <59018053+olivermrbl@users.noreply.github.com>
738 lines
16 KiB
Plaintext
738 lines
16 KiB
Plaintext
---
|
||
description: 'Learn how to implement customer group functionalities for admins using the REST APIs. This includes listing customer groups, creating a customer group, managing customers in the group, and more.'
|
||
addHowToData: true
|
||
---
|
||
|
||
import Tabs from '@theme/Tabs';
|
||
import TabItem from '@theme/TabItem';
|
||
|
||
# How to Manage Customer Groups
|
||
|
||
In this document, you’ll learn how to use the customer groups admin APIs to manage customer groups and their associated customers and price lists.
|
||
|
||
## Overview
|
||
|
||
Using the Admin API you can manage customer groups by creating, retrieving, updating, and deleting them. You can also manage the customers in a customer group.
|
||
|
||
Using the PriceList API you can specify among the conditions the customer groups that the prices will apply to.
|
||
|
||
This guide covers how to use these APIs to perform these tasks.
|
||
|
||
---
|
||
|
||
## Prerequisites
|
||
|
||
### Medusa Components
|
||
|
||
It is assumed that you already have a Medusa backend installed and set up. If not, you can follow our [quickstart guide](../../../development/backend/install.mdx) to get started.
|
||
|
||
### JS Client
|
||
|
||
This guide includes code snippets to send requests to your Medusa backend using Medusa’s JS Client, among other methods.
|
||
|
||
If you follow the JS Client code blocks, it’s assumed you already have [Medusa’s JS Client](../../../js-client/overview.md) installed and have [created an instance of the client](../../../js-client/overview.md#configuration).
|
||
|
||
### Medusa React
|
||
|
||
This guide also includes code snippets to send requests to your Medusa backend using Medusa React, among other methods.
|
||
|
||
If you follow the Medusa React code blocks, it's assumed you already have [Medusa React installed](../../../medusa-react/overview.md) and have [used MedusaProvider higher in your component tree](../../../medusa-react/overview.md#usage).
|
||
|
||
### Authenticated Admin User
|
||
|
||
You must be an authenticated admin user before following along with the steps in the tutorial.
|
||
|
||
You can learn more about [authenticating as an admin user in the API reference](/api/admin/#section/Authentication).
|
||
|
||
---
|
||
|
||
## Create Customer Groups
|
||
|
||
You can create a customer group by sending a request to the Create Customer Group endpoint:
|
||
|
||
<Tabs groupId="request-type" wrapperClassName="code-tabs">
|
||
<TabItem value="client" label="Medusa JS Client" default>
|
||
|
||
```ts
|
||
medusa.admin.customerGroups.create({
|
||
name: "VIP",
|
||
})
|
||
.then(({ customer_group }) => {
|
||
console.log(customer_group.id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="medusa-react" label="Medusa React">
|
||
|
||
```tsx
|
||
import { useAdminCreateCustomerGroup } from "medusa-react"
|
||
|
||
const CreateCustomerGroup = () => {
|
||
const createCustomerGroup = useAdminCreateCustomerGroup()
|
||
// ...
|
||
|
||
const handleCreate = () => {
|
||
createCustomerGroup.mutate({
|
||
name,
|
||
})
|
||
}
|
||
|
||
// ...
|
||
|
||
return (
|
||
<form>
|
||
{/* Render form */}
|
||
</form>
|
||
)
|
||
}
|
||
|
||
export default CreateCustomerGroup
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="fetch" label="Fetch API">
|
||
|
||
```ts
|
||
fetch(`<BACKEND_URL>/admin/customer-groups`, {
|
||
method: "POST",
|
||
credentials: "include",
|
||
headers: {
|
||
"Content-Type": "application/json",
|
||
},
|
||
body: JSON.stringify({
|
||
name: "VIP",
|
||
}),
|
||
})
|
||
.then((response) => response.json())
|
||
.then(({ customer_group }) => {
|
||
console.log(customer_group.id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="curl" label="cURL">
|
||
|
||
```bash
|
||
curl -L -X POST '<BACKEND_URL>/admin/customer-groups' \
|
||
-H 'Authorization: Bearer <API_TOKEN>' \
|
||
-H 'Content-Type: application/json' \
|
||
--data-raw '{
|
||
"name": "VIP"
|
||
}'
|
||
```
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
This request requires the `name` parameter and optionally accepts the `metadata` object parameter to be passed in the body. It returns the created customer group.
|
||
|
||
---
|
||
|
||
## List Customer Groups
|
||
|
||
You can get a list of all customer groups by sending a request to the List Customer Groups endpoint:
|
||
|
||
<Tabs groupId="request-type" wrapperClassName="code-tabs">
|
||
<TabItem value="client" label="Medusa JS Client" default>
|
||
|
||
```ts
|
||
medusa.admin.customerGroups.list()
|
||
.then(({ customer_groups, limit, offset, count }) => {
|
||
console.log(customer_groups.length)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="medusa-react" label="Medusa React">
|
||
|
||
```tsx
|
||
import { CustomerGroup } from "@medusajs/medusa"
|
||
import { useAdminCustomerGroups } from "medusa-react"
|
||
|
||
const CustomerGroups = () => {
|
||
const {
|
||
customer_groups,
|
||
isLoading,
|
||
} = useAdminCustomerGroups()
|
||
|
||
return (
|
||
<div>
|
||
{isLoading && <span>Loading...</span>}
|
||
{customer_groups && !customer_groups.length && (
|
||
<span>No Customer Groups</span>
|
||
)}
|
||
{customer_groups && customer_groups.length > 0 && (
|
||
<ul>
|
||
{customer_groups.map(
|
||
(customerGroup: CustomerGroup) => (
|
||
<li key={customerGroup.id}>
|
||
{customerGroup.name}
|
||
</li>
|
||
)
|
||
)}
|
||
</ul>
|
||
)}
|
||
</div>
|
||
)
|
||
}
|
||
|
||
export default CustomerGroups
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="fetch" label="Fetch API">
|
||
|
||
```ts
|
||
fetch(`<BACKEND_URL>/admin/customer-groups`, {
|
||
credentials: "include",
|
||
})
|
||
.then((response) => response.json())
|
||
.then(({ customer_groups, limit, offset, count }) => {
|
||
console.log(customer_groups.length)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="curl" label="cURL">
|
||
|
||
```bash
|
||
curl -L -X GET '<BACKEND_URL>/admin/customer-groups' \
|
||
-H 'Authorization: Bearer <API_TOKEN>'
|
||
```
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
This request returns an array of customer groups, as well as pagination fields.
|
||
|
||
You can also pass filters and other selection query parameters to the request. Check out the [API reference](/api/admin/#tag/Customer-Group/operation/GetCustomerGroups) for more details on available query parameters.
|
||
|
||
---
|
||
|
||
## Retrieve a Customer Group
|
||
|
||
You can retrieve a single customer group by sending a request to the Get a Customer Group endpoint:
|
||
|
||
<Tabs groupId="request-type" wrapperClassName="code-tabs">
|
||
<TabItem value="client" label="Medusa JS Client" default>
|
||
|
||
```ts
|
||
medusa.admin.customerGroups.retrieve(customerGroupId)
|
||
.then(({ customer_group }) => {
|
||
console.log(customer_group.id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="medusa-react" label="Medusa React">
|
||
|
||
```tsx
|
||
import { useAdminCustomerGroup } from "medusa-react"
|
||
|
||
const CustomerGroup = () => {
|
||
const { customer_group, isLoading } = useAdminCustomerGroup(
|
||
customerGroupId
|
||
)
|
||
|
||
return (
|
||
<div>
|
||
{isLoading && <span>Loading...</span>}
|
||
{customer_group && <span>{customer_group.name}</span>}
|
||
</div>
|
||
)
|
||
}
|
||
|
||
export default CustomerGroup
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="fetch" label="Fetch API">
|
||
|
||
```ts
|
||
fetch(
|
||
`<BACKEND_URL>/admin/customer-groups/${customerGroupId}`,
|
||
{
|
||
credentials: "include",
|
||
}
|
||
)
|
||
.then((response) => response.json())
|
||
.then(({ customer_group }) => {
|
||
console.log(customer_group.id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="curl" label="cURL">
|
||
|
||
```bash
|
||
curl -L -X GET '<BACKEND_URL>/admin/customer-groups/<CUSTOMER_GROUP_ID>' \
|
||
-H 'Authorization: Bearer <API_TOKEN>'
|
||
```
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
This request accepts the ID of the customer group to retrieve as a path parameter. It returns the customer group of that ID.
|
||
|
||
---
|
||
|
||
## Update a Customer Group
|
||
|
||
You can update a customer group’s data by sending a request to the Update Customer Group endpoint:
|
||
|
||
<Tabs groupId="request-type" wrapperClassName="code-tabs">
|
||
<TabItem value="client" label="Medusa JS Client" default>
|
||
|
||
```ts
|
||
medusa.admin.customerGroups.update(customerGroupId, {
|
||
metadata: {
|
||
is_seller: true,
|
||
},
|
||
})
|
||
.then(({ customer_group }) => {
|
||
console.log(customer_group.id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="medusa-react" label="Medusa React">
|
||
|
||
```tsx
|
||
import { useAdminUpdateCustomerGroup } from "medusa-react"
|
||
|
||
const UpdateCustomerGroup = () => {
|
||
const updateCustomerGroup = useAdminUpdateCustomerGroup(
|
||
customerGroupId
|
||
)
|
||
// ..
|
||
|
||
const handleUpdate = () => {
|
||
updateCustomerGroup.mutate({
|
||
name,
|
||
})
|
||
}
|
||
|
||
// ...
|
||
|
||
return (
|
||
<form>
|
||
{/* Render form */}
|
||
</form>
|
||
)
|
||
}
|
||
|
||
export default UpdateCustomerGroup
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="fetch" label="Fetch API">
|
||
|
||
```ts
|
||
fetch(
|
||
`<BACKEND_URL>/admin/customer-groups/${customerGroupId}`,
|
||
{
|
||
method: "POST",
|
||
credentials: "include",
|
||
headers: {
|
||
"Content-Type": "application/json",
|
||
},
|
||
body: JSON.stringify({
|
||
metadata: {
|
||
is_seller: true,
|
||
},
|
||
}),
|
||
}
|
||
)
|
||
.then((response) => response.json())
|
||
.then(({ customer_group }) => {
|
||
console.log(customer_group.id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="curl" label="cURL">
|
||
|
||
```bash
|
||
curl -L -X POST '<BACKEND_URL>/admin/customer-groups/<CUSTOMER_GROUP_ID>' \
|
||
-H 'Authorization: Bearer <API_TOKEN>' \
|
||
-H 'Content-Type: application/json' \
|
||
--data-raw '{
|
||
"metadata": {
|
||
"is_seller": true
|
||
}
|
||
}'
|
||
```
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
This request accepts the ID of the customer group as a path parameter, and optionally accepts the `name` or `metadata` fields as body parameters. It returns the updated customer group.
|
||
|
||
---
|
||
|
||
## Delete Customer Group
|
||
|
||
You can delete a customer group by sending a request to the Delete a Customer Group endpoint:
|
||
|
||
<Tabs groupId="request-type" wrapperClassName="code-tabs">
|
||
<TabItem value="client" label="Medusa JS Client" default>
|
||
|
||
```ts
|
||
medusa.admin.customerGroups.delete(customerGroupId)
|
||
.then(({ id, object, deleted }) => {
|
||
console.log(id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="medusa-react" label="Medusa React">
|
||
|
||
```tsx
|
||
import { useAdminDeleteCustomerGroup } from "medusa-react"
|
||
|
||
const CustomerGroup = () => {
|
||
const deleteCustomerGroup = useAdminDeleteCustomerGroup(
|
||
customerGroupId
|
||
)
|
||
// ...
|
||
|
||
const handleDeleteCustomerGroup = () => {
|
||
deleteCustomerGroup.mutate()
|
||
}
|
||
|
||
// ...
|
||
}
|
||
|
||
export default CustomerGroup
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="fetch" label="Fetch API">
|
||
|
||
```ts
|
||
fetch(
|
||
`<BACKEND_URL>/admin/customer-groups/${customerGroupId}`,
|
||
{
|
||
method: "DELETE",
|
||
credentials: "include",
|
||
}
|
||
)
|
||
.then((response) => response.json())
|
||
.then(({ id, object, deleted }) => {
|
||
console.log(id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="curl" label="cURL">
|
||
|
||
```bash
|
||
curl -L -X DELETE '<BACKEND_URL>/admin/customer-groups/<CUSTOMER_GROUP_ID>' \
|
||
-H 'Authorization: Bearer <API_TOKEN>'
|
||
```
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
This request accepts the ID of the customer group to delete as a path parameter. It returns the ID of the deleted entity.
|
||
|
||
---
|
||
|
||
## Manage Customers
|
||
|
||
### Add Customer to Group
|
||
|
||
You can add a customer to a group by sending a request to the Customer Group’s Add Customer endpoint:
|
||
|
||
<Tabs groupId="request-type" wrapperClassName="code-tabs">
|
||
<TabItem value="client" label="Medusa JS Client" default>
|
||
|
||
```ts
|
||
medusa.admin.customerGroups.addCustomers(customerGroupId, {
|
||
customer_ids: [
|
||
{
|
||
id: customerId,
|
||
},
|
||
],
|
||
})
|
||
.then(({ customer_group }) => {
|
||
console.log(customer_group.id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="medusa-react" label="Medusa React">
|
||
|
||
```tsx
|
||
import {
|
||
useAdminAddCustomersToCustomerGroup,
|
||
} from "medusa-react"
|
||
|
||
const CustomerGroup = () => {
|
||
const addCustomers = useAdminAddCustomersToCustomerGroup(
|
||
customerGroupId
|
||
)
|
||
// ...
|
||
|
||
const handleAddCustomers= (customerId: string) => {
|
||
addCustomers.mutate({
|
||
customer_ids: [
|
||
{
|
||
id: customerId,
|
||
},
|
||
],
|
||
})
|
||
}
|
||
|
||
// ...
|
||
}
|
||
|
||
export default CustomerGroup
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="fetch" label="Fetch API">
|
||
|
||
<!-- eslint-disable max-len -->
|
||
|
||
```ts
|
||
fetch(
|
||
`<BACKEND_URL>/admin/customer-groups/${customerGroupId}/customers/batch`,
|
||
{
|
||
method: "POST",
|
||
credentials: "include",
|
||
headers: {
|
||
"Content-Type": "application/json",
|
||
},
|
||
body: JSON.stringify({
|
||
customer_ids: [
|
||
{
|
||
id: customerId,
|
||
},
|
||
],
|
||
}),
|
||
}
|
||
)
|
||
.then((response) => response.json())
|
||
.then(({ customer_group }) => {
|
||
console.log(customer_group.id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="curl" label="cURL">
|
||
|
||
```bash
|
||
curl -L -X POST '<BACKEND_URL>/admin/customer-groups/<CUSTOMER_GROUP_ID>/customers/batch' \
|
||
-H 'Authorization: Bearer <API_TOKEN>' \
|
||
-H 'Content-Type: application/json' \
|
||
--data-raw '{
|
||
"customer_ids": [
|
||
{
|
||
"id": "<CUSTOMER_ID>"
|
||
}
|
||
]
|
||
}'
|
||
```
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
This request accepts the ID of the customer group as a path parameter. In its body, it accepts a `customer_ids` array of objects. Each object in the array must have the `id` property with its value being the ID of the customer you want to add.
|
||
|
||
### List Customers
|
||
|
||
You can retrieve a list of all customers in a customer group using the List Customers endpoint:
|
||
|
||
<Tabs groupId="request-type" wrapperClassName="code-tabs">
|
||
<TabItem value="client" label="Medusa JS Client" default>
|
||
|
||
```ts
|
||
medusa.admin.customerGroups.listCustomers(customerGroupId)
|
||
.then(({ customers, count, offset, limit }) => {
|
||
console.log(customers.length)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="medusa-react" label="Medusa React">
|
||
|
||
```tsx
|
||
import { Customer } from "@medusajs/medusa"
|
||
import { useAdminCustomerGroupCustomers } from "medusa-react"
|
||
|
||
const CustomerGroup = () => {
|
||
const {
|
||
customers,
|
||
isLoading,
|
||
} = useAdminCustomerGroupCustomers(
|
||
customerGroupId
|
||
)
|
||
|
||
return (
|
||
<div>
|
||
{isLoading && <span>Loading...</span>}
|
||
{customers && !customers.length && (
|
||
<span>No customers</span>
|
||
)}
|
||
{customers && customers.length > 0 && (
|
||
<ul>
|
||
{customers.map((customer: Customer) => (
|
||
<li key={customer.id}>{customer.first_name}</li>
|
||
))}
|
||
</ul>
|
||
)}
|
||
</div>
|
||
)
|
||
}
|
||
|
||
export default CustomerGroup
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="fetch" label="Fetch API">
|
||
|
||
<!-- eslint-disable max-len -->
|
||
|
||
```ts
|
||
fetch(`<BACKEND_URL>/admin/customer-groups/${customerGroupId}/customers`, {
|
||
credentials: "include",
|
||
})
|
||
.then((response) => response.json())
|
||
.then(({ customers, count, offset, limit }) => {
|
||
console.log(customers.length)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="curl" label="cURL">
|
||
|
||
```bash
|
||
curl -L -X GET '<BACKEND_URL>/admin/customer-groups/<CUSTOMER_GROUP_ID>/customers' \
|
||
-H 'Authorization: Bearer <API_TOKEN>'
|
||
```
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
This request accepts the ID of the customer group as a path parameter. It returns an array of customers along with pagination fields.
|
||
|
||
### Remove Customers from a Group
|
||
|
||
:::info
|
||
|
||
Removing customers from a group does not remove them entirely. They’ll still be available in your store.
|
||
|
||
:::
|
||
|
||
You can remove customers from a customer group by sending a request to the Remove Customers endpoint:
|
||
|
||
<Tabs groupId="request-type" wrapperClassName="code-tabs">
|
||
<TabItem value="client" label="Medusa JS Client" default>
|
||
|
||
```ts
|
||
medusa.admin.customerGroups.removeCustomers(
|
||
customer_group_id,
|
||
{
|
||
customer_ids: [
|
||
{
|
||
id: customer_id,
|
||
},
|
||
],
|
||
}
|
||
)
|
||
.then(({ customer_group }) => {
|
||
console.log(customer_group.id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="medusa-react" label="Medusa React">
|
||
|
||
```tsx
|
||
import { Customer } from "@medusajs/medusa"
|
||
import {
|
||
useAdminRemoveCustomersFromCustomerGroup,
|
||
} from "medusa-react"
|
||
|
||
const CustomerGroup = () => {
|
||
const removeCustomers =
|
||
useAdminRemoveCustomersFromCustomerGroup(
|
||
customerGroupId
|
||
)
|
||
// ...
|
||
|
||
const handleRemoveCustomer = (customer_id: string) => {
|
||
removeCustomers.mutate({
|
||
customer_ids: [
|
||
{
|
||
id: customer_id,
|
||
},
|
||
],
|
||
})
|
||
}
|
||
|
||
// ...
|
||
}
|
||
|
||
export default CustomerGroup
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="fetch" label="Fetch API">
|
||
|
||
<!-- eslint-disable max-len -->
|
||
|
||
```ts
|
||
fetch(
|
||
`<BACKEND_URL>/admin/customer-groups/${customerGroupId}/customers/batch`,
|
||
{
|
||
method: "DELETE",
|
||
credentials: "include",
|
||
headers: {
|
||
"Content-Type": "application/json",
|
||
},
|
||
body: JSON.stringify({
|
||
customer_ids: [
|
||
{
|
||
id: customerId,
|
||
},
|
||
],
|
||
}),
|
||
}
|
||
)
|
||
.then((response) => response.json())
|
||
.then(({ customer_group }) => {
|
||
console.log(customer_group.id)
|
||
})
|
||
```
|
||
|
||
</TabItem>
|
||
<TabItem value="curl" label="cURL">
|
||
|
||
```bash
|
||
curl -L -X DELETE '<BACKEND_URL>/admin/customer-groups/<CUSTOMER_GROUP_ID>/customers/batch' \
|
||
-H 'Authorization: Bearer <API_TOKEN>' \
|
||
-H 'Content-Type: application/json' \
|
||
--data-raw '{
|
||
"customer_ids": [
|
||
{
|
||
"id": "<CUSTOMER_ID>"
|
||
}
|
||
]
|
||
}'
|
||
```
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
This request accepts as a path parameter the ID of the customer group to remove customers from. In its body, it accepts a `customer_ids` array of objects. Each object in the array must have the `id` property with the value being the ID of the customer to remove from the group.
|
||
|
||
This request returns the customer group.
|
||
|
||
---
|
||
|
||
## Use Customer Groups as Conditions in a Price List
|
||
|
||
When you create or update a price list, you can specify one or more customer groups as conditions for the price list. You can learn how to do that in the [PriceList API documentation](../../price-lists/admin/manage-price-lists.mdx). |