Requests and responses

Request conventions

• Base URL: https://api.godaily.co.il/v1
• Methods: GET and HEAD only. Other methods return 405 method_not_allowed with Allow: GET, HEAD.
• Accept: use Accept: application/json.
• Authentication: send Authorization: Bearer $DAILY_API_KEY.
• Query strings longer than 2,048 characters return 400 invalid_filter.
• Unknown query parameters are rejected; they are not silently ignored.

There are no request bodies in v1.

IDs

Resource IDs are UUID strings. Use them exactly as returned. Invalid or path-like IDs return 400 invalid_filter; an absent or out-of-scope ID returns 404 resource_not_found.

Dates, times, and timezones

Timestamp fields such as created_at, updated_at, and due_at use ISO 8601 in UTC, for example 2026-07-21T11:45:00.000Z. Date-only fields such as issue_date, payment_date, and due_date use YYYY-MM-DD and do not carry a timezone.

Filtering timestamps must be strict ISO 8601 values. created_after and updated_after are exclusive (>), not inclusive.

Currency and monetary values

Currency codes are three-letter strings such as ILS. Monetary fields ending in _minor are integers in the currency's minor unit. For ILS, 218300 means ₪2,183.00. Do not parse these values as floating-point major units.

Inventory quantities and document line quantities are fixed three-decimal strings, such as "42.000", to preserve decimal precision.

Nullability and collections

Nullable fields are present with null when no value is available. Arrays are present as empty arrays when no values exist. Do not assume an email, phone, owner, due date, product relationship, or PDF is always present.

Response envelopes

Single resources:

{
  "data": { "id": "44cfbbd5-185d-4c9d-8597-588c25e574e8", "object": "product" },
  "request_id": "req_docsresponse01"
}

Collections:

{
  "data": [],
  "page": { "has_more": false, "next_cursor": null },
  "request_id": "req_docsresponse02"
}

Errors:

{
  "error": {
    "type": "invalid_request_error",
    "code": "invalid_filter",
    "message": "One or more request parameters are invalid."
  },
  "request_id": "req_docsresponse03"
}

Request IDs

Daily returns request_id in JSON and X-Request-ID at the HTTP edge. You may supply X-Request-ID using 8–100 ASCII letters, numbers, underscores, or hyphens. Invalid values and values resembling a Daily key are replaced. Record the ID beside your own trace ID, but never attach the Authorization header when contacting support.

Caching and compatibility

Authenticated responses use private no-store/no-cache headers. Do not put them in shared caches. Clients should ignore new object fields to remain forward-compatible; existing documented fields will not be repurposed within v1 without a breaking-version decision.