Rippling vs Zoho People

Rippling

API tokens carry any of 162 scopes and can never see more than their owner, and hires and worker changes land as drafts for a person to review. There is no public price, trial or self-serve signup, and status.rippling.com shows five incidents marked critical between 16 July and 29 September 2026.

Zoho People

The REST API covers employee forms, leave, attendance, timesheets, files and learning, with per-endpoint rate limits and Markdown docs listed in an llms.txt. No OpenAPI spec, official SDK or dated API changelog was found, the Free plan has no API access, and several scopes come only as ALL.

Rippling

1. Call https://rest.ripplingapis.com with a Bearer token and pin Rippling-Api-Version. Use V1 at api.rippling.com only for resources that exist nowhere else
2. Treat a null field as possibly hidden. Check __meta.redacted_fields, the token's scopes and whether expand was sent
3. Follow next_link until it is null. The default page is 50 records and a limit above 100 returns 400
4. Stay under 300 requests per IP in any 10 seconds. Going over rejects every request for the next 10 seconds
5. Send an Idempotency-Key on POST /hires/ and POST /draft-transitions/, then poll the request until it reaches a final status

Zoho People

1. Use the accounts host and API host of the organisation's data centre. Tokens issued in one region fail in another
2. Stay under each page's threshold, often 30 calls a minute. Exceeding it locks that endpoint for five minutes
3. Page form records with sIndex and limit, at most 200 a call, and use modifiedtime to fetch only changes
4. Look up form and field label names with /api/forms before writing. inputData takes label names, and lookup fields take record IDs
5. Send the refresh token and client secret in the POST body, not the query string, and store the refresh token, which never expires