forked from akamai/akamai-apis
-
Notifications
You must be signed in to change notification settings - Fork 0
/
delete.yaml
199 lines (199 loc) · 6.46 KB
/
delete.yaml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
openapi: 3.0.0
info:
title: Deletions
version: '1'
license:
name: Apache 2.0
url: https://www.apache.org/licenses/LICENSE-2.0.html
servers:
- url: https://{hostname}/ccu/v3
x-akamai:
auth-type: EDGE_GRID
file-path: delete.yaml
paths:
/delete/cpcode/{network}:
parameters:
- $ref: parameters/network-path.yaml
post:
operationId: post-delete-cpcode
summary: Delete by CP code
tags:
- CP code
description: |
Deletes content on the selected CP code for the selected `network`. In most cases, you should [invalidate](ref:invalidate-cpcode) rather than delete content. Invalidation keeps each object in cache until the version on your origin server is newer. Deletion retrieves the object regardless, which can dramatically increase the load on your origin server and would prevent Akamai from serving the old content if your origin is unreachable.
requestBody:
required: true
content:
application/json:
example:
$ref: examples/post-cpcode.json
schema:
$ref: schemas/post-cpcode.yaml
responses:
201:
description: |
Successful POST of a purge request.
content:
application/json:
example:
$ref: examples/201.json
schema:
$ref: schemas/response.yaml
400:
description: |
Bad request.
content:
application/problem+json:
schema:
$ref: schemas/response.yaml
403:
description: |
Forbidden request.
content:
application/problem+json:
example:
$ref: examples/403.json
schema:
$ref: schemas/response.yaml
429:
description: |
Too many requests.
content:
application/json:
example:
$ref: examples/cpcode-429.json
schema:
$ref: schemas/response.yaml
500:
description: |
Internal server error.
content:
application/json:
example:
$ref: examples/500.json
schema:
$ref: schemas/response.yaml
/delete/tag/{network}:
parameters:
- $ref: parameters/network-path.yaml
post:
operationId: post-delete-tag
summary: Delete by cache tag
tags:
- Cache tag
description: |
Deletes content on the selected set of cache tags for the selected `network`. In most cases, you should [invalidate](ref:invalidate-tag) rather than delete content. Invalidation keeps each object in cache until the version on your origin server is newer. Deletion retrieves the object regardless, which can dramatically increase the load on your origin server and would prevent Akamai from serving the old content if your origin is unreachable.
requestBody:
required: true
content:
application/json:
example:
$ref: examples/post-tag.json
schema:
$ref: schemas/post-tag.yaml
responses:
201:
description: |
Successful POST of a purge request.
content:
application/json:
example:
$ref: examples/201.json
schema:
$ref: schemas/response.yaml
400:
description: |
Bad request.
content:
application/problem+json:
schema:
$ref: schemas/response.yaml
403:
description: |
Forbidden request.
content:
application/problem+json:
example:
$ref: examples/403.json
schema:
$ref: schemas/response.yaml
429:
description: |
Too many requests.
content:
application/json:
example:
$ref: examples/tag-429.json
schema:
$ref: schemas/response.yaml
500:
description: |
Internal server error.
content:
application/json:
example:
$ref: examples/500.json
schema:
$ref: schemas/response.yaml
/delete/url/{network}:
parameters:
- $ref: parameters/network-path.yaml
post:
operationId: post-delete-url
summary: Delete by URL or ARL
tags:
- URL/ARL
description: |
Deletes content on the selected URL or ARL for the selected `network`. URLs and ARLs can be submitted in the same request. In most cases, you should [invalidate](ref:invalidate-url) rather than delete content. Invalidation keeps each object in cache until the version on your origin server is newer. Deletion retrieves the object regardless, which can dramatically increase the load on your origin server and would prevent Akamai from serving the old content if your origin is unreachable.
requestBody:
required: true
content:
application/json:
example:
$ref: examples/post-url.json
schema:
$ref: schemas/post-url.yaml
responses:
201:
description: |
Successful POST of a purge request.
content:
application/json:
example:
$ref: examples/201.json
schema:
$ref: schemas/response.yaml
400:
description: |
Bad request.
content:
application/problem+json:
schema:
$ref: schemas/response.yaml
403:
description: |
Forbidden request.
content:
application/problem+json:
example:
$ref: examples/403.json
schema:
$ref: schemas/response.yaml
429:
description: |
Too many requests.
content:
application/json:
example:
$ref: examples/url-429.json
schema:
$ref: schemas/response.yaml
500:
description: |
Internal server error.
content:
application/json:
example:
$ref: examples/500.json
schema:
$ref: schemas/response.yaml