October 12, 2026: New error docs section explains 403 on v2 endpoints caused by customerId confusion
View as MarkdownOctober 12, 2026API
Domains
New
The error reference now explains a specific cause of 403 Forbidden on Domains v2 endpoints: passing the wrong identifier type in the customerId path parameter.
What changed
A new 403 on v2 endpoints section on the Handle errors page covers the mix-up directly: customerId is a UUID, not your shopperId (a numeric account identifier). Supplying the shopperId where customerId is expected returns a 403 even though the credential is otherwise valid. The section links to steps for finding your actual customerId.
Who is affected
Any developer calling a Domains v2 endpoint with a customerId path parameter. This is a documentation clarification only — no API behavior changed.
Links
- Handle errors — full status code and error envelope reference
- Domains v2 reference — endpoints that take
customerId
Last updated on
How is this guide?