Picomes Uploads API

The Uploads API from Picomes — 2 operation(s) for uploads.

Operations 2

POST /uploads POST /uploads #
PATCH /uploads/{id} Media Upload API #

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/picomes:picomes-uploads-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

picomes-uploads-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Picomes Uploads API
  version: '2026-10-12'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-12: 5 operation(s) read from 4 public documentation page(s) (each operation names its page in x-source). This is not the provider''s published contract; Picomes has published no machine-readable contract that the pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 4
    documentation: 1
    pages-with-code: 4
    pages-read: 4
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-12'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://apidocs.picomes.com/guides/media-upload-api
  - https://apidocs.picomes.com/guides/work-instructions-api
  - https://apidocs.picomes.com/guides/erp_example_calls
  - https://apidocs.picomes.com/guides/authentication
servers:
- url: https://your-erp-system.com
security:
- x-pico-api-org: []
tags:
- name: Uploads
paths:
  /uploads:
    post:
      operationId: post_uploads
      tags:
      - Uploads
      summary: POST /uploads
      x-source: https://apidocs.picomes.com/guides/media-upload-api
      responses:
        '201':
          description: Success (shape read from the example response on the page)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PostUploadsResponse'
      x-evidence:
        kind: code-example
        language: curl
        snippet: "curl -X POST https://example.picomes.io/uploads \\ -H \"x-pico-api-org: YOUR_API_TOKEN\" \\ -F \"destinationId=stepImage\" \\ -F \"file=@/path/to/image.jpg\" \n Python Example ​ \n import json import urllib . request import os UPLOAD_ENDPOINT = \"https://example.picomes.io/uploads\" API_TOKEN = \"YOUR_API_TOKEN\" def upload_image ( file_path , destination_id = \"stepImage\" ) : \"\"\"Upload an image and return the re"
  /uploads/{id}:
    patch:
      operationId: patch_uploads_id
      tags:
      - Uploads
      summary: Media Upload API
      description: Send chunk to existing stream
      x-source: https://apidocs.picomes.com/guides/media-upload-api
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PatchUploadsIdRequest'
      responses:
        '200':
          description: Success (status as documented)
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/PatchUploadsIdResponse'
      x-evidence:
        kind: documentation
components:
  schemas:
    PatchUploadsIdRequest:
      type: object
      properties:
        chunkIndex:
          type: integer
          description: Zero‑based index of the chunk being sent
        totalChunks:
          type: integer
          description: Total number of chunks for the upload
        file:
          type: string
          description: Chunk binary data
      required:
      - chunkIndex
      - totalChunks
      - file
    PostUploadsResponse:
      type: object
      properties:
        streamId:
          type: string
    PatchUploadsIdResponse:
      type: object
      properties:
        streamId:
          type: string
          description: Identifier of the upload stream
        chunkIndex:
          type: integer
          description: Index of the chunk that was just received
        path:
          type: string
          description: Path to the uploaded media (present in final chunk response)
  securitySchemes:
    x-pico-api-org:
      type: apiKey
      in: header
      name: x-pico-api-org
      x-source: https://apidocs.picomes.com/guides/authentication/index.html