Currents Attachments API

The Attachments API from Currents — 2 operation(s) for attachments.

GitHub OpenAPI

Operations 2

GET /{slug}/attachments Files embedded in the trace #
GET /{slug}/attachments/{id} One attachment's bytes #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/currents-dev:currents-dev-attachments-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

currents-dev-attachments-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Currents trace Attachments API
  version: '1'
  description: On-demand access to Playwright trace contents (screencast frames, trace summary, DOM snapshots, network requests, attachments) via ranged zip reads. Human-readable docs at /docs.
servers:
- url: https://t.crts.sh
tags:
- name: Attachments
paths:
  /{slug}/attachments:
    get:
      summary: Files embedded in the trace
      description: Lists attachments recorded inside the trace (test.attach output, Playwright's error-context, screenshots, and from Playwright 1.63 the video) with name, contentType, and sha1. An attachment the runner left on disk without copying it into the zip is not served.
      parameters:
      - name: slug
        in: path
        required: true
        description: Link slug minted by the Currents backend; grants read access to one trace until the link expires.
        schema:
          type: string
          pattern: ^[A-Za-z0-9_-]{16}$
      - name: name
        in: query
        required: false
        description: substring filter on the attachment name
        schema:
          type: string
      responses:
        '200':
          description: Files embedded in the trace (application/json)
        '400':
          description: invalid parameters
        '404':
          description: unknown or expired link, or not found in this trace
        '413':
          description: the trace is larger than the worker can read
        '422':
          description: the trace artifact is not a readable zip
        '502':
          description: the trace could not be fetched from storage
        '503':
          description: this deployment has no link bucket bound, so no link can be read
      tags:
      - Attachments
      operationId: getBySlugAttachments
      x-operation-id-source: derived
  /{slug}/attachments/{id}:
    get:
      summary: One attachment's bytes
      description: '{id} is a sha1 content hash (from the attachments list or the trace summary) or an attachment name; by name, last match wins, since names repeat across retries. Served with the attachment''s own content type. Playwright''s error-context failure summary lives at ./attachments/error-context.'
      parameters:
      - name: slug
        in: path
        required: true
        description: Link slug minted by the Currents backend; grants read access to one trace until the link expires.
        schema:
          type: string
          pattern: ^[A-Za-z0-9_-]{16}$
      - name: id
        in: path
        required: true
        description: Snapshot name or timestamp; for attachments, a sha1 content hash or an attachment name.
        schema:
          type: string
      responses:
        '200':
          description: One attachment's bytes (attachment contentType)
        '400':
          description: invalid parameters
        '404':
          description: unknown or expired link, or not found in this trace
        '413':
          description: the trace is larger than the worker can read
        '422':
          description: the trace artifact is not a readable zip
        '502':
          description: the trace could not be fetched from storage
        '503':
          description: this deployment has no link bucket bound, so no link can be read
      tags:
      - Attachments
      operationId: getBySlugAttachmentsById
      x-operation-id-source: derived
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer