Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • D digitec-wiki
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Digitec
  • digitec-wiki
  • Wiki
  • rest api standards

rest api standards · Changes

Page history
rcabral created page: gitlab administration authored Jan 30, 2015 by Rene Cabral's avatar Rene Cabral
Hide whitespace changes
Inline Side-by-side
rest-api-standards.markdown
View page @ 957fb7bd
......@@ -10,4 +10,32 @@
- Extra properties can be requested using the following notation: `resource-endpoint:(extra-property1, extra-property2)`
- Extra properties can be sub-collections, relationships etc of the main resource.
- Updating or creating an entity should return the entity if discreet (i.e. tagging an asset will not return the tag or the asset but creating a tag will return the tag).
\ No newline at end of file
- Updating or creating an entity should return the entity if discreet (i.e. tagging an asset will not return the tag or the asset but creating a tag will return the tag).
| HTTP | Route | Action |
| -------- | ---------------------- | ------------------------- |
|`POST` | '/permissions` | create resource, optional permission id for parent in payload|
|`GET` | '/permissions` | get resource collection|
|`GET` | '/permissions?role=:id` | get resource collection for role|
|`GET` | '/permissions/:id` | get single resource|
|`DELETE`| '/permissions/:id` | delete single resource|
|`DELETE`| '/permissions/:id?recursive=:boolean` | delete single resource|
|`PATCH` | '/permissions/:id` | update resource|
|`POST` | '/permissions/:id/link` | link permission to specified role(s), payload []|
|`POST` | '/permissions/:id/unlink` | unlink permission to specified role(s), payload []|
|
| HTTP | Route | Action |
| -------- | ---------------------- | ------------------------- |
| `GET` | `/resources` | View all resources |
| `GET` | `/resources/{id}` | View single resource |
| `GET` | `/resources/new` | View create resource form |
| `POST` | `/resources` | Store new resource |
| `GET` | `/resources/{id}/edit` | View edit resource form |
| `PUT` | `/resources/{id}` | Update resource |
| `PATCH` | `/resources/{id}` | Update resource |
| `DELETE` | `/resources/{id}` | Delete resource |
Clone repository
  • alpha beta testing
  • browser testing
  • camtasia licenses
  • code delivery processes
  • coding practices
  • css and sass coding standards
  • database schema standards
  • dependency management
  • development environments
  • digitec agile process
  • digitec gitlab styles
  • digitec software promises
  • digitec spec process
  • gitlab administration
  • gitlab issues tags
View All Pages