Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Unnikrishnan Nair Fivetranner

    Hi Anri,
    Thanks for the input. 
    Analysing these endpoints we see that there this works best with an input provided to get the companies information that you would want to enrich. With potentially an unlimited list, this would be difficult as the list can be dynamic as per your changing requirements?
    Do you have any other usecase in mind?
    Also, the rate limits mention 600-1000 calls which we consider as low for efficient data retrieval. 

  • Anri Hakobyan User

    Hi Unnikrishnan,

    Understood, our use case is limited and controlled. We only enrich a defined list of companies from our warehouse (not an open-ended dataset).

    We’d simply like the connector to include the following existing Apollo fields in the synced output:

    • estimated_num_employees

    • organization_revenue

    • organization_revenue_printed

    These are part of the same enrichment response you’re already pulling, so no major logic change should be required - just adding the fields to the output schema would cover our need.

    Thanks for considering this enhancement!

     Anri