API

Sales APIs

POST sales/customer-groups

Create a new customer group

HTTP method POST
URI https://api.rambase.net/sales/customer-groups
Supported formats Xml, Html, Json (ex. $format=json)
Successful HTTP status code 201
API resource identifier 2462, version 1

The following body must be added to the request. Mouse over fieldnames for description and other useful information about the fields. Note that fields in bold are required/mandatory.

Format:
1
<CustomerGroup>
2
     <Name
Name

Required/mandatory field

Customer group name

>
{String}</Name>
3
     <Description
Description

Description of the customer group

This field is optional.

>
{String}</Description>
4
</CustomerGroup>
1
{
2
     "customerGroup": {
3
          "name
Name

Required/mandatory field

Customer group name

":
"{String}",
4
          "description
Description

Description of the customer group

This field is optional.

":
"{String}"
5
     }
6
}

The query string is placed after the resource URL, seperated with a questionmark (?). The query string is composed of a series of query parameters with values. See the page about query parameters on how to use these parameters.

$access_token String, optional After successful login you get an access token which needs to be provided in all API requests. Even though it is possible to pass this token as query parameter, we recommended passing it using the HTTP request header as described in Authorization. Note that all access tokens have an expiration time.
$db String, optional Set the database/company for the request
$useMinimumVersion Integer, optional Used to run a new version of an API resource when your API client is running a deprecated API resource. See the Breaking changes page for more information.
$lang String, optional Specifies the language used in the response, following the 3-letter ISO-639-1 [lll]

Read more about filters and sorting on how to use filter parameters and named filters.

Read more about filters and sorting on how to use sortable parameters

Requesting this resource will yield the following response. Mouse over fieldnames (or fieldgroups) for descriptions and other useful information about the fields.

Please note that some fields may be removed from the response, based on user roles/duties/permissions.

Format:
1
<CustomerGroup>
2
     <CustomerGroupId
CustomerGroupId

Customer group identificator

>
{Integer}</CustomerGroupId>
3
     <Status
Status

Customer group status

>
{Integer}</Status>
4
     <CreatedAt
CreatedAt

Date and time of creation

>
{Datetime}</CreatedAt>
5
     <Name
Name

Customer group name

>
{String}</Name>
6
     <Description
Description

Description of the customer group

>
{String}</Description>
7
</CustomerGroup>
1
{
2
     "customerGroup": {
3
          "customerGroupId
CustomerGroupId

Customer group identificator

":
"{Integer}",
4
          "status
Status

Customer group status

":
"{Integer}",
5
          "createdAt
CreatedAt

Date and time of creation

":
"{Datetime}",
6
          "name
Name

Customer group name

":
"{String}",
7
          "description
Description

Description of the customer group

":
"{String}"
8
     }
9
}

List of available operations/actions for this resource.
See the operations documentation for more information about API operations.

Possible error codes the response might return:

Error 102668 HTTP 400 Customer group name is required
Error 102669 HTTP 400 A customer group with that name already exists