Bynder Step 4 OR Finalize and save an additional uploaded file as a new asset. API

The Step 4 OR Finalize and save an additional uploaded file as a new asset. API from Bynder — 1 operation(s) for step 4 or finalize and save an additional uploaded file as a new asset..

Operations 1

POST /api/v4/media/{id}/save/additional/{uploadId}/ Finalize additional file #

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/bynder-step-4-or-finalize-and-save-an-additional-uploaded-file-as-a-new-asset-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

bynder-step-4-or-finalize-and-save-an-additional-uploaded-file-as-a-new-asset-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Group Upload Assets API Steps Step 4 OR Finalize and save an additional uploaded file as a new asset. API
  contact: {}
  version: 1.0.0
servers:
- url: https://{your-bynder-domain}/
  variables:
    your-bynder-domain:
      default: your-bynder-domainDefaultValue
- url: https://your-bynder-domainDefaultValue
  variables: {}
- url: https://DefaultParameterValue
  variables: {}
- url: https://your-bynder-domainDefaultValue
  variables: {}
- url: https://your-bynder-domainDefaultValue/v6/authentication/oauth2
  variables: {}
- url: https://your-bynder-domainDefaultValue
  variables: {}
- url: https://{your-auth-url}
  variables:
    your-auth-url:
      default: DefaultParameterValue
- url: https://your-bynder-domainDefaultValue
  variables: {}
- url: https://DefaultParameterValue
  variables: {}
- url: https://your-bynder-domainDefaultValue
  variables: {}
- url: https://your-bynder-domainDefaultValue/v6/authentication/oauth2
  variables: {}
- url: https://your-bynder-domainDefaultValue
  variables: {}
- url: https://bynder-public-us-east-1.s3.amazonaws.com/
  variables: {}
security: []
tags:
- name: Step 4 OR Finalize and save an additional uploaded file as a new asset.
  description: ''
paths:
  /api/v4/media/{id}/save/additional/{uploadId}/:
    parameters: []
    post:
      tags:
      - Step 4 OR Finalize and save an additional uploaded file as a new asset.
      summary: Finalize additional file
      description: The endpoints described in Step 4 are an Either/Or choice. You should use either the `Finalise an uploaded file` endpoint to finalize and process a standard upload, or the `Finalize additional file` endpoint to finalize and save an additional uploaded file as a new asset.
      operationId: Finalize additional file
      parameters:
      - name: id
        in: path
        description: Asset id to which to save the new additional.
        required: true
        style: simple
        schema:
          type: string
          examples:
          - 00000000-0000-0000-0000-000000000000
      - name: uploadId
        in: path
        description: The upload id of the file.
        required: true
        style: simple
        schema:
          type: string
          examples:
          - 00000000-0000-0000-0000-000000000000
      requestBody:
        content:
          application/x-www-form-urlencoded:
            encoding: {}
            schema:
              type: object
              properties:
                targetId:
                  type: string
                  description: Target id as returned by the initialise call.
                  examples:
                  - final/00000000-0000-0000-0000-000000000000/Logo.png
                s3_filename:
                  type: string
                  description: Base location of the uploaded file.
                  examples:
                  - api_uploads/00000000-0000-0000-0000-000000000000/00000000-0000-0000-000000000000/Logo.png
                chunks:
                  type: number
                  description: Total number of chunks uploaded.
                  examples:
                  - 5
      responses:
        '201':
          description: Created
          headers: {}
          content:
            application/json:
              schema:
                examples:
                - mediaid: 00000000-0000-0000-0000000000000000
                  batchId: 00000000-0000-0000-0000000000000000
                  success: true
                  mediaitems:
                  - original: final/00000000-0000-0000-0000000000000000/image.jpg
                    destination: ___URL_TO_BYNDER_CDN___
                  - original: final/00000000-0000-0000-0000000000000000/thul-image.jpg
                    destination: ___URL_TO_BYNDER_CDN___
                  - original: final/00000000-0000-0000-0000000000000000/mini-image.jpg
                    destination: ___URL_TO_BYNDER_CDN___
                contentMediaType: application/json
              examples:
                success:
                  summary: Successful response
                  value:
                    mediaid: 00000000-0000-0000-0000000000000000
                    batchId: 00000000-0000-0000-0000000000000000
                    success: true
                    mediaitems: null
      deprecated: false
components:
  securitySchemes:
    permanentToken:
      type: apiKey
      name: Authorization
      in: header
    OAuth2:
      type: oauth2
      flows:
        clientCredentials:
          tokenUrl: https://your-bynder-domainDefaultValue/token
          scopes:
            MEDIAUPLOAD: ''
            MEDIAUPLOADFORAPPROVAL: ''
        authorizationCode:
          authorizationUrl: https://your-bynder-domainDefaultValue/
          tokenUrl: https://your-bynder-domainDefaultValue/token
          scopes:
            MEDIAUPLOAD: ''
            MEDIAUPLOADFORAPPROVAL: ''