API access issue for Ledger_GetNominalLedgers / Ledger_Search / Report_ProfitAndLoss on two accounts

Hi,

We are using the QuickFile API across multiple QuickFile accounts for read-only bookkeeping/reporting automation.

For most accounts, the same integration works as expected. We can retrieve nominal ledgers and build trial balance data using the documented ledger/report methods.

However, we have two accounts where the credentials have been checked manually in the QuickFile UI and appear to be correct, but the API calls fail for ledger/reporting methods.

Affected accounts:

  • PERCEPTION7 LTD
  • REMOTE DRAFTING SERVICES LTD

What we have checked:

  • Account number has been checked manually in QuickFile and matches our configuration.
  • API key has been checked manually in QuickFile and matches our configuration.
  • Application ID has been checked manually in QuickFile and matches our configuration.
  • The same integration works on other QuickFile accounts.
  • This does not look like a rate limit issue.

Methods involved:

  • Ledger_GetNominalLedgers
  • Ledger_Search
  • Report_ProfitAndLoss

Current behaviour:

  • Ledger_GetNominalLedgers fails for both affected accounts.
  • Report_ProfitAndLoss also fails for these accounts.
  • Other accounts using the same code path are able to return data.

Questions:

  1. Are ledger/reporting API methods controlled per account or per registered application in a way that could explain this?
  2. Is there a setting in the QuickFile account, API section or app configuration that needs to be enabled for Ledger_GetNominalLedgers, Ledger_Search and Report_ProfitAndLoss?
  3. Can QuickFile support check whether these two accounts or the registered application have access to those methods?
  4. If the API credentials are accepted for some methods but not for ledger/reporting methods, what is the expected way to diagnose this?

Thanks.

Hi @motoko

What is the error message you’re seeing in response to the API calls?

Hi,

We have re-checked this on our side and it looks like the issue is now resolved. API
keys had a trailing space at the end. :confused:

Thanks for your help, and apologies for the false alarm.

1 Like