Skip to main content
GET
Get service point by code

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Headers

Accept-Language
string
default:en

Preferred language(s) for translatable content using BCP 47 language tags. Supports quality values (q-factors) for priority ordering. The API negotiates the best available language based on this header, the team's configured language, and available translations. If omitted, the team's default language is used.

Example:

"da-DK, da;q=0.9, en;q=0.8"

Request-ID
string

Optional client-supplied request identifier. When provided and matching the validation pattern, the value is echoed back in the Request-ID response header. Otherwise the server generates one. Use this to correlate requests between client and server when reporting issues.

Required string length: 1 - 64
Pattern: ^[A-Za-z0-9._-]{1,64}$

Path Parameters

teamUuid
string<uuid>
required

Team uuid. All resources are scoped to this team.

carrier
string
required

Carrier code (e.g., postnord, gls, bring)

Examples:

"postnord"

"bring"

"dao"

"gls"

country
string
required

ISO 3166-1 alpha-2 country code

Required string length: 2
Examples:

"DK"

"SE"

"FI"

"NO"

"DE"

"ES"

"US"

"CN"

"CA"

code
string
required

Carrier's service point code/number/id

Example:

"12345"

Response

Service point retrieved successfully

data
object
required

A service-point resource. Ordinary list and detail responses omit distance because there is no reference search position. The closest search uses ClosestServicePoint to add that context.