DailyAPI Documentationv1

Filtering and sorting

Use only the filters and deterministic sort orders implemented by each Daily resource.

View OpenAPI

Collection endpoints accept a defined subset of these parameters. Unknown parameters, unsupported combinations, invalid status values, and oversized values return 400 invalid_filter.

Common parameters

ParameterFormatDefault / constraintSemantics
limitintegerDefault 50; minimum 1; maximum 100Maximum objects in this page.
cursorstringMaximum 512 charactersOpaque cursor from the same collection.
created_afterstrict ISO 8601 timestampOptionalCreation time strictly greater than the value.
updated_afterstrict ISO 8601 timestampOptional except inventory movementsUpdate time strictly greater than the value.
statusresource enumMaximum raw length 50Exact public status, case-insensitive.
searchstringTrimmed; maximum 100 charactersCase-insensitive search over documented fields.

Resource matrix

ResourceStatus valuesSearch fieldsTime filtersSort order
Customersactive, inactivename, business number, email, contact personcreated, updatedupdated_at desc, ID desc
Suppliersactive, inactivename, business number, email, contact personcreated, updatedupdated_at desc, ID desc
Leadsnew, contacted, in_progress, proposal, negotiation, won, lostname, contact name, email, phonecreated, updatedupdated_at desc, ID desc
Productsactive, inactivename, SKU, barcodecreated, updatedupdated_at desc, ID desc
Documentsopen, converted, pending_payment, closed, credited, returned, partially_paid, partially_credited, partially_returnedtitle, customer-name snapshotcreated, updatedupdated_at desc, ID desc
PaymentsrecordedNot supportedcreated, updatedupdated_at desc, ID desc
Inventory levelsactive, inactiveproduct namecreated, updatedupdated_at desc, ID desc
Inventory movementsincrease, decreaseNot supportedcreated onlycreated_at desc, ID desc
Tasksopen, completed, canceledtask titlecreated, updatedupdated_at desc, ID desc

The business endpoint and single-resource endpoints accept no query parameters.

Combining filters

Filters are combined with logical AND. Search matches any of the listed search fields; time and status constraints still apply.

set -euo pipefail
: "${DAILY_API_KEY:?DAILY_API_KEY is required}"

curl --fail-with-body --silent --show-error \
  --get 'https://api.godaily.co.il/v1/documents' \
  --header "Authorization: Bearer ${DAILY_API_KEY}" \
  --header 'Accept: application/json' \
  --data-urlencode 'status=pending_payment' \
  --data-urlencode 'updated_after=2026-07-01T00:00:00.000Z' \
  --data-urlencode 'search=Orion' \
  --data-urlencode 'limit=100'

Incremental retrieval

Resources with updated_after support incremental reads. Store a UTC high-water timestamp taken before the traversal, request updated_after with overlap, fully paginate, and upsert by ID. The filter is exclusive, so overlap protects against clock and boundary mistakes; idempotent upserts remove duplicates.

Inventory movements have no update timestamp and reject updated_after. Increment them using created_after, understanding that it tracks creation only. If your correctness model must detect historical change outside that contract, perform periodic full pagination.

On this page