Skip to content

fix(sdk): default apiUrl to ingest.webdecoy.com (0.4.1)#3

Merged
cport1 merged 1 commit into
mainfrom
fix/sdk-apiurl-default
Jul 1, 2026
Merged

fix(sdk): default apiUrl to ingest.webdecoy.com (0.4.1)#3
cport1 merged 1 commit into
mainfrom
fix/sdk-apiurl-default

Conversation

@cport1

@cport1 cport1 commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

The SDK talks to the ingest service, but the default apiUrl was https://api.webdecoy.com — that host is the Railway backend and 404s on every /api/v1/sdk/* route (detect, violations, IP enrichment). So any integration relying on the default couldn't reach the ingest at all.

  • sdk.ts: default apiUrlhttps://ingest.webdecoy.com
  • types.ts @default JSDoc + README/express-README examples updated
  • all packages bumped to 0.4.1

Found while smoke-testing the tripwire→detection bridge: a call to api.webdecoy.com/api/v1/sdk/violations/batch returned 404; the same path on ingest.webdecoy.com returns 401 (route live).

⚠️ Note: this is necessary but not sufficient — ingest.webdecoy.com's TLS cert is currently expired (separate fix), so the SDK still won't connect until that's renewed.

…, which 404s)

The SDK's endpoints (detect, violations, IP enrichment) are served by the ingest service at ingest.webdecoy.com. api.webdecoy.com is the Railway backend and returns 404 for all /api/v1/sdk/* routes, so any integration relying on the default apiUrl could not reach the ingest — violations, detect, and enrichment all failed. Point the default at ingest.webdecoy.com and fix the README/JSDoc examples.

Bumps all packages to 0.4.1.
@cport1 cport1 merged commit dfa889c into main Jul 1, 2026
2 checks passed
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