Trove API beta program FAQ

What kind of help do I get from the Wrenfield team?

A named engineer from our platform group joins your workspace for the length of the beta, plus a shared channel for questions and a fortnightly office hour.

How long does wiring up the Trove API take?

Teams with an engineer on hand usually ship a first working sync in two to three weeks. Read-only pulls tend to land inside a week.

Who is eligible to use the Trove API?

Any workspace on a team or enterprise agreement can request a key. Trial workspaces get sandbox access with a lower rate limit.

Can I push data from several tools into Trove?

Yes. Each source gets its own key and mapping, so a survey platform, a call recorder and an internal database can all write into the same repository.

Can I move data out of Trove into other tools?

Outbound events fire whenever a study, transcript or tag changes, so a warehouse or reporting layer can stay in step without polling.

Can I build an integration without writing code (or pulling in my data team)?

For the common sources, yes — pick a template, paste a key and map the fields. Anything bespoke still wants a developer for a few days.

Who do I reach out to with questions?

Write to the beta desk at api-beta@wrenfield.example and someone from the platform group will pick it up the same working day.