Contents

Authenticated User

The Authenticated User is the user who granted your app access to their ShootProof account. Using the Authenticated User’s credentials, your app can manage their account and more through the ShootProof API.

Get the authenticated user

get
/studio/me

Example Request

Header Parameters

Property Description
Authentication required

The bearer token used to make authenticated requests to the ShootProof Studio API. See the authorization guide for more information on how to obtain and use bearer tokens.

200 OK

The authenticated user.

Response Body

When the Content-Type of the response is application/vnd.shootproof+json, the following properties will be available in the response body.

Properties
Property Description
created read-only

The date on which this user was created.

email

The email address for this user.

firstName

The first name for this user.

id

The identifier for this user.

isStudioOwner read-only

Whether the authenticated user is the owner of the studio.

lastLogin nullable read-only

The date on which this user last logged in to the Studio Panel.

lastName

The last name for this user.

links required read-only

Each property defines a hypertext link relationship as indicated by a link object or array of link objects. The target URL of each hypertext link relationship is related to the current resource according to the defined semantics of the link relationship property name.

name

The full name for this user.

permissions

An array of permission identifiers indicating the permission levels this user has within the Studio Panel.

Permission Description
account.payment-read The user may view the studio account's plan & billing information.
account.payment-withdrawal The user may request payment withdrawals on behalf of the studio.
account.read The user may view studio account settings (e.g. contact info, users, etc.).
account.update The user may update studio account settings (e.g. contact info, users, etc.).
brand-theme.create The user may create themes.
brand-theme.read The user may view themes.
brand-theme.update The user may edit themes.
brand.homepage-update The user may edit the client galleries homepage for a brand.
contact.create The user may create contacts.
contact.read The user may view contacts.
contact.update The user may edit contacts.
contract.create The user may create contracts.
contract.read The user may view contracts.
contract.update The user may edit contracts.
email-template.create The user may create email templates and automation groups.
email-template.read The user may view email templates and automation groups.
email-template.update The user may edit email templates and automation groups.
event-defaults.create The user may create default settings for events.
event-defaults.read The user may view default settings for events.
event-defaults.update The user may edit default settings for events.
event-photo.create The user may create event photos.
event-photo.update The user may edit event photos.
event.create The user may create events.
event.created-only The user may only view/edit/delete events they created.
event.delete The user may delete events.
event.read The user may view events.
event.update The user may edit events.
invoice.create The user may create invoices.
invoice.read The user may view invoices.
invoice.update The user may edit invoices.
mobile-app.create The user may create mobile apps.
mobile-app.read The user may view mobile apps.
mobile-app.update The user may edit mobile apps.
order.read The user may view orders.
order.update The user may edit orders.
playlist.read The user may view music playlists.
playlist.update The user may edit music playlists.
price-sheet.create The user may create price sheets.
price-sheet.read The user may view price sheets.
price-sheet.update The user may edit price sheets.
report.event-visitors-read The user may view the "Event Visitors" report.
report.invoices-read The user may view the "Invoices" report.
report.items-read The user may view the "Top-Selling Items" report.
report.orders-read The user may view the "Orders" report.
report.sales-read The user may view the "Sales" report.
tool.read The user may view the available downloadable tools (i.e. Desktop Uploader).
watermark.create The user may create watermarks.
watermark.read The user may view watermarks.
watermark.update The user may edit watermarks.
signature

A signature.

studio read-only

The studio to which the authenticated user belongs.

type

The type of object represented.

userStatus read-only

A human-readable string describing this user's status.

userStatusId

The numeric identifier for this user's status.

Error Response

API errors come in two kinds of varieties: 400s and 500s.

Any error with a status code of 400 to 499 is considered a client error. This means it’s usually an error you can handle in your app, and then resend a modified request to the ShootProof API to get a successful response.

An error in the range of 500 to 599, on the other hand, is a different story. These errors usually mean that a problem occured on the server and resending the request with modifications will not fix the issue.

Pay careful attention to the status codes. We try to stick as close as possible to their defined semantics. For a complete list of HTTP status codes, take a look at the official HTTP Status Code Registry.

Check out our errors guide for more information.

Response Body

When the Content-Type of the response is application/problem+json, the following properties will be available in the response body.

Properties
Property Description
detail

A longer description of of the error encountered.

info

Additional information that may be provided to aid in error resolution.

