# Briefcase Update

Notifies the receiving party about the files in an application. Use this whenever you add or replace documents in an application. When you update, it sends the webhook to the receiving party. Once the receiving party gets the update, they must use /respond. If you're the sender, you get a confirmation the update was accepted.

Endpoint: POST /briefcase/update
Version: 1.5
Security: 

## Path parameters:

  - `version` (string, required)
    The version of the API.
    Enum: "1.0", "1.1", "1.2", "1.3", "1.4", "1.5"

## Request fields (multipart/form-data):

  - `appid` (integer)
    Insights-assigned application identifier. Required if you use this instead of appnumber.

  - `appnumber` (string)
    Customer-provided identifier for the application. Required if you use this instead of appid.
    Example: "ACME Widgets"

  - `key` (string)
    Share key.

## Response 400 fields (application/json):

  - `error` (string)
    Example: "No file found to process"

## Response 401 fields (application/json):

  - `error` (string)
    Example: "Bad token"

## Response 403 fields (application/json):

  - `error` (string)
    Example: "Briefcase feature disabled"

## Response 500 fields (application/json):

  - `error` (string)
    Example: "Encountered an unknown error. It has been reported. Please contact support@moneythumb.com for any questions."

  - `requestId` (string)
    Unique identifier for the request, useful for tracing.

## Response 503 fields (application/json):

  - `error` (string)
    Example: "Service unavailable"


## Response 200 fields