POST /v8/artifacts/events
Records an artifacts cache usage event. The body of this request is an array of cache usage events. The supported event types are HIT
and MISS
. The source is either LOCAL
the cache event was on the users filesystem cache or REMOTE
if the cache event is for a remote cache. When the event is a HIT
the request also accepts a number duration
which is the time taken to generate the artifact in the cache.
Servers
- https://api.vercel.com
Request headers
Name | Type | Required | Description |
---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
x-artifact-client-ci |
String | No |
The continuous integration or delivery environment where this artifact is downloaded. |
x-artifact-client-interactive |
Integer | No |
1 if the client is an interactive shell. Otherwise 0 |
Query parameters
Name | Type | Required | Description |
---|---|---|---|
teamId |
String | No |
The Team identifier to perform the request on behalf of. |
slug |
String | No |
The Team slug to perform the request on behalf of. |
Request body fields
Name | Type | Required | Description |
---|---|---|---|
[] |
Array | Yes | |
[].source |
String | Yes |
One of Possible values:
|
[].hash |
String | Yes |
The artifact hash |
[].event |
String | Yes |
One of Possible values:
|
[].sessionId |
String | Yes |
A UUID (universally unique identifer) for the session that generated this event. |
[].duration |
Number | No |
The time taken to generate the artifact. This should be sent as a body parameter on |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.