@@ -76,11 +76,10 @@ sourcemaps) within Sentry. This removes the requirement for them to be
76
76
web-accessible, and also removes any inconsistency that could come from
77
77
network flakiness (on either your end, or Sentry's end).
78
78
79
- * Start by creating a new API key under your organization's API Keys nav
80
- (on the home).
79
+ * Start by creating a new authentication token under **[Account] > API **.
81
80
* Ensure you you have ``project:write `` selected under scopes.
82
- * You'll use HTTP basic auth with the api key being your username, and an
83
- empty value for the password .
81
+ * You'll use the Authorization header with the value of `` Bearer: {TOKEN} ``
82
+ with API requests .
84
83
85
84
Now you need to setup your build system to create a release, and attach
86
85
the various source files. You will want to upload all dist files (i.e. the
@@ -91,10 +90,10 @@ sourcemaps point to.
91
90
92
91
# Create a new release
93
92
$ curl https://app.getsentry.com/api/0/projects/:organization_slug/:project_slug/releases/ \
94
- -u [api_key]: \
95
93
-X POST \
96
- -d ' {"version": "2da95dfb052f477380608d59d32b4ab9" }' \
94
+ -H ' Authorization: Bearer {TOKEN }' \
97
95
-H ' Content-Type: application/json'
96
+ -d ' {"version": "2da95dfb052f477380608d59d32b4ab9"}' \
98
97
99
98
{
100
99
" dateCreated" : " 2015-03-06T04:51:32.723Z" ,
@@ -112,8 +111,8 @@ reference to ``app.map.js``, the name of the uploaded file should be ``http://ex
112
111
113
112
# Upload a file for the given release
114
113
$ curl https://app.getsentry.com/api/0/projects/:organization_slug/:project_slug/releases/2da95dfb052f477380608d59d32b4ab9/files/ \
115
- -u [api_key]: \
116
114
-X POST \
115
+ -H ' Authorization: Bearer {TOKEN}' \
117
116
118
117
-F name=" http://example.com/app.js.map"
119
118
@@ -132,7 +131,7 @@ reference to ``app.map.js``, the name of the uploaded file should be ``http://ex
132
131
133
132
# If you make a mistake, you can also simply clear out the release
134
133
$ curl https://app.getsentry.com/api/0/projects/:organization_slug/:project_slug/releases/2da95dfb052f477380608d59d32b4ab9/ \
135
- -u [api_key]: \
134
+ -H ' Authorization: Bearer {TOKEN} ' \
136
135
-X DELETE
137
136
138
137
Additionally, you'll need to configure the client to send the ``release ``:
0 commit comments