Terra
Integrations
Research

Integration

API
Unified API
SDK
SDK
Authentication
Authentication
Streaming
Streaming
Blood
Blood Report API
Planned Workouts
Planned Workouts
AI Interface
AI Interface

User engagement

Graph API
Graph API
Scores
Health Scores
Rewards
Health Rewards

Use cases

Enterprise
Enterprise
Insurance
Insurance

Developers

Wearable Data
Wearable Data
Community
Community
Documentation
Documentation

Learn

Blog
Blog
Podcast
Podcast
Events
Events
Reports
Reports

Company

Customers
Customers
Careers
Careers
Partners
Partners
Support
Support
Pricing
Become an integrationGet started
IntegrationsResearch
Unified APIUnified APISDKSDKAuthenticationAuthenticationStreamingStreamingGraph APIGraph APIScoresScoresRewardsRewardsBlood Report APIBloodAI InterfaceAI Interface
EnterpriseEnterpriseInsuranceInsuranceWearable DataWearable DataCommunityCommunityDocumentationDocumentationBlogBlogPodcastPodcastEventsEventsReportsReportsCustomersCustomersCareersCareersPartnersPartnersSupportSupport
Pricing
Get startedBecome an integration


Cookie Preferences

Essential CookiesAlways On
Advertisement Cookies
Analytics Cookies

Crunch Time: Embrace the Cookie Monster Within!

We use cookies to enhance your browsing experience and analyse our traffic. By clicking “Accept All”, you consent to our use of cookies according to our Cookie Policy. You can change your mind any time by visiting out cookie policy.

Cookies Policy
zap

Latest

zap

Popular

API

Unified API

SDK

Phone SDK

Authentication

Widget

Streaming

Streaming

Graph API

Graph API

How can I handle large Zwift payloads

All

MilitaryPuma26 months ago

Recently I have observed that Zwift payloads are noticeably larger than the payloads from most other providers. Sometimes the event gets rejected and on the dashboard debug log I see failure status events. How big do the zwift payloads get and do you guys chunk the data ever?

terra

Alexadmin26 months ago

The errors you see on the debug log are responses returned by your server. You should be seeing error 413s being recorded as most web servers are not configured to handle request bodies with sizes >1MB. The solution here would be to increase the size limit on POST requests on your web server or proxy, for example:

If you are using Nginx, navigate to the configuration directory and create/edit the configuration, setting client_max_body_size to 50MB (just in case).

This is typical practice, especially for sending large files over http. And whilst Terra does chunk payloads, they are chunked by days if the request spans over weeks.