Terra Docs
⌘Ctrlk
Dashboard
  • Docs
  • API Reference
  • Changelog
  • AI
  • FAQ
Terra Docs
  • Help Center
    • API, SDK & data formats
    • My data isn't arriving
    • Connecting a provider
    • Billing & account
    • Webhooks & destinations
      • Failures, errors and retries
      • Storage destinations: S3, SQS, Supabase, SQL, GCS
      • Destinations and routing setup
      • Delivery timing, volume and ordering
      • Large payloads and chunking
      • Payload content and provider quirks
        • Why don't Garmin simulator payloads appear in history?
        • Does the Include Samples toggle affect the API too?
        • Why do I get multiple Garmin sleep sessions for one night, or a sleep payload that looks incomplete?
        • Why are there two provider enums for Google?
        • Is planned_workout a valid webhook type?
      • Security, signatures and network access
    • Something else
Powered by GitBook
For the complete documentation index, see llms.txt. This page is also available as Markdown.
  1. FAQ
  2. Help topics
  3. Webhooks & destinations

Payload content and provider quirks

Payload content and provider quirks

Common questions about payload content and provider quirks.

Articles

Why don't Garmin simulator payloads appear in history?Does the Include Samples toggle affect the API too?Why do I get multiple Garmin sleep sessions for one night, or a sleep payload that looks incomplete?Why are there two provider enums for Google?Is planned_workout a valid webhook type?
PreviousWhy does a payload data URL fail with 400 expired-token?NextWhy don't Garmin simulator payloads appear in history?

Last updated 2 months ago

Was this helpful?

Was this helpful?