curl --request POST \
--url https://app.pennylane.com/api/external/v2/quotes/{quote_id}/appendices \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: multipart/form-data' \
--form file=@example-file
{
"id": 123,
"url": "https://www.pennylane.com/rails/active_storage/blobs/redirect/eyJfc..==--26d6e7391dd728fae2cde59bd3fbe4dd11e20a95/Invoice42.pdf",
"filename": "<string>",
"created_at": "2023-08-30T10:08:08.146343Z",
"updated_at": "2023-08-30T10:08:08.146343Z"
}
Upload a file that will be an appendix attached to a quote.
Note that this will not upload a file into the DMS (GED).
ℹ️ This endpoint requires one of the following scopes:
quotes:all
curl --request POST \
--url https://app.pennylane.com/api/external/v2/quotes/{quote_id}/appendices \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: multipart/form-data' \
--form file=@example-file
{
"id": 123,
"url": "https://www.pennylane.com/rails/active_storage/blobs/redirect/eyJfc..==--26d6e7391dd728fae2cde59bd3fbe4dd11e20a95/Invoice42.pdf",
"filename": "<string>",
"created_at": "2023-08-30T10:08:08.146343Z",
"updated_at": "2023-08-30T10:08:08.146343Z"
}
The access token received from the authorization server in the OAuth 2.0 flow.
Returns the created appendix
The response is of type object
.
Was this page helpful?