How to fetch expense data from NetSuite API with Python

Introduction

This article is part of a series covering the NetSuite API in depth. It focuses on a specific, high-frequency use case: retrieving expense data from NetSuite using its REST API.

If you’re building integrations around finance, reimbursements, or expense reporting, this is a core workflow you’ll need to get right. For a broader view of the NetSuite API, including authentication models, rate limits, and other supported use cases, you can refer to the complete NetSuite API guide here.

Prerequisites

Before you begin, ensure the following are in place:

• Access to a NetSuite account with API permissions enabled
• Consumer Key, Consumer Secret, Token ID, and Token Secret for OAuth 1.0 authentication
• A Python environment with the required libraries installed (requests and oauthlib)

Without these, API access will fail.

API Endpoints

• Base URL
• https://<ACCOUNT_ID>.suitetalk.api.netsuite.com

• Expense Report Endpoint
• /services/rest/record/v1/expenseReport


This endpoint is used to retrieve expense report records from NetSuite.

Step-by-Step Process

1. Authentication

NetSuite uses OAuth 1.0 for REST API authentication. Below is a basic Python example to configure OAuth credentials:

from requests_oauthlib import OAuth1

auth = OAuth1(
    'CONSUMER_KEY',
    'CONSUMER_SECRET',
    'TOKEN_ID',
    'TOKEN_SECRET'
)

‍
This authentication object is reused across all API requests.

2. Fetch Expense Data

Once authenticated, make a GET request to the Expense Report endpoint:

import requests

url = "https://<ACCOUNT_ID>.suitetalk.api.netsuite.com/services/rest/record/v1/expenseReport"
response = requests.get(url, auth=auth)

if response.status_code == 200:
    expense_data = response.json()
    print(expense_data)
else:
    print("Error:", response.status_code)

A successful response returns expense report data in JSON format.

Common Pitfalls

When working with the NetSuite Expense Report API, teams commonly run into the following issues:

1. Incorrect OAuth credentials causing authentication failures
2. Not accounting for NetSuite rate limits, leading to blocked requests
3. Ignoring pagination and retrieving only partial data
4. Skipping SSL validation, introducing security risks
5. Hardcoding account-specific URLs, reducing portability
6. Not handling API version changes, which can break integrations
7. Missing error handling, resulting in ungraceful failures

These are operational issues, not edge cases, and should be addressed early.

Frequently Asked Questions

How do I find my NetSuite Account ID?
Log in to NetSuite and navigate to Setup → Company → Company Information.

What is the rate limit for the NetSuite API?
NetSuite enforces concurrency limits based on account type.

Can I use other programming languages?
Yes. Any language that supports OAuth 1.0 can be used.

How do I handle pagination?
Use the next link provided in the API response to retrieve additional pages.

Is there a sandbox environment available?
Yes. NetSuite provides a sandbox environment for testing.

What data formats are supported?
Both JSON and XML are supported.

How do I update an expense report?
Use the PUT method on the same endpoint with the updated expense data.

Conclusion

Fetching expense data from the NetSuite API is a straightforward process once authentication and permissions are correctly configured. By using the Expense Report endpoint and handling common pitfalls such as pagination and rate limits, you can reliably access the data required for expense tracking and reporting workflows. Use Knit to make the process faster and simpler with our unified API.