Developer GuideAPI Reference
Entity Endpoints
Entity data access via the SuitePortal API
Entity Endpoints
Entity data (customers, vendors, contacts, employees) is accessed through synced datasets, not dedicated API endpoints.
Current Status
Direct entity API endpoints are not yet implemented. Entity data is available through:
- Synced datasets - Query via internal data services
- Portal UI - View in the SuitePortal dashboard
- Tenant Pages - Custom portal pages displaying entity data
Planned Endpoints
The following entity endpoints are planned for future releases:
| Endpoint | Status |
|---|---|
GET /api/v1/customers | TODO: Not yet implemented |
GET /api/v1/contacts | TODO: Not yet implemented |
GET /api/v1/vendors | TODO: Not yet implemented |
GET /api/v1/employees | TODO: Not yet implemented |
GET /api/v1/items | TODO: Not yet implemented |
Available Transaction Endpoints
For now, transaction data is available via:
GET /api/v1/invoicesGET /api/v1/salesGET /api/v1/purchasesGET /api/v1/fulfillments
See Transaction Endpoints for details.
Entity Data in Transactions
Transaction records include entity references:
| Field | Description |
|---|---|
data.entity | NetSuite entity internal ID |
data.entityid | Entity identifier string |
Use these fields to link transactions to entities.
Workaround: MCP Server
The MCP (Model Context Protocol) server provides query access to transaction data with entity filtering. See internal documentation for MCP setup.