Skip to content

fix(transport): send norbix-project-id and norbix-account-id instead of X-CM-* - #58

Merged
Domantas merged 1 commit into
mainfrom
fix/project-header-names
Oct 19, 2026
Merged

Domantas merged 1 commit into
mainfrom
fix/project-header-names

Conversation

@Domantas

Copy link
Copy Markdown
Contributor

The SDK sent the project and account only as X-CM-ProjectId and
X-CM-AccountId. The gateway reads neither name — only norbix-project-id
and norbix-account-id (AuthStatics) — so with an account bearer token
every Api project call failed with CM-ERRORS-PROPERTY-001 "Property
ProjectId is required". Same fix as the Go SDK (56f34b6): the legacy
names are no longer sent. Sync and async transports both change; a new
test checks the header names for a project-scoped Api call and an
account Hub call, and that the X-CM-* names are absent.

Co-Authored-By: Claude Opus 5.5 noreply@anthropic.com

…of X-CM-*

The SDK sent the project and account only as X-CM-ProjectId and
X-CM-AccountId. The gateway reads neither name — only norbix-project-id
and norbix-account-id (AuthStatics) — so with an account bearer token
every Api project call failed with CM-ERRORS-PROPERTY-001 "Property
ProjectId is required". Same fix as the Go SDK (56f34b6): the legacy
names are no longer sent. Sync and async transports both change; a new
test checks the header names for a project-scoped Api call and an
account Hub call, and that the X-CM-* names are absent.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Domantas
Domantas merged commit 55be8d0 into main Oct 19, 2026
9 checks passed
@Domantas
Domantas deleted the fix/project-header-names branch October 19, 2026 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant