Terra vs Spike Health: Which Aggregator for Your App?

Terra vs Spike Health, for developers#

Both Terra and Spike are health-data aggregators: one integration, a normalized feed from many sources, instead of a separate OAuth flow and schema per wearable. The difference for a build is what else each one reaches and how you learn the price. Everything here is from the vendors' own pages as we read them on October 17, 2026. An earlier version of this page said neither vendor published pricing, that Spike's own pages disagreed on its device count, and that Spike sold a generative-AI interpretation SDK and a low-code data-pipeline product. Both now publish prices, Spike's current pages agree on 500+ devices (the 200+ figure on its homepage counts customers), and we did not find the SDK or the pipeline product on the pages we read, so those claims are gone.

At a glance#

Where Terra wins#

• A price you can calculate. Terra's pricing page publishes the subscription, the credit allowance and the rates: "An active authentication is one connected data source for one end user, and costs 200 credits per month", the first 400 events per source are free, and extra credits start at $0.005. Spike publishes a starting price and calls its pricing "Usage-driven, transparent, and flexible", but does not itemize how the bill grows.
• Full payloads, wherever you want them. Terra sends normalized data to webhooks or straight into "SQL databases (Postgres and MySQL), Supabase, cloud storage (S3, GCS and Azure Blob), queueing services (SQS and Kafka), MongoDB and Firestore". Spike's webhook event lists the metrics and time range that changed, and you fetch the records with the API.
• Lab tests ordered for your users. Terra's homepage offers blood tests "through home kits, mobile phlebotomy, or lab walk-ins", and its lab page says "Nationwide US, plus the UK". Spike's lab product parses reports users already have.

Where Spike wins#

• Reach past the wrist. Spike's homepage pitches "normalized, ingestion-ready data from wearables, EMRs, lab tests, IoT devices, and more", including medical IoT such as glucose monitors, ECGs and blood pressure cuffs, and its integrations page lists CGMs like Dexcom and Freestyle Libre.
• Lab reports and food photos. The Lab Reports API takes "PDFs, JPEGs, or PNG files up to 10MB" through OCR and assigns LOINC codes "making lab test data from any language standardized". Its Nutrition AI turns "any food image into complete nutritional data".
• A person on your build. "Every organization gets a dedicated implementation engineer from the sandbox level to help with setup and optimization", which is unusual in a category where onboarding is normally the docs.

The trade-off. A banner on Spike's integrations and blog pages reads "Raintree Systems Acquires Spike Technologies". We found no further detail on Spike's own pages, so ask about roadmap and contract continuity before you sign.

Webhooks compared#

Both sign every event with HMAC-SHA256. Terra's header is terra-signature, computed over the timestamp and the raw body; Spike's is X-Body-Signature, computed over the raw request body with a shared key from its admin console. Terra retries a failed delivery "up to 10 times with exponential backoff"; Spike will "retry the request up to 10 times with exponential backoff" too, then discard the event. Spike's payload is a notification (user, metrics, provider and time range), so plan an API call per event.

What we could not verify#

• How Spike's price grows past the Sandbox starting price.
• Whether Spike needs your own developer credentials for any provider; its provider docs describe a user consent redirect and say nothing either way.
• The terms and timing of the Raintree acquisition.

Which should you pick?#

• Consumer fitness or wellness app reacting to new sleep, workout or recovery data: lean Terra for the calculable bill and the push-to-destination delivery.
• Clinical or medical-adjacent build with lab reports, medical IoT or EMR data, or food logging from photos: lean Spike, after confirming each capability and the post-acquisition terms.
• Lab tests ordered for users in the US or UK: Terra.

If you are also weighing Terra against a labs-first option, see Terra vs Vital (Junction), and for the whole field, health-data aggregator APIs.

Honest close#

Terra and Spike are both single-integration aggregators, so neither saves you from the core trade: you pay to remove per-provider integration work. The split that decides it is reach and visibility: Terra publishes a price you can model and pushes full payloads, Spike reaches further into clinical data and puts an engineer on your build, at a price you learn on a call. Re-check both live pricing pages before you build; the Terra API integration guide covers the wearable side.