40060: Invalid value for field 'project_id' as a response to expense.create

[Kirill]

Hello,

Here is a setup: Sample Project, assigned to the -internal- client.
project.list returns:
<project>
<project_id>1</project_id>
<name>Sample project</name>
...
<client_id></client_id>
...
</project>

Then, when project_id: 1 and client_id: "" (or 0) is used in
expense.create, the error "40060: Invalid value for field
'project_id'. Invalid value '1' for field 'project_id'." is returned.

Projects, assigned to real clients (where the project.list returns non-
empty <client_id>), can successfully be used in expense.create.

What's the correct way to submit expenses to projects of -internal-
client via API?

--
Kirill

[Nox Dineen (FreshBooks)]

Hi Kirill,

I'm afraid there isn't a way to associate an expense with an internal project. The limitation exists within the web app as well as via the API. Truthfully I'm not sure what the rationale for that restriction is, but I'll bring it up with the web app's product manager for re-consideration.

Cheers,

Nox Dineen | FreshBooks

[Kirill]

Dear Nox,

> I'm afraid there isn't a way to associate an expense with an internal
> project. The limitation exists within the web app as well as via the API.

I'm so sorry - I must have been looking at the wrong field in the web
app. As long as web app and API agree, everything is good.

So, the only remaining problem for me - as discussed in another thread
- is compound taxes on expense.create. Hopefully, you will give me
good news soon.

Thank you!

--
Kirill