Help and support

Create a group, add its members, then choose the group and attendance date. Mark each person present or not marked. The daily totals update as you work, and you can search the member list to find a person quickly.

The core attendance tools work offline without signing in. Return to a saved group and date to review or change its marks. After adding members, choose Prepare date again for the selected day. This adds the new members while keeping marks that are already saved.

Use Export CSV to create an attendance report, then choose an Android app or storage destination to save or share it. The file can be opened in spreadsheet software. Verify the chosen group, dates and destination before sharing a roster.

If a file opens with the wrong characters, import it as UTF-8 in your spreadsheet application. Keep exported copies somewhere you control if you need them after clearing or removing the app.

Open API setup and enter the final HTTPS endpoint supplied by your system administrator. The URL may include noncredential routing query parameters, but must not contain an embedded username, password or fragment. If required, enter a bearer token in its separate field. Saved tokens are encrypted with a key held in Android Keystore.

Test connection sends an OPTIONS request and the saved token, if configured, to that endpoint. It does not send attendance. A server that does not support OPTIONS may report that it was reached without passing this test.

Choose a group and saved day, review the displayed destination and records, then confirm Send to API. The app makes a JSON POST. The receiving application must support this format; an arbitrary website or API that expects a different format will need an adapter.

Each request contains schemaVersion (1), event (attendance_export), a generated requestId, group, date (YYYY-MM-DD), and records. Each record contains member (the name) and present (true for Present or false for Not marked). The request also includes an Idempotency-Key header and, when configured, an Authorization: Bearer header.

Example: {"schemaVersion": 1, "event": "attendance_export", "requestId": "example-request", "group": "Example group", "date": "2026-10-25", "records": [{"member": "Example member", "present": true}]}

Check the destination, network connection, server certificate, authentication and the server’s expected format. Redirects are not followed; enter the final HTTPS URL instead. The app displays the HTTP status and a limited response so you can review the result.

A timeout or interrupted connection can leave delivery uncertain. Check the receiving application before sending again, because a new manual send is a new request. A successful HTTP response confirms that the server accepted the request; check its response for the application’s own result.

Deleting a member or group removes its related attendance history in the app. Clearing app data or uninstalling removes the local database and saved settings. Export the records you need first. Clear API configuration from API setup if you no longer want to keep the endpoint or token.

Files already exported and records already received by another application are separate copies. Delete those files or ask the recipient to remove its copies as appropriate.

The Android app uses Google AdMob and UMP. When applicable, use Privacy choices in the app to revisit your advertising choices. Read the app Privacy Policy for information about local attendance, optional API requests and advertising data.

We can help with app errors and explain the integration format. Your receiving system’s administrator can help with its endpoint, token and record-retention policy.

Email: greenmob2014@gmail.com