TheDude
/
openproject
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
OpenProject is the leading open source project management software.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
34997 Commits
139 Branches
203 Tags
1.2 GiB
Tag: Branch: Tree: e3903a70e6
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'e3903a70e6'
${ noResults }
openproject/docs/api/apiv3-documentation.apib

38 lines
1.5 KiB
Raw Normal View History Unescape

Transferring blueprint from apiary.io
11 years ago
FORMAT: 1A
Transferring blueprint from apiary.io
11 years ago
# OpenProject API v3
Transferring blueprint from apiary.io
11 years ago
Extract APIV3 documentation into single endpoints This does not differentiate further inside an endpoint and while useful (for e.g., work packages) we should discuss how the structure inside an endpoint should look like.
8 years ago
<!-- include(apiv3/introduction.apib) -->
<!-- include(apiv3/basic-objects.apib) -->
<!-- include(apiv3/group-objects.apib) -->
<!-- include(apiv3/endpoints/activities.apib) -->
<!-- include(apiv3/endpoints/attachments.apib) -->
<!-- include(apiv3/endpoints/categories.apib) -->
<!-- include(apiv3/endpoints/configuration.apib) -->
add description on custom action * turn custom action into fully fledged resource * add description to custom action model * load custom action resource on mouse over and display in title
7 years ago
<!-- include(apiv3/endpoints/custom-actions.apib) -->
replace string object by custom option for list custom fields
8 years ago
<!-- include(apiv3/endpoints/custom-options.apib) -->
Extract APIV3 documentation into single endpoints This does not differentiate further inside an endpoint and while useful (for e.g., work packages) we should discuss how the structure inside an endpoint should look like.
8 years ago
<!-- include(apiv3/endpoints/forms.apib) -->
introduce group resource stub
7 years ago
<!-- include(apiv3/endpoints/groups.apib) -->
Create /help_texts endpoint
7 years ago
<!-- include(apiv3/endpoints/help_texts.apib) -->
document added resources
7 years ago
<!-- include(apiv3/endpoints/posts.apib) -->
adding filter instance schemas
8 years ago
<!-- include(apiv3/endpoints/principals.apib) -->
Extract APIV3 documentation into single endpoints This does not differentiate further inside an endpoint and while useful (for e.g., work packages) we should discuss how the structure inside an endpoint should look like.
8 years ago
<!-- include(apiv3/endpoints/priorities.apib) -->
<!-- include(apiv3/endpoints/projects.apib) -->
<!-- include(apiv3/endpoints/queries.apib) -->
<!-- include(apiv3/endpoints/relations.apib) -->
<!-- include(apiv3/endpoints/render.apib) -->
<!-- include(apiv3/endpoints/revisions.apib) -->
adding filter instance schemas
8 years ago
<!-- include(apiv3/endpoints/roles.apib) -->
Extract APIV3 documentation into single endpoints This does not differentiate further inside an endpoint and while useful (for e.g., work packages) we should discuss how the structure inside an endpoint should look like.
8 years ago
<!-- include(apiv3/endpoints/root.apib) -->
<!-- include(apiv3/endpoints/schemas.apib) -->
<!-- include(apiv3/endpoints/statuses.apib) -->
<!-- include(apiv3/endpoints/string-objects.apib) -->
read operations for time_entries via api v3 (#5776) * read operations for time_entries via api v3 Introduces the endpoints: * GET /api/v3/time_entries * GET /api/v3/time_entries/:id * GET /api/v3/time_entries/activities/:id The index action for time entries can be queried by the following filters: * project_id * user_id * work_package_id The implementation is exposing the database structure mostly one to one with the exception of some renaming and the hiding of the activities' complexity, where only the activity used systemwide is referenced regardless of whether a project specific override exists or not. * allow custom values for time entries [ci skip]
7 years ago
<!-- include(apiv3/endpoints/time_entries.apib) -->
Extract APIV3 documentation into single endpoints This does not differentiate further inside an endpoint and while useful (for e.g., work packages) we should discuss how the structure inside an endpoint should look like.
8 years ago
<!-- include(apiv3/endpoints/types.apib) -->
<!-- include(apiv3/endpoints/user-preferences.apib) -->
<!-- include(apiv3/endpoints/users.apib) -->
<!-- include(apiv3/endpoints/versions.apib) -->
document added resources
7 years ago
<!-- include(apiv3/endpoints/wiki_pages.apib) -->
Extract APIV3 documentation into single endpoints This does not differentiate further inside an endpoint and while useful (for e.g., work packages) we should discuss how the structure inside an endpoint should look like.
8 years ago
<!-- include(apiv3/endpoints/work-packages.apib) -->