-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue adding prospect #459
Comments
We are having the same issue. We are trying to add prospects and include them in specific pools/departments/offices. We started with this endpoint https://developers.greenhouse.io/harvest.html#post-add-prospect and realized it will not accept prospect_pool _id, prospective_department_id, or prospective_office_id as parameters. Now we're using this endpoint https://developers.greenhouse.io/harvest.html#post-add-candidate and getting a 422 Unprocessable Entity error message with the following response:
We are passing
Alternatively, if we create the prospect using https://developers.greenhouse.io/harvest.html#post-add-prospect we are able to update the pool/department/office by using the https://developers.greenhouse.io/harvest.html#post-add-application-to-candidate-prospect however it seems like this should not have to be a 2 step process. |
Hello, I'm trying to add a prospect, based on the documentation provided here: https://developers.greenhouse.io/harvest.html#post-add-prospect and here: https://developers.greenhouse.io/harvest.html#the-application-object
I am able to add the prospect correctly, but the prospect does not get added the the prospect pool as I would have hoped. I have double checked IDs etc to make sure they're ok, but still can't see any obvious issue.
Below is the structure of the JSON request I'm making, with data redacted for security:
The API Key I use has access to add prospects - as far as I can tell, that should be all I need.
Is this a documentation problem?
As a side note, it would be VERY useful to list the permissions required by a given endpoint in the documentation directly.
The text was updated successfully, but these errors were encountered: