Skip to content
GitLab
Next
Menu
Why GitLab
Pricing
Contact Sales
Explore
Why GitLab
Pricing
Contact Sales
Explore
Sign in
Get free trial
Primary navigation
Search or go to…
Project
GitLab
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Iterations
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Package registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Privacy statement
Keyboard shortcuts
?
What's new
4
Snippets
Groups
Projects
Show more breadcrumbs
GitLab.org
GitLab
Commits
b456e909
Commit
b456e909
authored
2 years ago
by
Cleveland Bledsoe Jr
Committed by
Kati Paizee
2 years ago
Browse files
Options
Downloads
Patches
Plain Diff
Add 202 Accepted to table
parent
8091c3f3
No related branches found
No related tags found
1 merge request
!89177
Add 202 Accepted to table
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
doc/api/index.md
+2
-1
2 additions, 1 deletion
doc/api/index.md
with
2 additions
and
1 deletion
doc/api/index.md
+
2
−
1
View file @
b456e909
...
...
@@ -342,13 +342,14 @@ The following table gives an overview of how the API functions generally behave.
|
`GET`
| Access one or more resources and return the result as JSON. |
|
`POST`
| Return
`201 Created`
if the resource is successfully created and return the newly created resource as JSON. |
|
`GET`
/
`PUT`
| Return
`200 OK`
if the resource is accessed or modified successfully. The (modified) result is returned as JSON. |
|
`DELETE`
| Returns
`204 No Content`
if the resource was deleted successfully. |
|
`DELETE`
| Returns
`204 No Content`
if the resource was deleted successfully
or
`202 Accepted`
if the resource is scheduled to be deleted
. |
The following table shows the possible return codes for API requests.
| Return values | Description |
|--------------------------|-------------|
|
`200 OK`
| The
`GET`
,
`PUT`
or
`DELETE`
request was successful, and the resource itself is returned as JSON. |
|
`202 Accepted`
| The
`GET`
,
`PUT`
or
`DELETE`
request was successful, and the resource is scheduled for processing. |
|
`204 No Content`
| The server has successfully fulfilled the request, and there is no additional content to send in the response payload body. |
|
`201 Created`
| The
`POST`
request was successful, and the resource is returned as JSON. |
|
`304 Not Modified`
| The resource hasn't been modified since the last request. |
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment