- /api/core/sites
- /api/core/communities
- /api/core/collections
- /api/core/items
- /api/core/itemtemplates
- /api/core/bitstreams
- /api/core/bitstreamformats
- /api/core/bundles
- /api/core/sites
- /api/core/metadatafields
- /api/core/metadataschemas
- /api/core/epersons
- /api/core/groups
- /api/core/{model}/search
- /api/authn/login
- /api/authn/logout
- /api/authn/status
- /api/config/harvestermetadata
- /api/config/submissiondefinitions
- /api/config/submissionsections
- /api/config/submissionforms
- /api/config/submissionuploads
- /api/config/workflowdefinitions
- /api/config/workflowsteps
- /api/discover/browses
- /api/discover/search
- /api/submission/workspaceitems
- /api/submission/vocabularies
- /api/submission/vocabularyEntryDetails
- /api/versioning/version
- /api/versioning/versionhistory
- /api/workflow/workflowitems
- /api/workflow/pooltasks
- /api/workflow/claimedtasks
- /api/authz/resourcepolicies
- /api/authz/authorizations
- /api/authz/features
- /api/statistics
- /api/tools/itemrequests
- /api/authorize/(dso)
- /api/curate
- /api/export
- /api/app/bulkmetadataedit
- /api/statistics/(dso)
- /api/configuration
- return relevant configuration values to the client
- DSpace version
- Root url
- Site name
- Contact info
- Root handle
- Supported themes
- Default language
- Languages supported
- question, how will we mark / designate the values that are safe to expose?
- return relevant configuration values to the client
- /api/feature
- return the status of features that are enabled for a site
- statistics viewing
- return the status of features that are enabled for authorized users
- item versioning
- return the status of features that are enabled for a site