Hi Folks, A few days ago I've raised here a questi...
# help-connector-development
a
Hi Folks, A few days ago I've raised here a question in the connection-issues channel regarding Netsuite connection taking too long to extract invoices data. 1000 rows every 30 minutes. I'm still trying to understand if it's an API thing... I mean, In my case the Stream/Table has 350 columns... 98 json columns in this group... I started reading the Netsuite source connector code... I could read without worries the overriden methods from SourceNetsuite class (auth, base_url, get_session...) I tested the check_connection method using invoice stream as the example... using limit 1000. Then I saw the API is just returning the invoice id and the url to invoice details... So my question is, Does the netsuite connector sends one request for every invoice i.e (https://5046696-sb2.suitetalk.api.netsuite.com/services/rest/record/v1/invoice/xxxx) ... or there's an endpoint to receive invoice details for n invoice... with pagination and all the required stuff... I'm asking it because, if the connector need to send one request for every invoice... I think maybe that's the reason for the connection taking too much time to run... I tried to find more details with the API documentation... but it's a little bit confusing to me... Or... the way I see, we have to send one request for every invoice. Could you help to confirm this point? please?
k
A message from kapa.ai
Hmm, I don't know enough to give you a confident answer yet. However, you can refer to the [Airbyte documentation](https://docs.airbyte.com) for more information on connectors and their performance considerations.