Property Description
reason

An optional reason for the error response.

In some cases, more information is required to convey information about the error to the client. In these cases, one of the following reason slugs may be used.

Reason Slug Description
contract-not-ready-to-countersign The contract is in a state that does not allow countersigning. Its status must be ready-to-countersign to perform this action.
event-photo-count-limit The event has reached the maximum number of photos allowed.
plan-does-not-allow-uploads The studio is in a plan that does not allow uploads or they have reached the limit of photos the plan allows.
status

The HTTP status code associated with this error.

title

A short description of the error encountered.

type

A namespace URI uniquely identifying the error type.

Validation Error Example
{
  "detail": "There was a problem with your request. Please see `info` for more information.",
  "info": {
    "errors": {
      "type": {
        "isEmpty": "Value is required and can't be empty"
      }
    }
  },
  "status": 400,
  "title": "Bad Request",
  "type": "https://developer.shootproof.com/errors#error-bad-request"
}
Forbidden Error Example
{
  "detail": "You do not have permission to access the requested resource.",
  "status": 403,
  "title": "Forbidden",
  "type": "https://developer.shootproof.com/errors#error-forbidden"
}
Not Found Error Example
{
  "detail": "The requested resource could not be found.",
  "status": 404,
  "title": "Not Found",
  "type": "https://developer.shootproof.com/errors#error-not-found"
}
Server Error Example
{
  "detail": "An error occurred on the server. If this error continues to occur, please contact support.",
  "status": 500,
  "title": "Internal Server Error",
  "type": "https://developer.shootproof.com/errors#error-server-error"
}
Unauthorized Error Example
{
  "detail": "No authorization credentials provided. You must provide an authorization token for this request.",
  "status": 401,
  "title": "Unauthorized",
  "type": "https://developer.shootproof.com/errors#error-unauthorized"
}

OpenAPI Schema

The following schema is based on OpenAPI 3.0 and is provided in our downloadable OpenAPI document.

{
  "200": {
    "content": {
      "application/vnd.shootproof+json": {
        "schema": {
          "$ref": "#/components/schemas/AuthenticatedUser"
        }
      }
    },
    "description": "The authenticated user."
  },
  "default": {
    "$ref": "#/components/responses/defaultError"
  }
}

Remove the authenticated user’s signature

If you need to remove a user’s signature, you may send a DELETE request to this resource to detach their signature.

Please note, this does not completely delete the signature if, for example, it has already been used to sign a contract, etc. Everything signed with the signature before it was removed will remained signed with that signature.

delete
/studio/me/signature

Example Request

Header Parameters

Property Description
Authentication required

The bearer token used to make authenticated requests to the ShootProof Studio API. See the authorization guide for more information on how to obtain and use bearer tokens.

200 OK

The authenticated user’s signature was successfully detached from the user.

Headers
Header Description
Content-Location

The URL to the resource represented in the body of the response.

Response Body

When the Content-Type of the response is application/vnd.shootproof+json, the following properties will be available in the response body.

Properties
Property Description
created read-only

The date on which this user was created.

email

The email address for this user.

firstName

The first name for this user.

id

The identifier for this user.

isStudioOwner read-only

Whether the authenticated user is the owner of the studio.

lastLogin nullable read-only

The date on which this user last logged in to the Studio Panel.

lastName

The last name for this user.

links required read-only

Each property defines a hypertext link relationship as indicated by a link object or array of link objects. The target URL of each hypertext link relationship is related to the current resource according to the defined semantics of the link relationship property name.

name

The full name for this user.

permissions

An array of permission identifiers indicating the permission levels this user has within the Studio Panel.

