Bynder Step 2 API
This endpoint uploads a chunk of the file. You need to provide the file ID obtained from the prepare upload step and the chunk number (starting from 0). The request body should contain the binary data of the chunk being uploaded.
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.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/bynder-step-2-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
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
openapi: 3.2.0
info:
title: Modern Stack File Upload Step 2 API
version: 1.0.0
description: This endpoint uploads a chunk of the file. You need to provide the file ID obtained from the prepare upload step and the chunk number (starting from 0). The request body should contain the binary data of the chunk being uploaded.
servers:
- url: https://{your-bynder-domain}/
variables:
your-bynder-domain:
default: example.com
description: Your Bynder domain.
tags:
- name: Step 2
description: This endpoint uploads a chunk of the file. You need to provide the file ID obtained from the prepare upload step and the chunk number (starting from 0). The request body should contain the binary data of the chunk being uploaded.
paths:
/v7/file_cmds/upload/{file_id}/chunk/{chunk_number}:
post:
summary: Upload a file chunk
description: Upload a chunk of the file.
tags:
- Step 2
parameters:
- name: file_id
in: path
required: true
description: The file ID retrieved from the prepare upload step.
schema:
type: string
example: 00000000-0000-0000-0000-000000000000
- name: chunk_number
in: path
required: true
description: The number of the chunk being uploaded. The first chunk is 0.
schema:
type: integer
example: 0
requestBody:
required: true
content:
application/octet-stream:
schema:
type: string
format: binary
responses:
'201':
description: Chunk uploaded successfully
'400':
description: Bad request
operationId: postV7FileCmdsUploadByFileIdChunkByChunkNumber
x-operation-id-source: derived