Skip to content

Commit 537dc63

Browse files
docs(api): Use correct HTTP method for specific issue
1 parent dc4c803 commit 537dc63

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

develop-docs/backend/api/design.mdx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -124,19 +124,19 @@ Resources can get complicated when you need to expose batch operations vs single
124124
Let's say for example we have an endpoint that mutates an issue:
125125

126126
```
127-
POST /api/0/organizations/{org}/issues/{issue}/
127+
PUT /api/0/organizations/{org}/issues/{issue}/
128128
```
129129

130130
When designing a batch interface, we simply expose it on the collection instead of the individual resource:
131131

132132
```
133-
POST /api/0/organizations/{org}/issues/
133+
PUT /api/0/organizations/{org}/issues/
134134
```
135135

136136
You may also need to expose selectors on batch resources, which can be done through normal request parameters:
137137

138138
```
139-
POST /api/0/organizations/{org}/issues/
139+
PUT /api/0/organizations/{org}/issues/
140140
{
141141
"issues": [1, 2, 3]
142142
}

0 commit comments

Comments
 (0)