Projects on Open Humans can remove project members from their project. Removals are performed based on project member ID. Removal is an irreversible action that deauthorizes the member, removing any continued access to data shared by the member and/or added to their account by the project.
Removals will not remove data deposited by the project. If a project wishes to remove data it added to a member account, it must do so before removing the member.
Removal does not prevent a member from re-joining a project.
Note: If you plan to message members to inform them of their removal, you must do so before removing them. You will be unable to message them after the removal, as they will no longer be members.
Go to your project management page.
Go to the project detail page by clicking the project name.
Click the "Remove project members" button for your project.
Specify which members you're removing. Use a comma-separated list of project member IDs.
Remove members. Click "Remove members" to remove the project member(s) you've specified.
You can use a master access token with POST to the member removal endpoint to remove a specified subset of project members.
The endpoint takes these parameters as a JSON object:
project_member_ids: An array of project member IDs to remove.
You must either specify
or specify an array of
project_member_ids but not both.
The URL for the messaging endpoint is:
Each project has a "master access token" used for API calls. This token is a password for your project.
To find the token, your project management page and click on your project's name. The master access token should be listed in your project's details.
Keep this token PRIVATE.
This token is used to authorize the following:
If you ever believe the security of this token may have been compromised, contact us at email@example.com and we'll reset it to a new value.
When using this token in programs, we recommend you do NOT store it. You should enter the token each time you run your software.
If you want to have fully automated API transactions with Open Humans, you should use OAuth2 endpoints with user-specific access tokens.