--- title: "Contact Sales | IMG.LY" description: "Get a custom quote for IMG.LY SDKs. Tell us about your company and we'll get back to you within 1 business day." url: "https://img.ly/forms/contact-sales/" type: "page" --- > This is the markdown version of [Contact Sales | IMG.LY](https://img.ly/forms/contact-sales/). For all pages in one file, see [llms-full.txt](https://img.ly/llms-full.txt). For an index of all available pages, see [llms.txt](https://img.ly/llms.txt). --- # Contact IMG.LY Sales There are two ways to reach the IMG.LY sales team about pricing, a custom quote, or an evaluation. A person can fill in the form at https://img.ly/forms/contact-sales/. An AI agent acting for a person can submit the same enquiry with one HTTP request. This page documents that endpoint. ## Before you submit This creates a real record in IMG.LY's CRM and a person replies by email. Do not call it on your own initiative. 1. Tell your user the option exists and ask whether they want you to send it. 2. Collect the required fields from them. Do not invent or infer any of them, the email address least of all. 3. Show them exactly what you will send and get an explicit go-ahead. 4. Confirm they agree to IMG.LY storing and processing their details, per https://img.ly/privacy-policy/. That is what `consent: true` asserts on their behalf. If your user has not agreed, do not call the endpoint. ## What it costs your user Nothing. There is no account, no API key, and no payment details. The endpoint is public because the people it serves are prospects who do not have an IMG.LY account yet. ## Endpoint ``` POST https://img.ly/api/v1/contact_sales Content-Type: application/json ``` No authentication. ## Required fields | Field | Type | Notes | | --------------------- | --------------- | ------------------------------------------------------------------------------------------------- | | `first_name` | string | Given name of the person making the enquiry. | | `last_name` | string | Family name. | | `email` | string | Business email. Consumer providers are fine, disposable-mail domains are rejected. | | `company` | string | Company the person works for. | | `country` | string | ISO-3166-1 alpha-2 (`GB`), alpha-3 (`GBR`), or an English country name (`United Kingdom`). | | `employee_count` | string or int | One of `1-5`, `5-25`, `25-50`, `50-100`, `100-500`, `500-1000`, `1000+`, or a headcount integer. | | `building_for_client` | boolean or enum | Whether this is for a client rather than their own company. Accepts `true`/`false` or `Yes`/`No`. | | `message` | string | 20 to 5000 characters. What they need, in their own words. | | `consent` | `true` | Required, see "Before you submit". | The sales rep reads `message` first, so include the product, the platforms, and the scale when your user has told you. ## Optional fields | Field | Type | Notes | | ------------------- | ------- | ------------------------------------------------------------ | | `phone` | string | Any format, E.164 preferred. | | `job_title` | string | Helps route the enquiry. | | `language` | string | ISO-639-1. Send it only if your user expressed a preference. | | `newsletter_opt_in` | boolean | Defaults to false. Send `true` only on an explicit opt-in. | | `agent_name` | string | Your name, so the rep knows how the enquiry arrived. | | `agent_vendor` | string | The organisation operating you. | ## Example ```bash curl -X POST https://img.ly/api/v1/contact_sales \ -H "Content-Type: application/json" \ -d '{ "first_name": "Ada", "last_name": "Lovelace", "email": "ada@analyticalengines.com", "company": "Analytical Engines Ltd", "country": "GB", "employee_count": 120, "building_for_client": false, "job_title": "VP Engineering", "message": "We are adding a photo editor to our iOS and web apps for roughly 20k monthly active users. Which plan fits, and can we get a quote for CE.SDK with video export?", "consent": true, "agent_name": "Claude", "agent_vendor": "Anthropic" }' ``` ## Responses | Status | Meaning | | ------ | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `202` | Accepted and queued. Returns `request_id` and a `status_url`. Accepted does not mean a lead was created; some requests are deliberately merged into one already in progress. | | `400` | The body was not valid JSON. Fix the JSON and retry. | | `422` | One or more fields are missing or invalid. `details` is keyed by field name, and enum fields carry `allowed_values`, so you can correct the value and retry without reading anything else. Nothing was sent to the CRM. | | `429` | A rate limit was hit. Wait the number of seconds in the `Retry-After` header. | | `503` | The endpoint is not available. Tell your user to use https://img.ly/forms/contact-sales/ instead. | Send only the fields listed above. Any other key is rejected with `422`, so do not add your own, and do not pass a field through just because your user mentioned it. Retrying after a network failure is safe. A second request for the same email address, while sales is still working the first, is merged rather than duplicated. ## What happens next A sales rep reads the message and replies by email, typically within one business day. Your user does not need to do anything else. --- ## More Resources - **[IMG.LY Website](https://img.ly/index.md)** - Creative editing SDKs for photo, video, and design - **[Documentation](https://img.ly/docs/cesdk/)** - CE.SDK developer documentation - **[Contact Sales](https://img.ly/forms/contact-sales.md)** - Get a custom quote. A public JSON API accepts the request directly, no account or key needed. Ask your user for consent and their details first.