API

Logistics APIs

POST logistics/carriers/{carrierId}/services

Creates a new service in provided carrier

HTTP method POST
URI https://api.rambase.net/logistics/carriers/{carrierId}/services
Supported formats Xml, Html, Json (ex. $format=json)
- URI parameter {carrierId} Carrier identifier
Integer, minimum 1000
Successful HTTP status code 201
API resource identifier 3585, version 3

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
<CarrierService>
2
     <CarriersId
CarriersId

Required/mandatory field

Carrier service identifier

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

Description of the carriers shipping service

This field is optional.

>
{String}</Description>
4
</CarrierService>
1
{
2
     "carrierService": {
3
          "carriersId
CarriersId

Required/mandatory field

Carrier service identifier

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

Description of the carriers shipping service

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
<CarrierService>
2
     <CarrierServiceId
CarrierServiceId

Identifier from archive for shipping services

>
{Integer}</CarrierServiceId>
3
     <CarriersId
CarriersId

Carrier service identifier

>
{String}</CarriersId>
4
     <Description
Description

Description of the carriers shipping service

>
{String}</Description>
5
</CarrierService>
1
{
2
     "carrierService": {
3
          "carrierServiceId
CarrierServiceId

Identifier from archive for shipping services

":
"{Integer}",
4
          "carriersId
CarriersId

Carrier service identifier

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

Description of the carriers shipping service

":
"{String}"
6
     }
7
}

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 101524 HTTP 400 ProductId is mandatory for carrier
Error 101540 HTTP 404 Specified product identifier was not found