Permission Description
account.payment-read The user may view the studio account's plan & billing information.
account.payment-withdrawal The user may request payment withdrawals on behalf of the studio.
account.read The user may view studio account settings (e.g. contact info, users, etc.).
account.update The user may update studio account settings (e.g. contact info, users, etc.).
brand-theme.create The user may create themes.
brand-theme.read The user may view themes.
brand-theme.update The user may edit themes.
brand.homepage-update The user may edit the client galleries homepage for a brand.
contact.create The user may create contacts.
contact.read The user may view contacts.
contact.update The user may edit contacts.
contract.create The user may create contracts.
contract.read The user may view contracts.
contract.update The user may edit contracts.
email-template.create The user may create email templates and automation groups.
email-template.read The user may view email templates and automation groups.
email-template.update The user may edit email templates and automation groups.
event-defaults.create The user may create default settings for events.
event-defaults.read The user may view default settings for events.
event-defaults.update The user may edit default settings for events.
event-photo.create The user may create event photos.
event-photo.update The user may edit event photos.
event.create The user may create events.
event.created-only The user may only view/edit/delete events they created.
event.delete The user may delete events.
event.read The user may view events.
event.update The user may edit events.
invoice.create The user may create invoices.
invoice.read The user may view invoices.
invoice.update The user may edit invoices.
mobile-app.create The user may create mobile apps.
mobile-app.read The user may view mobile apps.
mobile-app.update The user may edit mobile apps.
order.read The user may view orders.
order.update The user may edit orders.
playlist.read The user may view music playlists.
playlist.update The user may edit music playlists.
price-sheet.create The user may create price sheets.
price-sheet.read The user may view price sheets.
price-sheet.update The user may edit price sheets.
report.event-visitors-read The user may view the "Event Visitors" report.
report.invoices-read The user may view the "Invoices" report.
report.items-read The user may view the "Top-Selling Items" report.
report.orders-read The user may view the "Orders" report.
report.sales-read The user may view the "Sales" report.
tool.read The user may view the available downloadable tools (i.e. Desktop Uploader).
watermark.create The user may create watermarks.
watermark.read The user may view watermarks.
watermark.update The user may edit watermarks.
signature

A signature.

studio read-only

The studio to which the authenticated user belongs.

type

The type of object represented.

userStatus read-only

A human-readable string describing this user's status.

userStatusId

The numeric identifier for this user's status.

OpenAPI Schema

The following schema is based on OpenAPI 3.0 and is provided in our downloadable OpenAPI document.

{
  "200": {
    "content": {
      "application/vnd.shootproof+json": {
        "schema": {
          "$ref": "#/components/schemas/AuthenticatedUser"
        }
      }
    },
    "description": "The authenticated user’s signature was successfully detached from the\nuser.",
    "headers": {
      "Content-Location": {
        "description": "The URL to the resource represented in the body of the response.",
        "schema": {
          "format": "uri",
          "type": "string"
        }
      }
    }
  }
}

Add a signature for the authenticated user

After creating a signature, you can attach that signature to the authenticated user using this resource with a PUT request.

put
/studio/me/signature

Example Request

Header Parameters

Property Description
Authentication required

The bearer token used to make authenticated requests to the ShootProof Studio API. See the authorization guide for more information on how to obtain and use bearer tokens.

Request Body

An object containing the signature ID for the signature you wish to attach to the authenticated user.

application/vnd.shootproof+json
Property Description
signatureId

The signature identifier.

OpenAPI Schema

The following schema is based on OpenAPI 3.0 and is provided in our downloadable OpenAPI document.

{
  "content": {
    "application/vnd.shootproof+json": {
      "schema": {
        "properties": {
          "signatureId": {
            "allOf": [
              {
                "$ref": "#/components/schemas/Id"
              },
              {
                "description": "The signature identifier."
              }
            ]
          }
        },
        "type": "object"
      }
    }
  },
  "description": "An object containing the signature ID for the signature you wish to\nattach to the authenticated user.",
  "required": true
}

200 OK

The signature was successfully attached to the authenticated user.

Headers
Header Description
Content-Location

The URL to the resource represented in the body of the response.

Response Body

When the Content-Type of the response is application/vnd.shootproof+json, the following properties will be available in the response body.

Properties
Property Description
created read-only

The date on which this user was created.

email

The email address for this user.

firstName

The first name for this user.

id

The identifier for this user.

isStudioOwner read-only

Whether the authenticated user is the owner of the studio.

lastLogin nullable read-only

The date on which this user last logged in to the Studio Panel.

lastName

The last name for this user.

links required read-only

Each property defines a hypertext link relationship as indicated by a link object or array of link objects. The target URL of each hypertext link relationship is related to the current resource according to the defined semantics of the link relationship property name.

name

The full name for this user.

permissions

An array of permission identifiers indicating the permission levels this user has within the Studio Panel.

