Skip to main content
POST
/
v1
/
inbox
/
[token]
Create an RFP
curl --request POST \
  --url 'https://api.proposales.com/v1/inbox/[token]' \
  --header 'Authorization: Bearer <token>' \
  --header 'Content-Type: application/json' \
  --data '
{
  "email": "<string>",
  "company_name": "<string>",
  "first_name": "<string>",
  "last_name": "<string>",
  "phone_number": "<string>",
  "message": "<string>",
  "language": "<string>",
  "start_date": "<string>",
  "end_date": "<string>",
  "is_test": "<string>",
  "silent_confirmation": "<string>"
}
'
{
  "id": 123
}

Documentation Index

Fetch the complete documentation index at: https://docs.proposales.com/llms.txt

Use this file to discover all available pages before exploring further.

This is a public endpoint and does not require an API token. Data can be sent as application/json, application/x-www-form-urlencoded or multipart/form-data. The parameters listed below are treated specially, but arbitrary form data can be passed and will be associated with the proposal as metadata.

​
Body

​
email
string
required
A confirmation email will be sent to this address.
​
company_name
string
​
first_name
string
​
last_name
string
​
phone_number
string
​
message
string
Displayed in the request excerpt.
​
language
string
Determines the language of the confirmation email. Falls back to using the accept-language header of the request. In ISO 639 Set 1 format.
​
start_date
string
Start date of the event, in ISO 8601 format.
​
end_date
string
End date of the event, in ISO 8601 format.
​
is_test
string
If any data is passed via this parameter, the RFP is considered a test.
​
silent_confirmation
string
If any data is passed via this parameter, the confirmation email will not be sent to the user.

​
Response

​
id
number
The ID of the RFP.