Regarding Bullhorn API "*" deprecated, Data should be same with * and field names, why error "TOO_MUCH_DATA_REQUESTED"?

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

Moderators: StaffingSupport, s.emmons, BullhornSupport

Post Reply
mitulshah
User
Posts: 1
Joined: Thu Oct 29, 2020 5:47 am

Regarding Bullhorn API "*" deprecated, Data should be same with * and field names, why error "TOO_MUCH_DATA_REQUESTED"?

Post by mitulshah »

Hi,

We are using the "*" in bullhorn API search calls.
as per the notification that "*" is being deprecated, and need to use
individual field names for the call.

We have updated our API calls to specify all the individual fields in the
call, but so some reason the calls have started returning
"TOO_MUCH_DATA_REQUESTED" message with partial data being returned.

Why is it that the same call works with "*" but not with the individual
column list?
We used to call 200 records with * call which used to work but calling 200
records with field name lists, The only change is * to field list, The
amount of data being returned should be the same so why is it now throwing
error message with part of the data.

Also, For few entities even if I call 15 records it returns the following error.
"The requested number of to-many field queries exceeds the maximum of 200. The number of queries equals the count value times the number of to-many fields requested in the fields query parameter.|| severity: WARNING|| type: TOO_MUCH_DATA_REQUESTED"

The error says a maximum of 200 records, even if calling only 15 records.

Can you please suggest how to handle this?

Thanks,
Mitul
lauraingalls
User
Posts: 11
Joined: Wed Feb 26, 2020 12:19 pm

Re: Regarding Bullhorn API "*" deprecated, Data should be same with * and field names, why error "TOO_MUCH_DATA_REQUESTE

Post by lauraingalls »

Hi Mitul,

Can you provide an example (or examples) of the call you're making so I can take a closer look into what may be causing the errors?

Thank you.
Laura Ingalls
Bullhorn Enterprise Support Analyst
Post Reply