1. List credentials
When the user clicks the "My Collectors" button in your app, he should see:
- A list of all their configured credentials.
- The current status of each collector (active, error, needs authentication, etc...).
- Basic information about each collector (supplier name, account identifier).
- Options to manage their credentials (view, re-connect and delete).
Here is an example of what the table displayed on your frontend could look like:
| Supplier | Status | Creation date | Last Collect | Next Collect | Documents collected | Actions |
|---|---|---|---|---|---|---|
| Amazon Business | Active | 2025-10-01 | 2025-11-14 | 2025-11-16 | 46 | Delete |
| Google Workspace | In Progress | 2025-12-15 | - | 2025-12-15 | 0 | |
| Office Depot | Error - Wrong password | 2025-11-05 | 2025-11-05 | - | 0 | Delete |
| OpenAI | Disconnected | 2025-08-21 | 2025-10-30 | - | 21 |
Implementation
| Step | Side | Description |
|---|---|---|
| 1 | Frontend | User clicks on the My Collectors button. |
| 2 | Backend | Upsert the user in our database using the POST /user endpoint and get the user id |
| 3 | Backend | Use the user id to get the users credentials with the endpoint GET /user/{user_id}/credentials. |
| 4 | Frontend | Render the credentials on your frontend in a nice table. See recommended table above. |
Display actions depending on the collector state
When getting the credentials with the endpoint GET /user/{user_id}/credentials,
you will see that each credential has a field called state. Actions displayed in the table depends on the state.index value.
See Credential state for more infos.