Get Carrier Service Detail

Allows users to retrieve detailed information about a specific carrier service by its unique ID.

🔒

Requires read_product access scope. More access scope

The Get CarrierService Detail API allows users to retrieve detailed information about a specific carrier service by its unique ID. This helps users view the configuration and status of a carrier service.

This API is especially useful for:

  1. Verifying carrier service configuration.
  2. Fetching the current status and properties of a carrier service.
  3. Debugging carrier service-related issues.

Request Parameters

Public Request Parameters

📘

Path Parameters

NameTypeRequiredExampleDescription
carrier_service_idstringYes"123"The unique identifier of the carrier service.

Response Explanation

Public Response Parameters

📘

Successful Response

ParameterTypeExampleDescription
codestring200Error code (200 indicates success)
messagestringSuccessError message
dataobject{...}Contains the carrier services data
carrier_serviceobjectcarrier service object

Carrier Service Object Structure

ParameterTypeExampleDescription
idstringcs_123456Unique identifier for the carrier service
namestringFedEx ExpressName of the carrier service
activebooleantrueWhether the carrier service is active
callback_urlstringhttps://carrier.example.com/callbackURL for carrier service callbacks
scopesstringread_writePermissions scope for the carrier service
carrier_service_codestringfedex_expressCode identifier for the carrier service
logostringhttps://example.com/logo.pngURL to the carrier service logo
short_descstringFast domestic shippingBrief description of the carrier service
created_atstring2023-01-15T10:00:00ZTimestamp when the carrier service was created
updated_atstring2023-06-20T15:30:00ZTimestamp when the carrier service was last updated

Error Response

FieldTypeExampleDescription
codestringInvalidParameterError http message
messagestring``Error message

API Structure Overview

Language
Credentials
Header
URL
Click Try It! to start a request and see the response here!