Permission Description
account.payment-read The user may view the studio account's plan & billing information.
account.payment-withdrawal The user may request payment withdrawals on behalf of the studio.
account.read The user may view studio account settings (e.g. contact info, users, etc.).
account.update The user may update studio account settings (e.g. contact info, users, etc.).
brand-theme.create The user may create themes.
brand-theme.read The user may view themes.
brand-theme.update The user may edit themes.
brand.homepage-update The user may edit the client galleries homepage for a brand.
contact.create The user may create contacts.
contact.read The user may view contacts.
contact.update The user may edit contacts.
contract.create The user may create contracts.
contract.read The user may view contracts.
contract.update The user may edit contracts.
email-template.create The user may create email templates and automation groups.
email-template.read The user may view email templates and automation groups.
email-template.update The user may edit email templates and automation groups.
event-defaults.create The user may create default settings for events.
event-defaults.read The user may view default settings for events.
event-defaults.update The user may edit default settings for events.
event-photo.create The user may create event photos.
event-photo.update The user may edit event photos.
event.create The user may create events.
event.created-only The user may only view/edit/delete events they created.
event.delete The user may delete events.
event.read The user may view events.
event.update The user may edit events.
invoice.create The user may create invoices.
invoice.read The user may view invoices.
invoice.update The user may edit invoices.
mobile-app.create The user may create mobile apps.
mobile-app.read The user may view mobile apps.
mobile-app.update The user may edit mobile apps.
order.read The user may view orders.
order.update The user may edit orders.
playlist.read The user may view music playlists.
playlist.update The user may edit music playlists.
price-sheet.create The user may create price sheets.
price-sheet.read The user may view price sheets.
price-sheet.update The user may edit price sheets.
report.event-visitors-read The user may view the "Event Visitors" report.
report.invoices-read The user may view the "Invoices" report.
report.items-read The user may view the "Top-Selling Items" report.
report.orders-read The user may view the "Orders" report.
report.sales-read The user may view the "Sales" report.
tool.read The user may view the available downloadable tools (i.e. Desktop Uploader).
watermark.create The user may create watermarks.
watermark.read The user may view watermarks.
watermark.update The user may edit watermarks.
signature

A signature.

studio read-only

The studio to which the authenticated user belongs.

type

The type of object represented.

userStatus read-only

A human-readable string describing this user's status.

userStatusId

The numeric identifier for this user's status.

400 Bad Request

Validation error response. Check the info.errors property in the response for more details.

Response Body

When the Content-Type of the response is application/problem+json, the following properties will be available in the response body.

Properties
Property Description
detail

A longer description of of the error encountered.

info

Additional information that may be provided to aid in error resolution.

Property Description
errors

If the error response is a result of validation errors, it will most likely be a 400 Bad Request response and contain this info.errors property. Each property name in the errors object is a property that failed validation. These properties contain objects with property names in the form of internal validation error message slugs paired with human-readable string values describing the validation failure. Each property may have multiple validation failure messages.

reason

An optional reason for the error response.

In some cases, more information is required to convey information about the error to the client. In these cases, one of the following reason slugs may be used.

Reason Slug Description
contract-not-ready-to-countersign The contract is in a state that does not allow countersigning. Its status must be ready-to-countersign to perform this action.
event-photo-count-limit The event has reached the maximum number of photos allowed.
plan-does-not-allow-uploads The studio is in a plan that does not allow uploads or they have reached the limit of photos the plan allows.
status

The HTTP status code associated with this error.

title

A short description of the error encountered.

type

A namespace URI uniquely identifying the error type.

OpenAPI Schema

The following schema is based on OpenAPI 3.0 and is provided in our downloadable OpenAPI document.

{
  "200": {
    "content": {
      "application/vnd.shootproof+json": {
        "schema": {
          "$ref": "#/components/schemas/AuthenticatedUser"
        }
      }
    },
    "description": "The signature was successfully attached to the authenticated user.",
    "headers": {
      "Content-Location": {
        "description": "The URL to the resource represented in the body of the response.",
        "schema": {
          "format": "uri",
          "type": "string"
        }
      }
    }
  },
  "400": {
    "$ref": "#/components/responses/validationError"
  }
}

Create a signature

post
/studio/signature

Example Request

Header Parameters

Property Description
Authentication required

The bearer token used to make authenticated requests to the ShootProof Studio API. See the authorization guide for more information on how to obtain and use bearer tokens.

Request Body

The signature to create.

application/vnd.shootproof+json
Property Description
signaturePaths

The SVG paths that define this signature.

