AtlasCore Market

Oracle NetSuite Commerce Legal addendum · Legal version v1 · Last updated: July 13, 2026

Oracle NetSuite Commerce API Compliance

Last updated: August 25, 2026

This addendum summarizes AtlasCore alignment with Oracle NetSuite developer and account agreement requirements for connected accounts via the SuiteTalk REST Record API using OAuth 1.0a Token-Based Authentication (TBA) configured by the merchant.

Independent application status

AtlasCore is an independent software application. NetSuite, Oracle NetSuite Commerce, and related marks are trademarks of Oracle Corporation or its affiliates. AtlasCore is not sponsored, endorsed, or affiliated with Oracle or NetSuite.

Primary integration mechanism

AtlasCore integrates with NetSuite exclusively through:

- SuiteTalk REST Record API (`/services/rest/record/v1/…`)

  • OAuth 1.0a TBA (Consumer Key/Secret + Token ID/Secret with HMAC-SHA256 request signing)

AtlasCore does not use OAuth 2.0, RESTlets, SuiteTalk SOAP, or UI scraping for NetSuite connectivity.

Permitted SaaS sync operations

AtlasCore accesses a NetSuite account only after explicit merchant authorization with scoped TBA credentials. Live server-side reads are focused on order synchronization and connection health validation. Seller writes (inventory update) run only when `NETSUITE_WRITE_APPROVED` is also true. Inbound webhooks never mutate stock.

AtlasCore does not scrape the NetSuite UI or use undocumented data extraction methods. Catalog listing sync is not a primary NetSuite spoke surface; order ingest and optional inventory writes are the supported integration scope.

Data handling controls

  • Order data: Only operational fields (internal/tran id, status, totals, dates, line SKU/qty) are stored. Customer, shipping, billing, and contact fields are not persisted. Seller dashboard GETs return cache-only sanitized rows. Live server-side reads run strictly for seller-initiated sync POSTs (`POST /sync/`), `GET /status/` health probes, and credential validation

Rate limits & API discipline

- AtlasCore respects NetSuite governance limits (concurrency, request quotas) and implements backoff on HTTP 429/503 responses

  • Seller-initiated sync (`POST /sync/`) uses a limit-capped SuiteTalk `salesOrder` list (maximum 100 rows per request) plus targeted on-demand detail GETs only when a list row is sparse — not an automated bulk batching or scheduled sync worker
  • AtlasCore does not run a background NetSuite pagination worker; merchants pull additional pages by repeating seller-initiated sync as needed

Credential security & prohibited practices

- Credential encryption: TBA Consumer Key/Secret and Token ID/Secret are encrypted at rest (AES-256-GCM, `enc:v1:` format). Optional per-workspace webhook signing secrets are encrypted the same way.

  • Transport: Production traffic uses TLS 1.2+ (HTTPS)
  • Tenant isolation: Each AtlasCore user may link their own NetSuite realm; one active `account_id` is allowed platform-wide. Cross-user realm access is denied at the API layer
  • Webhooks: Incoming NetSuite webhooks require HMAC-SHA256 verification (`X-NetSuite-Signature`) over the raw request body before timestamp freshness, event persistence or dispatch. Failed signatures return HTTP 401. Ingress ignores `X-Tenant` and binds to the verified realm. Canonical sales-order terminals are `BILLED`, `CLOSED`, `CANCELED`, and `CANCELLED`. A dedicated webhook secret is required — TBA token secrets are never used as HMAC material. A bounded parse may run solely to extract `account_id` for per-account key lookup. Replay keys persist after disconnect on unlinked `netsuite_processed_webhook_events` rows. Merchants must configure SuiteScript (or equivalent) to sign outbound notifications to this contract. Persistent 401/403 SuiteTalk responses fail closed until reconnect.
  • Detail reads: Sparse list rows hydrate via SuiteTalk internal record `id`; `tranId` is preserved for display.

Prohibited: screen scraping, credential sharing across tenants or workspaces, unauthorized data mining, or reselling NetSuite API data.

Seller controls

- Disconnect NetSuite in AtlasCore to stop sync and purge stored credentials

See our Privacy Policy and Disconnect Marketplace guide.