Sales enquiry - Anona Memory

POST /v1/sales/enquiry is the endpoint behind the contact sales form. Enterprise has no self-serve path, so this is how an Enterprise conversation starts if you would rather not use the form or email support@anonalabs.com. It needs no authentication: the person asking usually does not have an account yet. It costs no credits.

Send an enquiry

POST /v1/sales/enquiry
Content-Type: application/json

{
  "name": "Ada Lovelace",
  "email": "ada@example.com",
  "company": "Example Corp",
  "message": "We need a committed annual pool for three teams.",
  "estimated_credits": "about 4M a month"
}

{ "status": "received" }

cURL

curl -X POST https://api.anonalabs.com/v1/sales/enquiry \
  -H "Content-Type: application/json" \
  -d '{"name": "Ada Lovelace", "email": "ada@example.com", "company": "Example Corp", "message": "We need a committed annual pool."}'

Field	Type	Notes
`name`	string	Required, 1 to 120 characters.
`email`	string	Required, a valid email address. This is where we reply.
`company`	string	Required, 1 to 160 characters.
`message`	string	Required, 1 to 4000 characters.
`estimated_credits`	string	Optional, up to 80 characters. A rough figure in your own words; “not sure yet” is a fine answer.

Any other field is rejected with 422, as is a field outside its length or an invalid email address.

Responses

Status	Meaning
`202`	The enquiry was recorded and handed to our sales team.
`422`	The body failed validation (see the table above).
`429`	`too_many_attempts`: more than 5 enquiries an hour from one IP address, or more than 3 an hour for one email address.

The response is 202, not 200: the enquiry is stored before anything is sent, and the email to our team is dispatched in the background, so the response cannot confirm delivery. Nothing is sent back to the address in the body; we reply from the sales inbox.