goodday API v2 — Projects, Tasks & Users

REST API for goodday work management. Base URL: https://api.goodday.work/2.0 — HTTPS only, the API does not answer over HTTP.

Authentication

Every request carries the API token in the gd-api-token header. Read it from the environment variable GOODDAY_API_TOKEN — never hardcode a token into code or a command.

curl -H "gd-api-token: $GOODDAY_API_TOKEN" https://api.goodday.work/2.0/projects

If GOODDAY_API_TOKEN is unset, stop and tell the user to export it (the token comes from their goodday Organization → Settings → API screen); do not proceed without it.

Conventions

• All write routes (POST/PUT) identify the acting user with a user-id field in the JSON body — userId, fromUserId, or createdByUserId as noted per route. This is required.
• Dates are YYYY-MM-DD strings. On PUT /task/{TASK-ID}/update, sending null for a nullable field resets it.
• {PROJECT-ID}, {TASK-ID}, {TAG-ID}, {USER-ID} are path segments you substitute with real IDs.