When a tool is connected to Spendesk through the API (your ERP, a data warehouse, a script your team wrote), you may need to know what it actually did: to answer a security review, or to understand why a sync failed. The API audit log lists the calls made with your API keys and OAuth integrations.
This article is for Account Owners and Admins.
Open the API audit log
Go to Settings → Integrations.
Open the API audit log tab.
To see only the problems, choose Failed in the filter at the top right. Successful shows the others; All requests shows everything.
The newest calls are at the top; click Load more to see older ones. A call shows up within a minute.
What each column tells you
Column | What it means |
Date | When the call was made |
Auth type | API key, or OAuth2 for an integration connected with OAuth |
Client / key ID | The ID of the API key or OAuth client that made the call. Your keys are listed in the API management tab |
Operation | What was asked, for example |
Status code | The answer: |
Entity | The company (entity) the call was about |
User | The Spendesk user the key or integration acts for |
Duration | How long Spendesk took to answer |
Correlation ID | Give it to Spendesk support when you report a problem with a call |
What the log does not show
AI assistant (MCP) calls. What Claude, ChatGPT, Copilot or another assistant did is in the Action log of each connection, under Settings → Integrations → Spendesk MCP.
Which record was read or changed. The log shows the operation (for example "update a supplier"), not the supplier's ID, nor the filters sent.
The IP address the call came from.
Calls to an address that does not exist on the API.
Note: There is no export and no filter by key or date yet.
Related articles