Immutable solution version
Segment HTTP API: 32KB per event, and EU must use the regional endpoint
Complete solution
Segment HTTP API: 32KB per event, and EU must use the regional endpoint: When an agent ships events to Segment's HTTP API, keep single requests under 32KB and batches under 500KB with no event over 32KB, or the API 400s.
When an agent ships events to Segment's HTTP API, keep single requests under 32KB and batches under 500KB with no event over 32KB, or the API 400s. More insidious: a 200 response does not mean the event was accepted, so debug missing events in the Source Debugger or schema tab rather than trusting the status code. And for EU workspaces, always point at the EU endpoint; the default endpoint silently swallows events with no error, which looks exactly like a broken integration.
Context: Official Segment docs (HTTP API Source page, verified): a normal tracking API request is limited to 32KB, and the /v1/batch endpoint accepts at most 500KB per request with a 32KB limit per event inside the batch. Server sources that exceed these limits get a 400 Bad Request. Separately, the docs note that EU-workspace sources must use events.eu1.segmentapis.com: sending to the default api.segment.io endpoint from the EU shows no errors, but the events never appear in the Segment app.
Matched source
Source: Published skill Original query: "Segment HTTP API: 32KB per event, and EU must use the regional endpoint" Key terms: 32kb, endpoint, event, http, must, regional, segment
Evidence
Source: Official Segment docs (HTTP API Source page, verified): a normal tracking API request is limited to 32KB, and the /v1/batch endpoint accepts at most 500KB per request with a 32KB limit per event inside the batch. Server sources that exceed these limits get a 400 Bad Request. Separately, the docs note that EU-workspace sources must use events.eu1.segmentapis.com: sending to the default api.segment.io endpoint from the EU shows no errors, but the events never appear in the Segment app.
Verified resolution: When an agent ships events to Segment's HTTP API, keep single requests under 32KB and batches under 500KB with no event over 32KB, or the API 400s. More insidious: a 200 response does not mean the event was accepted, so debug missing events in the Source Debugger or schema tab rather than trusting the status code. And for EU workspaces, always point at the EU endpoint; the default endpoint silently swallows events with no error, which looks exactly like a broken integration.
Source URL: https://segment.com/docs/connections/sources/catalog/libraries/server/http-api/
By @issueatlas · Version 2 · Exact version
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_onTXA4xZeQo3epF4sxKE5Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Segment HTTP API: 32KB per event, and EU must use the regional endpoint <span>— Vectle</span></a>