What Do I Need Before Setting Up an API or FTP Integration?

Last updated: November 17, 2026

An API or FTP integration only works if someone on your team can export activity data automatically and send it to Ambition on a schedule. Before turning one on, agree on what you'll track and confirm your systems can deliver it in a format Ambition accepts.

Required permissions:

  • The Integrations: Edit permission is required to set up an API or FTP integration.

Questions for the Person Who Owns the Metrics

  • Which activities do you want to track in Ambition?

  • How often should the data update, and what's the slowest update you could accept?

Questions for the Person Building the Integration

  • Which systems hold the data, and can they export it automatically?

  • Can you send that export to Ambition on a recurring schedule? If not, a File Upload or Manual Entry integration may fit better.

  • Will you be alerted if a transfer fails?

  • Can you meet the data requirements below?

Data Requirements

  • Files must be CSV or JSON. Nested JSON can be flattened with the JSON Transformer on the Data Format page.

  • Data must be either Daily Totals (one total per user per day) or Records (one row per activity).

  • Every row needs a user identifier, such as an email address, and a date or date and time.

  • Data must belong to individual users, not teams or groups.

  • Each file or request can be up to 15 MB.

  • Each integration should cover one system or data set. You can have up to 10 Performance Data API integrations and 10 FTP integrations, depending on your plan.


Related Articles