Owner reporting API
A read-only API for an authorized service owner to connect aggregate signup counts to a reporting tool. It returns registered account totals and daily counts, with verified guest-only identities counted separately.
Authorized reporting access
The service owner issues a dedicated reporting key. Send it in the Authorization header as a Bearer token. The key reads aggregate reports only; it does not grant access to documents, form jobs, account sessions or payments. Ordinary Form Filler accounts do not grant organization-wide reporting access.
For customer form processing, use the Form Filler API and create a key in My account. Reporting uses its own owner-issued credential.
Read signup counts
curl --get 'https://aideify.com/api/v1/reports/signups' -H "Authorization: Bearer $AIDEIFY_REPORTING_KEY" --data-urlencode 'timezone=America/New_York'Optional from and to dates use YYYY-MM-DD and include both endpoints. The default is today and the preceding 29 days. The maximum is 90 days. Supply an IANA timezone; future dates are rejected.
What the counts mean
external excludes the owner's configured internal email list; all includes it. Both contain an all-time retained account total, a daily series and the number of older accounts whose registration time is unavailable. Excluding known internal identities does not prove that every remaining identity is a distinct person or paying customer.
verifiedGuestOnly counts verified email identities that have not registered an account. A guest who later registers counts as one registered account, not an additional person. Daily registration tracking starts at coverage.trackingStartedAt. Earlier unavailable days return null. The first tracked day and the current day are partial. Older accounts remain in totals; their signup dates are not invented.
Limits and failures
Reporting is unmetered and limited to 60 authenticated requests per minute per application process. Honor Retry-After on HTTP 429. HTTP 401 means a missing or invalid key; 400 means invalid query input; 503 means configuration or source unavailability. Retain the last successful report with its timestamp when a refresh fails. Responses are private and must not be publicly cached.