Updating Placements Issue

Forum for users and developers of Bullhorn's API service.

Moderators: StaffingSupport, s.emmons, BullhornSupport

Post Reply
Posts: 1
Joined: Wed Feb 17, 2021 6:04 pm

Updating Placements Issue

Post by RyanNCData »


We are currently sending the following request to the server to update a placement:


POST https://rest33.bullhornstaffing.com/res ... cement/270

[HTTP Headers]
HTTP Auth Scheme: 0
POST /rest-services/<redacted>/entity/Placement/270 HTTP/1.1
Host: rest33.bullhornstaffing.com
Accept: application/json
Accept-Encoding: gzip, deflate
User-Agent: CData Data Provider Engine - www.cdata.com - Accepts: gzip
Content-Type: application/json
Content-Length: 41
BHRestToken: <redacted>

{"dateEnd": "2017-08-30T05:00:00Z"}


This follows the documentation as described here: http://bullhorn.github.io/rest-api-docs/#post-entity . We did check the metadata for this field to confirm it was not confidential as per the warning in the docs.

We receive a 200 OK response from the server:


[HTTP Headers]
HTTP/1.1 200 OK
Content-Type: application/json;charset=UTF-8
X-RateLimit-Limit-minute: 3000
X-RateLimit-Remaining-minute: 2997
Server: Apache-Coyote/1.1
X-Kong-Upstream-Latency: 253
X-Kong-Proxy-Latency: 1
Content-Length: 119
Date: Fri, 12 Feb 2021 01:26:00 GMT
Connection: keep-alive



Upon completion of the request the dateEnd value is null, not 2017-08-30T05:00:00Z as expected. Could you please provide some clarification on why the above request would fail to update the entity?

Thank you,
Posts: 31
Joined: Wed Feb 26, 2020 12:43 pm

Re: Updating Placements Issue

Post by ggaragiola »

Hello Ryan,

This is Grant with Bullhorn Support.

When updating date values via Rest API they must use EPOCH Timestamps. Below is a good website for these conversions:

So for the example you provide you will actually want this as your payload:

{ "dateEnd" : "1504130400000" }

Thank you,

Bullhorn Support.
Post Reply