TEteaflask
authed

Upload Org Action Specs

Upload API spec files — OpenAPI 3 or Swagger 2.0 as JSON or YAML, or GraphQL operations (.graphql files) with the schema they are checked against (SDL files or one introspection result) and graphql_endpoint, the path on your API every operation is sent to — several files that reference each other, or a zip of them. Each upload adds to the catalog and is scanned like a repository: proposals land in the review inbox, never directly in the catalog. An upload never proposes removing an action; archive the ones you no longer want.

post/api/v1/org-actions/spec-uploads

Request

  • Base URL
    https://api.teaflask.com (the document declares no server; this is the origin it was published from)
  • URL
    https://api.teaflask.com/api/v1/org-actions/spec-uploads
  • Auth
    none declared

Request body multipart/form-data

filesstring[] required
graphql_endpointstring nullable

Response

Successful Response

idstring uuid required
organization_idstring uuid required
status'queued' | 'working' | 'succeeded' | 'failed' | 'unfunded' required
errorstring nullable required
requested_by_user_idstring uuid nullable required
trigger'manual' | 'push' | 'upload' required

What started the scan: manual (a member scanned the connected repositories), push (a push to a default branch) or upload (a member uploaded spec files).

finished_atstring date-time nullable required
created_atstring date-time required
updated_atstring date-time required
replaced_a_waiting_uploadboolean

Changes

No recorded changes to this operation across all 1 revision of this API.