{
  "aid": "quantiv.io:main-1.0.0",
  "name": "Quantiv API",
  "type": "Index",
  "description": "Welcome to the Quantiv API documentation! \n\nThe Quantiv API empowers developers with seamless access to powerful data-driven solutions. Our suite of APIs enables you to efficiently interact with key resources, automate processes, and enhance your applications with reliable insights.\n\nWhether you're integrating property intelligence, optimizing lead quality assessments, or leveraging advanced data analytics, Quantiv provides the tools you need to drive smarter decisions and maximize efficiency.\n\nGet started today and unlock the full potential of our APIs!\n\n### 🧐 Overview\n  \nThe Quantiv API is organized around REST principles, utilizing standard HTTP methods, response codes, and authentication. It accepts requests with a JSON body and returns responses in JSON format. The API only supports HTTPS-secured communication. Standard HTTP status codes are used to indicate request outcomes. Error responses include `error`, `statusCode`, and `message` fields for clear debugging.\n### 🌐 Endpoint\n  The Quantiv API uses a single endpoint for both sandbox and production environments.\n   | Environment | Endpoint URL                            |\n   |-------------|-----------------------------------------|\n   | Sandbox    | [https://public-api.quantiv.io](https://public-api.quantiv.io) |\n   | Production | [https://public-api.quantiv.io](https://public-api.quantiv.io) |\n\n### 🔐 Authentication\n\nYou will be provided with two API keys. The key with the `sandbox` prefix should be used for requests to the sandbox environment, while the key with the `production` prefix should be used for requests to the production environment.  \n\nThe API key must be included in the `token` request header for each API request.\n\n### 📝 Response Status Codes\n  \nThe Quantiv API follows standard HTTP response codes to communicate the outcome of an API request. Generally, codes in the 200 range represent successful requests, codes in the 400 range indicate errors in the request, and codes in the 500 range denote server-side issues.\n\n  | Status Code | Status Message        | Description                                    |\n  |-------------|-----------------------|------------------------------------------------|\n  | 200         | Success               | The request was successfully processed.        |\n  | 400         | Bad Request           | The request was malformed or had invalid syntax. |\n  | 401         | Unauthorized          | The provided authentication credentials were invalid. |\n  | 404         | Not Found             | The requested resource could not be located.   |\n  | 500         | Internal Server Error | An error occurred on the server while processing the request. |\n\n### ⚠️ Business Errors\n\nThe Quantiv API returns a status code of **400 Bad Request** for business-related errors. The response will include the details of the error, as outlined in the table below.\n\n  | Case                              | Error        | StatusCode | Message                                                           |\n  |-----------------------------------|--------------|------------|-------------------------------------------------------------------|\n  | Incorrect Payment Status         | Bad Request  | 400        | Account is paused due to failed payment. Contact Quantiv Admin.   |\n  | Inactive API Product Triggered   | Bad Request  | 400        | Product is not activated. Contact Quantiv Admin.                  |\n  | Reaching API Usage Limit         | Bad Request  | 400        | API Monthly Limit is reached. Contact Quantiv Admin.              |\n  | Reaching $0 Account Balance      | Bad Request  | 400        | Insufficient Account Balance to process request. Contact Quantiv Admin. |\n",
  "url": "https://raw.githubusercontent.com/jentic/jentic-public-apis/refs/heads/main/apis/openapi/quantiv.io/main/1.0.0/apis.json",
  "tags": [
    "quantiv.io",
    "main"
  ],
  "created": "2026-04-02",
  "modified": "2026-04-02",
  "specificationVersion": "0.19",
  "access": "3rd-Party",
  "maintainers": [
    {
      "FN": "Jentic",
      "X-github": "jentic",
      "url": "https://github.com/jentic"
    }
  ],
  "apis": [
    {
      "aid": "quantiv.io:main-1.0.0",
      "name": "Quantiv API",
      "description": "Welcome to the Quantiv API documentation! \n\nThe Quantiv API empowers developers with seamless access to powerful data-driven solutions. Our suite of APIs enables you to efficiently interact with key resources, automate processes, and enhance your applications with reliable insights.\n\nWhether you're integrating property intelligence, optimizing lead quality assessments, or leveraging advanced data analytics, Quantiv provides the tools you need to drive smarter decisions and maximize efficiency.\n\nGet started today and unlock the full potential of our APIs!\n\n### 🧐 Overview\n  \nThe Quantiv API is organized around REST principles, utilizing standard HTTP methods, response codes, and authentication. It accepts requests with a JSON body and returns responses in JSON format. The API only supports HTTPS-secured communication. Standard HTTP status codes are used to indicate request outcomes. Error responses include `error`, `statusCode`, and `message` fields for clear debugging.\n### 🌐 Endpoint\n  The Quantiv API uses a single endpoint for both sandbox and production environments.\n   | Environment | Endpoint URL                            |\n   |-------------|-----------------------------------------|\n   | Sandbox    | [https://public-api.quantiv.io](https://public-api.quantiv.io) |\n   | Production | [https://public-api.quantiv.io](https://public-api.quantiv.io) |\n\n### 🔐 Authentication\n\nYou will be provided with two API keys. The key with the `sandbox` prefix should be used for requests to the sandbox environment, while the key with the `production` prefix should be used for requests to the production environment.  \n\nThe API key must be included in the `token` request header for each API request.\n\n### 📝 Response Status Codes\n  \nThe Quantiv API follows standard HTTP response codes to communicate the outcome of an API request. Generally, codes in the 200 range represent successful requests, codes in the 400 range indicate errors in the request, and codes in the 500 range denote server-side issues.\n\n  | Status Code | Status Message        | Description                                    |\n  |-------------|-----------------------|------------------------------------------------|\n  | 200         | Success               | The request was successfully processed.        |\n  | 400         | Bad Request           | The request was malformed or had invalid syntax. |\n  | 401         | Unauthorized          | The provided authentication credentials were invalid. |\n  | 404         | Not Found             | The requested resource could not be located.   |\n  | 500         | Internal Server Error | An error occurred on the server while processing the request. |\n\n### ⚠️ Business Errors\n\nThe Quantiv API returns a status code of **400 Bad Request** for business-related errors. The response will include the details of the error, as outlined in the table below.\n\n  | Case                              | Error        | StatusCode | Message                                                           |\n  |-----------------------------------|--------------|------------|-------------------------------------------------------------------|\n  | Incorrect Payment Status         | Bad Request  | 400        | Account is paused due to failed payment. Contact Quantiv Admin.   |\n  | Inactive API Product Triggered   | Bad Request  | 400        | Product is not activated. Contact Quantiv Admin.                  |\n  | Reaching API Usage Limit         | Bad Request  | 400        | API Monthly Limit is reached. Contact Quantiv Admin.              |\n  | Reaching $0 Account Balance      | Bad Request  | 400        | Insufficient Account Balance to process request. Contact Quantiv Admin. |\n",
      "image": "",
      "baseURL": "https://public-api.quantiv.io",
      "humanURL": "https://github.com/jentic/jentic-public-apis/tree/main/apis/openapi/quantiv.io/main/1.0.0",
      "version": "1.0.0",
      "tags": [
        "quantiv.io",
        "main"
      ],
      "properties": [
        {
          "type": "OpenAPI",
          "name": "OpenAPI definition",
          "url": "https://raw.githubusercontent.com/jentic/jentic-public-apis/refs/heads/main/apis/openapi/quantiv.io/main/1.0.0/openapi.json",
          "mediaType": "application/openapi+json"
        },
        {
          "type": "GitHubRepo",
          "url": "https://github.com/jentic/jentic-public-apis/tree/main/apis/openapi/quantiv.io/main/1.0.0"
        }
      ],
      "contact": [
        {
          "FN": "eugene@quantiv.io",
          "email": "eugene@quantiv.io"
        }
      ]
    }
  ]
}