Skip to main content
Invoice Comment Add API

Authentication

All requests require an API key in the request headers. Headers:

Request

Content-Type: application/json

Path Parameters

Body Parameters

Mentions

Comments support user mentions in the form @<userId> (the user’s id / slug). When rendered via the Invoice Comments API, valid @<userId> tokens are replaced with the user’s display name (e.g., @John Doe). Mentions whose user id does not exist in your organization are kept in the text as-is — they are not rejected.

Code Examples

Success Response

HTTP Status: 200 OK Response Fields:

Response Example

Error Responses

Missing Comment

HTTP Status: 400 Bad Request

Invalid Comment Type

HTTP Status: 400 Bad Request

Invoice Not Found

HTTP Status: 404 Not Found

Access Denied

HTTP Status: 403 Forbidden
Returned when the caller is not an admin / bookkeeper, did not create the invoice, and is not the owner of its vendor.

Authentication Errors

HTTP Status: 401 Unauthorized

Permission Errors

HTTP Status: 403 Forbidden

Internal Error

HTTP Status: 500 Internal Server Error

Best Practices

  • Keep comments under 1500 characters — longer text is rejected with VALIDATION_ERROR
  • Use @<userId> to address specific users — fetch the id from the User List API or User Details API
  • The comment author is the user tied to the API key — there is no userId field in the body
  • Use the Invoice Comments API to retrieve the thread with mentions resolved to user names