We have updated our documentation to include rate limits for all API endpoints

What has changed:

  • Detailed rate limits: each section in the reference guide now includes a main page which displays the rate limits for all endpoints in that section. This helps you understand the usage limits and plan your API calls accordingly.
  • Rate limits headers: we've included details about HTTP response header which provide real-time information about your current usage and remaining quota.
  • Best practices section: we've added a best practices section with general instructions on how to manage rate limits effectively. This includes tips on optimizing your API usage to stay within the limits and avoid potential issues.

To learn more, see Rate limiting.

Example:

We are pleased to announce that Bob’s Webhooks now support Time Off events.

Webhooks are a way for Bob to communicate with other applications automatically. When a specific event occurs in Bob, a webhook sends real-time data to the other application through an HTTP request. This enables seamless integration and automation between different systems.

Benefits:

  • Real-Time updates: Webhooks provide instant notifications about changes, allowing your application to react immediately.
  • Automation: Reduce manual tasks by automating workflows based on specific events.
  • Efficiency: Streamline processes by integrating systems and reducing the need for frequent API calls to check for updates.

Supported Time Off Events:

  • Approved: Get notified when a time off request is approved.
  • Declined: Receive updates when a time off request is declined.
  • Canceled: Know immediately when a time off request is canceled.
  • Deleted: Be informed when a time off request is deleted.
  • Updated: Get informed when a time off request is updated.
  • Submitted: Receive notifications when a time off request is submitted.
  • Created from Import: Stay updated when time off requests are created through imports.

These new webhook events help you keep your systems synchronized and ensure you have up-to-date information about employee time off statuses. To learn more, see Time off Webhooks events.

To learn more, see Time off Webhook events.

You can now retrieve specific table data for up to 200 different employees in a single API call.

Benefits:

  • Optimized data retrieval: this enhancement allows you to obtain the necessary data in a consolidated and optimized manner, reducing the need for multiple API requests and improving performance.
  • Improved efficiency: by retrieving data in bulk, you can streamline your processes and reduce the load on your API calls.

Pagination Support:

  • Efficient data management: endpoints that perform bulk read also support pagination, which helps in managing large datasets by breaking them into smaller, more manageable chunks. This improves performance and makes data handling more efficient. To learn more, see Pagination in Bob’s API.

Supported endpoints:

We are pleased to announce the release of Bob's Hiring API, designed to enhance your recruitment process.

With Bob Hiring you can promote job openings, build your candidate pipeline, and send offers. With Bob's Hiring API you can fetch the job ads from Bob's careers page and post them to your custom careers page.

Key Features:

  • Fetch job ads: retrieve job ads from Bob's careers page and post them to your custom careers page.
  • Application form links: get a link to an application form for new candidates to apply for the job.

Highlights:

  • Efficient job ads management: fetch lists and details of job ads.
  • Custom career page integration: create corresponding pages on your career site for each job ad retrieved.
  • Easy application process: utilize the 'applyUrl' field in the job ad to link directly to Bob-hosted application forms and streamline adding applicants to Bob.

To learn more about how to set up the integration, see Integrate your custom careers page with Bob Hiring.

For more detailed instructions for developers, see the Hiring reference guide

We have made some changes to the reference guide menus to improve navigation and clarity.

  • People endpoints update: the "People" section now includes only the endpoints for the entire "employee" record or basic "fields" (not tables).
  • Employee Tables: all other people APIs, which access employee tables, have been moved to the new "Employee Tables" section.
  • Main page for each category: each category now has a main page that includes basic information about accessing these endpoints and their rate limits.

These enhancements aim to provide a more organized and user-friendly experience.


🚧

As of July 31st, 2024, we will be discontinuing the Read my tasks endpoint

This change is part of our ongoing efforts to enhance security and streamline our API authentication methods. It may require some adjustments on your end, but the good news is that we have already prepared an alternative endpoint that can replace the functionality of the discontinued endpoint: Read tasks of a specific employee. This endpoint will provide you with similar functionality to the one you are currently using.

What do you need to do?

We recommend updating your code to use this endpoint before the discontinuation date to avoid any disruption in your services. If you have any questions or need further assistance, please contact our support team.


We've enhanced our document management capabilities with new endpoints. Previously, you could manage documents in either an employee's confidential or shared folders. Now, you have the flexibility to manage documents across all of an employee's folders.

The new endpoints include:

These new features provide more control and flexibility in managing employee documents. If you have any questions or need further assistance, please contact our support team.

❗️

Effective October 31, 2024 the "API Access Token" authentication method will be discontinued.

Starting October 31, 2024, we will exclusively support the API Service Users method for API authentication. This change is a step towards strengthening security measures and ensuring a more robust and reliable service for all our users.

What do you need to do?

  • By June 15, 2024: Ensure you do not create any new API Tokens, as it will no longer be possible. Please incorporate this change into your processes. You can continue to manage existing tokens until October 31, 2024.
  • By October 31, 2024: Transition fully to the API Service Users method for API authentication.

Please ensure you update your systems and processes accordingly. If you have any questions or need further assistance, feel free to contact our support team.

🚧

As of July 31st, 2024, we will be discontinuing the Read Avatar for Logged-in User endpoint.

This change is part of our ongoing efforts to enhance security and streamline our API authentication methods. While this may require some adjustments on your end, the good news is that we have already prepared alternative endpoints that can replace the functionality of the discontinued endpoint: Read Avatar for an Employee ID and Read Avatar for an Employee Email.

What Do I Need to Do?

By July 31st, 2024: Update your integration to use the alternative endpoints:

  • Read Avatar for an Employee ID
  • Read Avatar for an Employee Email

Updating your systems to use these endpoints before the discontinuation date will help avoid any disruption in your services.

If you have any questions or need further assistance, please contact our support team.

🚧

The following endpoints will be deprecated on March 31, 2024: 'Read All Company Employees' and 'Read Company Employee by ID'. Additionally, as of April 2, 2024, the rate limits on these endpoints will be reduced from 100 to 70.

As part of our ongoing efforts to enhance performance, stability, and security, we're updating our APIs. We've introduced a new Search API to replace the two GET endpoints for reading all company employees and employees by ID.

The new Search API allows you to retrieve specific employee data and is designed for controlled access by API Service Users only, offering enhanced security and stability.

What Do I Need to Do?

  • Familiarize yourself: Review the new Search API documentation.
  • Update implementations: Review and update your API implementations to use the new endpoints.
  • Test and transition: Thoroughly test the new API in your environment and transition to it in your production systems.

Benefits:

  • Faster performance: Quicker responses with optimized speed.
  • Enhanced stability: Improved service reliability.
  • Balanced resource use: Fair allocation and prevention of misuse.

Please ensure you update your integrations to avoid disruptions. If you have any questions or need further assistance, please contact our support team.