svgViewbox

The SVG viewbox that defines the dimensions of this signature.

type

The type of resource represented.

OpenAPI Schema

The following schema is based on OpenAPI 3.0 and is provided in our downloadable OpenAPI document.

{
  "content": {
    "application/vnd.shootproof+json": {
      "schema": {
        "$ref": "#/components/schemas/Signature"
      }
    }
  },
  "description": "The signature to create.",
  "required": true
}

201 Created

The newly-created signature.

Headers
Header Description
Location

The URL to the newly-created signature.

Response Body

When the Content-Type of the response is application/vnd.shootproof+json, the following properties will be available in the response body.

Properties
Property Description
created read-only

The date on which the entity was created.

id read-only

An entity identifier. It may be either an integer or a universally unique identifier (UUID) represented as a string.

links required read-only

Each property defines a hypertext link relationship as indicated by a link object or array of link objects. The target URL of each hypertext link relationship is related to the current resource according to the defined semantics of the link relationship property name.

publicId read-only

The public identifier for this signature (may be used in the portal website).

signaturePaths

The SVG paths that define this signature.

svgViewbox

The SVG viewbox that defines the dimensions of this signature.

type

The type of resource represented.

400 Bad Request

Validation error response. Check the info.errors property in the response for more details.

Response Body

When the Content-Type of the response is application/problem+json, the following properties will be available in the response body.

Properties
Property Description
detail

A longer description of of the error encountered.

info

Additional information that may be provided to aid in error resolution.

Property Description
errors

If the error response is a result of validation errors, it will most likely be a 400 Bad Request response and contain this info.errors property. Each property name in the errors object is a property that failed validation. These properties contain objects with property names in the form of internal validation error message slugs paired with human-readable string values describing the validation failure. Each property may have multiple validation failure messages.

reason

An optional reason for the error response.

In some cases, more information is required to convey information about the error to the client. In these cases, one of the following reason slugs may be used.

Reason Slug Description
contract-not-ready-to-countersign The contract is in a state that does not allow countersigning. Its status must be ready-to-countersign to perform this action.
event-photo-count-limit The event has reached the maximum number of photos allowed.
plan-does-not-allow-uploads The studio is in a plan that does not allow uploads or they have reached the limit of photos the plan allows.
status

The HTTP status code associated with this error.

title

A short description of the error encountered.

type

A namespace URI uniquely identifying the error type.

OpenAPI Schema

The following schema is based on OpenAPI 3.0 and is provided in our downloadable OpenAPI document.

{
  "201": {
    "content": {
      "application/vnd.shootproof+json": {
        "schema": {
          "$ref": "#/components/schemas/Signature"
        }
      }
    },
    "description": "The newly-created signature.",
    "headers": {
      "Location": {
        "description": "The URL to the newly-created signature.",
        "schema": {
          "format": "uri",
          "type": "string"
        }
      }
    }
  },
  "400": {
    "$ref": "#/components/responses/validationError"
  }
}

Get a signature

get
/studio/signature/{signatureId}

Example Request

Header Parameters

Property Description
Accept

Optionally, you may provide an Accept header with a value of image/svg+xml to be redirected to an SVG representation of the signature.

Authentication required

The bearer token used to make authenticated requests to the ShootProof Studio API. See the authorization guide for more information on how to obtain and use bearer tokens.

200 OK

The signature.

Response Body

When the Content-Type of the response is application/vnd.shootproof+json, the following properties will be available in the response body.

Properties
Property Description
created read-only

The date on which the entity was created.

id read-only

An entity identifier. It may be either an integer or a universally unique identifier (UUID) represented as a string.

links required read-only

Each property defines a hypertext link relationship as indicated by a link object or array of link objects. The target URL of each hypertext link relationship is related to the current resource according to the defined semantics of the link relationship property name.

publicId read-only

The public identifier for this signature (may be used in the portal website).

signaturePaths

The SVG paths that define this signature.

svgViewbox

The SVG viewbox that defines the dimensions of this signature.

type

The type of resource represented.

Alternate Response Body

When the Content-Type of the response is image/svg+xml, the following properties will be available in the response body.

