FAQ

Does NetSuite use OAuth login in Coupler.io?

No. NetSuite uses token-based authentication (TBA). Instead of signing in through a redirect, you generate a Consumer Key, Consumer Secret, Token Key, and Token Secret in NetSuite, then enter them along with your Realm (Account ID) directly in Coupler.io.

What's the difference between Objects and SuiteQL?

Objects pulls a standard or custom NetSuite record type as a single table — one row per record, with fields matching that record's schema. SuiteQL runs a SQL-like query you write yourself, letting you join across records, add calculated fields, or apply filters that Object parameters don't expose.

Use Objects for straightforward record exports. Use SuiteQL when you need data shaped across multiple records or fields not available through a single Object.

Which NetSuite records can I export?

Any standard or custom record type your NetSuite account and Access Token role have access to — the Object list in Coupler.io loads live from your account's metadata catalog. Common examples include Invoice, Sales Order, Purchase Order, Vendor Bill, Journal Entry, Customer-related entities, and inventory items. See Data Overview for a fuller breakdown by category.

Why doesn't Start date filter some of my objects?

Start date (and Window in days) only work for record types that expose a last-modified field — lastModifiedDate for standard records, lastmodified for most custom records. Record types without one of these fields don't support incremental filtering and are synced in full every run.

Is there a row limit on SuiteQL queries?

Yes. NetSuite's REST API caps SuiteQL results at 100,000 rows per query — a query that would return more fails instead of paginating past the limit. Narrow your WHERE clause or aggregate in the query itself to stay under it.

How do I connect to a sandbox instead of production?

Append your sandbox suffix to the Realm value, for example 1234567_SB1 instead of 1234567. Everything else (Consumer Key, Consumer Secret, Token Key, Token Secret) is generated the same way, but you'll need a separate Integration record and Access Token created in the sandbox account.

Why am I getting a permission error on an object I know exists?

The Access Token is tied to a specific NetSuite role, and that role may not have view permission for the record type you're requesting — even if your own user account can see it in the NetSuite UI. Grant the role access to that record type, or create a token under a role that already has it.

What happens if I lose my Consumer Secret or Token Secret?

NetSuite only displays these values once, when they're generated — there's no way to retrieve them later. You'll need to create a new Access Token in NetSuite and reconnect the source in Coupler.io with the new credentials.