BookYourPTO

Changelog

Stay up to date with the latest changes, improvements, and bug fixes in BookYourPTO.

BookYourPTO v1.1.4 release notes

v1.1.4

Mobile app

  • BookYourPTO is now on Android. The mobile app, already available for iPhone, can now be installed from Google Play (com.anhourtec.bookyourpto). Android users sign in with their existing BookYourPTO account. Download links for both platforms are on bookyourpto.com/mobile-app.

Public API

  • A REST API and webhooks. Organizations can now connect their own systems, scripts and integration tools (Zapier, Make, Workato and the like) to BookYourPTO. The REST API reads and writes people, departments, teams, leave, leave balances, public holidays and locked dates, time entries and timesheets, projects and clients, shifts, expense reports, documents, onboarding, and each person's training, certifications, assets, benefits, compensation, custom fields and goals. Webhooks send an event to your own HTTPS address when something happens, so an integration does not have to keep asking. In all, the API has 67 operations across 17 resource groups, 39 scopes and 24 webhook event types.
  • Who can use it. The API comes with every paid plan — Pro, Business and Enterprise — and not the Free plan. It is off by default: an executive turns it on under Settings → API, and a new organization starts with no tokens and no webhook endpoints. Downgrading to Free, turning the API off, or a subscription falling past due stops every token and every webhook at once.
  • Tokens act as the person who owns them. A token can never do more than its owner could do in the app. It sees the same people, departments and records, through the same rules the app uses: a department head's token sees their departments, an employee's token sees what that employee sees, private leave is redacted the same way, and the time tracking, expenses and one-on-ones switches apply. The owner's role and status are checked again on every request, so a token stops working the moment its owner is deactivated, offboarded or moved to a role that may not hold tokens.
  • Managing tokens. Settings → API lists every token, with who owns it, when it expires and when it was last used. Each token has a required expiry (the organization sets the maximum, 90 days unless changed, up to a year), an optional list of IP addresses or ranges it may be used from, and is shown once when it is created. Rotating a token can keep the old one working for 0, 1, 24 or 72 hours while your systems switch over. Owners are emailed 7 days before a token expires. Revoking is immediate, and every change is recorded in the audit log. Administrators and executives can create tokens for people ranked below them and transfer ownership; by default only administrators and executives may create tokens, and the organization can allow other roles, who then see a Personal API Tokens page with their own tokens only.
  • Scopes and API roles. Each token is limited to the scopes it is given, such as leaves:read or time_entries:approve, and never beyond what its owner's role allows. Personal details, government ids, compensation and document files are separate scopes that only administrators or executives can hold, and every read of them is recorded. An API role is a named set of scopes — start from a template such as Leave sync, Time and payroll export or Read-only directory — and editing the role updates every token that uses it.
  • Writes follow the app's rules. Booking, cancelling, approving and rejecting leave, editing and approving time entries, deciding expense reports, and adding or updating people, departments, teams, training and assets all go through the same steps as the app: the same checks, notifications, calendar sync and audit entries. Every change made through the API is marked in the audit log as made through the API, with the token that made it. Through the API no one approves their own leave, time entry or expense report, whatever their role.
  • Rate limits. Each token may make 120 requests a minute (with short bursts of up to 20 a second), each organization 600 a minute, and every response says how much of the allowance is left. Downloading a document's file counts as 10 requests.
  • An interactive reference. /developers/api documents every endpoint, scope, error and webhook event, with example requests and responses, and lets you send a test request to your own organization. The OpenAPI document and a Postman collection can be downloaded from it. Organizations with the White-Label add-on see their own brand throughout the reference, the console and the downloads.
  • Webhooks. Administrators and executives add endpoints on the Webhooks tab of Settings → API, or through the API. Choose the events to receive — leave requested, approved, rejected, cancelled, updated or with a cancellation requested; people added, updated, deactivated or reactivated; departments created, updated or deleted; time entries submitted, approved or rejected; timesheets finalized; expense reports submitted, approved, rejected or paid; documents signed or declined — or every event the endpoint's owner may receive.
    • An endpoint receives only what its owner could read through the API. An event about a record the owner cannot see is not sent, and a webhook never carries personal details, government ids, compensation, locations or document contents.
    • Every delivery is signed with the endpoint's secret using the open Standard Webhooks scheme, which has verification libraries for most languages. The secret is shown once; rotating it keeps the old one valid for 24 hours, and deliveries in that window carry both signatures.
    • A delivery that fails is retried over about 45 hours, up to 8 attempts. An endpoint that has failed for 72 hours is switched off and its owner and the organization's executives are emailed. Send test event, a delivery log for each endpoint and Redeliver are on the same tab.
    • Each organization can have up to 10 endpoints. Webhook addresses must be public https:// addresses.
  • Existing document webhooks move to the new system. Organizations that had a document signing webhook set up by our team will find it on the Webhooks tab, paused until an administrator confirms it. It now uses the signing scheme above, with retries and a delivery log. The signature format has changed, so update the receiving system to verify the new webhook-signature header before resuming the endpoint; the old X-Webhook-Signature header is no longer sent.
  • The public demo shows the API console but refuses every change made through the API.
  • A webhook's signing secret is shown once. Repeating POST /webhooks with the same Idempotency-Key returns the endpoint with signing_secret: null and a note in meta; the secret is never kept for replays.
  • user.updated is sent only when a field in the User object changes. A change to employment or personal details alone no longer sends an event.