Properties
A signature represented as an SVG image.
"<svg viewBox=\"0 0 430 150\" version=\"1.1\" xmlns=\"http://www.w3.org/2000/svg\">\n  <path stroke=\"black\" stroke-width=\"2\" fill=\"none\" shape-rendering=\"auto\" stroke-linejoin=\"round\" d=\"M125.5,66 L125.5,66 L126.5,66 L127.5,66 L127.5,66 L128.5,66 L129.5,66 L129.5,66 L129.5,66 L130.5,66 L130.5,66 L130.5,66 L131.5,66 L131.5,66 L132.5,65 L132.5,65 L132.5,65 L132.5,65\"></path>\n</svg>"

Error Response

API errors come in two kinds of varieties: 400s and 500s.

Any error with a status code of 400 to 499 is considered a client error. This means it’s usually an error you can handle in your app, and then resend a modified request to the ShootProof API to get a successful response.

An error in the range of 500 to 599, on the other hand, is a different story. These errors usually mean that a problem occured on the server and resending the request with modifications will not fix the issue.

Pay careful attention to the status codes. We try to stick as close as possible to their defined semantics. For a complete list of HTTP status codes, take a look at the official HTTP Status Code Registry.

Check out our errors guide for more information.

Response Body

When the Content-Type of the response is application/problem+json, the following properties will be available in the response body.

Properties
Property Description
detail

A longer description of of the error encountered.

info

Additional information that may be provided to aid in error resolution.

Property Description
reason

An optional reason for the error response.

In some cases, more information is required to convey information about the error to the client. In these cases, one of the following reason slugs may be used.

Reason Slug Description
contract-not-ready-to-countersign The contract is in a state that does not allow countersigning. Its status must be ready-to-countersign to perform this action.
event-photo-count-limit The event has reached the maximum number of photos allowed.
plan-does-not-allow-uploads The studio is in a plan that does not allow uploads or they have reached the limit of photos the plan allows.
status

The HTTP status code associated with this error.

title

A short description of the error encountered.

type

A namespace URI uniquely identifying the error type.

Validation Error Example
{
  "detail": "There was a problem with your request. Please see `info` for more information.",
  "info": {
    "errors": {
      "type": {
        "isEmpty": "Value is required and can't be empty"
      }
    }
  },
  "status": 400,
  "title": "Bad Request",
  "type": "https://developer.shootproof.com/errors#error-bad-request"
}
Forbidden Error Example
{
  "detail": "You do not have permission to access the requested resource.",
  "status": 403,
  "title": "Forbidden",
  "type": "https://developer.shootproof.com/errors#error-forbidden"
}
Not Found Error Example
{
  "detail": "The requested resource could not be found.",
  "status": 404,
  "title": "Not Found",
  "type": "https://developer.shootproof.com/errors#error-not-found"
}
Server Error Example
{
  "detail": "An error occurred on the server. If this error continues to occur, please contact support.",
  "status": 500,
  "title": "Internal Server Error",
  "type": "https://developer.shootproof.com/errors#error-server-error"
}
Unauthorized Error Example
{
  "detail": "No authorization credentials provided. You must provide an authorization token for this request.",
  "status": 401,
  "title": "Unauthorized",
  "type": "https://developer.shootproof.com/errors#error-unauthorized"
}

OpenAPI Schema

The following schema is based on OpenAPI 3.0 and is provided in our downloadable OpenAPI document.

{
  "200": {
    "content": {
      "application/vnd.shootproof+json": {
        "schema": {
          "$ref": "#/components/schemas/Signature"
        }
      },
      "image/svg+xml": {
        "examples": {
          "svg": {
            "summary": "A signature represented as an SVG image.",
            "value": "<svg viewBox=\"0 0 430 150\" version=\"1.1\" xmlns=\"http://www.w3.org/2000/svg\">\n  <path stroke=\"black\" stroke-width=\"2\" fill=\"none\" shape-rendering=\"auto\" stroke-linejoin=\"round\" d=\"M125.5,66 L125.5,66 L126.5,66 L127.5,66 L127.5,66 L128.5,66 L129.5,66 L129.5,66 L129.5,66 L130.5,66 L130.5,66 L130.5,66 L131.5,66 L131.5,66 L132.5,65 L132.5,65 L132.5,65 L132.5,65\"></path>\n</svg>"
          }
        },
        "schema": {
          "title": "A signature represented as an SVG image.",
          "type": "string"
        }
      }
    },
    "description": "The signature."
  },
  "default": {
    "$ref": "#/components/responses/defaultError"
  }
}