Fix API and Zapier problems
Fix failed authentication, billing, IDs, validation, rate limits, and Zapier connections.
Start with the HTTP status and the error.message. Keep the full response, but remove keys, client data, and signed file URLs before sharing it.
I get 401 Unauthorized
Check these items:
- Use
https://public-api.sydnee.app, nothttps://api.sydnee.app. - Send
Authorization: Bearer YOUR_API_KEY. - Make sure there is one space after
Bearer. - Check that the key was not deleted.
- Check that API subscription access is active.
The initial free trial without a payment method cannot use the API. API access is available during any trial period shown at checkout, while the selected plan is active, and during Sydnee's current grace period for a past-due payment.
If a key may have leaked, delete it. Do not test an exposed key again.
I get 402 Payment Required
The current public API does not intentionally return 402. Its API access check returns 401 when the key or subscription access is not valid.
Check the real HTTP status and error body. If the response is truly 402, save the method, path, time, and safe error details for Sydnee support. Do not replace the key or change billing based on the label alone.
I get 403 Forbidden
The key is valid, but the action is not allowed. Examples include trying to remove the workspace owner or sending a request to a team member instead of a portal user.
Read the message before changing the request. A new key does not grant a different API role.
I get 404 Not Found
- Check the method and full
/v1path. - Check that the resource belongs to the key's workspace.
- Use the account CUID, not its slug or numeric database ID.
- Use the board, section, task, tag, and template IDs returned by the API.
- Use the numeric account-membership ID for account user routes.
- Make sure the parent account or board is not archived when the action needs an active parent.
List the parent resource again and copy its current ID. Do not build an ID from a URL.
I get 400 or 409
For 400, read error.issues. It shows the bad field or query value.
For 409, read error.details when present. The current record may have changed, a board or task rule may block the action, or a version value may be stale. Fetch the resource again before retrying.
I get 429 Too Many Requests
Stop sending requests until the Retry-After time passes. Use the rate-limit headers to slow the whole workspace integration.
Current /v1 limits are 300 reads and 100 writes per minute for the workspace.
A paged list repeats or skips items
Use the exact nextCursor from the prior response. Keep the same route and filters. Do not decode or edit the cursor.
My Zapier connection stopped working
- Check whether its Sydnee API key was deleted.
- Check the workspace plan and payment state.
- Create a new key if needed.
- Reconnect the Sydnee account in Zapier with the new key.
- Retest each Zap before turning it back on.
A Zapier field is empty
The selected item may be archived, outside this workspace, or the wrong type. Portal-user fields list portal users, not team members. Template fields need a current request template or task template.
Refresh the field. If the item is still missing, open Sydnee and confirm it exists and is active.
A Zapier trigger did not run yet
The public Sydnee listing does not promise instant trigger delivery. Make sure the Zap is on and the connection test passes. Then create a new test item and check the Zap's run history.
I get 500 Internal Server Error
Retry once. If it fails again, save the method, path without private IDs, time, status, and returned error id. Send those details to Sydnee support. Never send the API key or request data.