Security

These fixes come from a security review of the whole server carried out before the API was built.

  • The two-factor step could be skipped. A sign-in waiting at the two-factor step could be used as a full session. A session is now issued only once sign-in is complete, and the two-factor step has a credential of its own that nothing else accepts. Existing sessions carry on.
  • Leave status could be changed without going through approval. Editing a leave request could also change its status, which let some users approve requests — including their own — outside the approval flow. Status now changes only through approve, reject and cancel, with their usual checks.
  • Time entries and timesheets could be approved by the person who submitted them. Nobody now approves their own time entries or timesheets — one at a time, in bulk, or from the approval queue — and the approval queue and its badge no longer count your own.
  • Refund requests were visible beyond the organization's administrators. They are now listed only to administrators and executives, and only for their own organization.
  • Custom profile fields and tables were readable by colleagues. An employee now sees only their own values, and only on tabs shown to their role. Administrators and executives still see everyone's. Values can no longer be saved against a person in another organization.
  • Data deletion could reach outside the organization. Erasing a person's data now finds them only inside the organization of whoever asked.
  • Employee notes marked for managers are now shown to a department head only for people in the departments they manage.
  • Organization backups and user updates returned more than they should. The backup no longer includes the outgoing mail password or anyone's sign-in secrets, and saving a person's profile no longer sends back sign-in related fields.
  • Expense claims and projects accepted references from elsewhere. A claim's department, payee, project and receipts must now belong to your organization and your claim, and a project's details, board, tasks, issues and comments follow the same department rule as the projects list.
  • Connecting a calendar is tied to the person who started it. The Google Calendar and Outlook connection now checks that it finishes for the same person who began it.
  • An account that has to finish setting up — verify its email, change its password or set up two-factor — can reach only the pages needed to do that.
  • Outgoing mail servers and Teams webhooks must be public. An organization's own SMTP server must be on a public address, checked when saved and again before each connection; if it later points somewhere internal, mail goes out through our own mail server instead, and the stored password is not sent. Teams webhook addresses must be on Microsoft's own domains.
  • AI assistant connections. The consent screen for connecting an AI assistant now names the site you will be returned to and warns that the application is not verified by us.
  • Schedules are generated at most a year either side of today, whatever range is asked for.

Bug fixes

  • Two people deciding the same request at once. Approving or rejecting a leave request, a cancellation request or a time entry, cancelling a leave, and signing or declining a document now refuse a second, simultaneous decision (409) instead of recording it twice, with a second notification and webhook event. Approving a time entry that is already approved is refused too.
  • Leave could be booked for a deactivated or offboarded person. It is now refused, in the app and through the API.
  • A webhook delivery cancelled while it was being sent (endpoint paused or removed) could be marked delivered or queued again afterwards. It now stays cancelled.
  • Document signing events were emitted by two paths. The retired document webhook dispatcher has been removed; each signature or decline sends exactly one event.
  • A department head could learn whether another department's leave was already decided. Approving or rejecting a request from outside their departments answered "already approved" rather than refusing. The department is now checked first, so they learn nothing about the request.
  • An address with an unusual # part could break navigation. Following a link whose part after # was not a valid page anchor raised an error instead of opening the page. It now opens the page and simply does not scroll.

Improvements

  • API access ends when a person leaves. Offboarding or erasing a person revokes every API token they own or hold, in the same step that deactivates them, and switches off webhook endpoints they own. Reactivating them later does not bring any of it back; new tokens must be issued. Moving someone to a role that may not hold tokens revokes any token secrets they hold for other people.
  • Editing an approved time entry sends it back for approval. When someone other than an administrator or executive changes the hours, break, project, task or billing of an approved or rejected entry, it returns to pending for an approver to look at again. Description, notes and tags can still be edited freely.
  • Only administrators and executives set an hourly rate on a time entry.
  • Time entries in a finalized timesheet are frozen. Once a period's timesheet is finalized or signed, nobody — whatever their role — changes its entries' hours, rate or billing, or moves an entry into that period.
  • SSO settings are executive-only. Administrators can no longer change the identity provider or the role new SSO users receive, and SSO sign-up never creates anyone above Department Head.
  • Public holidays and holiday overrides are managed by administrators. Adding or removing the organization's holiday locations, and setting a person's holiday overrides, is now limited to administrators and executives.
  • A colleague's personal holidays stay with the people allowed to see them. Someone's holiday overrides and personal holiday calendar are shown to them, to administrators and executives, and to a department head whose departments include them. Everyone else, on the calendar and the Dashboard, sees the organization's holidays for that person.
  • Profile edits in the audit log name the fields, not personal values. The audit entry for a profile change lists every field submitted, and records the value only for organizational settings such as role, department and manager — not addresses, phone numbers, dates of birth or identification numbers.