How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

IntakeQ Intake Forms API

Intake questionnaires, consent forms, templates, and practitioners.

IntakeQ Intake Forms API is one of 6 APIs that IntakeQ publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Intake Forms. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 9 operations across 9 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, https://intakeq.com/api/v1.

9 operations 9 paths 2 schemas 6 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://intakeq.com/api/v1
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

IntakeQ Intake Forms API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-Auth-Key (authKey). By default, every request must be authenticated.

  • authKey — The account API key found under More Settings Integrations Developer API.

Paths & Operations 9

Across 9 paths, the API surfaces 9 operations — 6 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Intake Forms 9

Intake questionnaires, consent forms, templates, and practitioners.

GET
/intakes/summary
Query intake form summaries
queryIntakes 4 params → 200401
GET
/intakes/{intakeId}
Retrieve a complete intake form
getIntake 1 param → 200401
GET
/intakes/{intakeId}/pdf
Download an intake package as PDF
downloadIntakePdf 1 param → 200401
GET
/intakes/{intakeId}/consent/{consentFormId}/pdf
Download a single consent form as PDF
downloadConsentPdf 2 params → 200401
POST
/intakes/send
Send an intake questionnaire to a client
sendIntake body → 200401
POST
/intakes/resend
Resend a previously sent intake
resendIntake body → 200401
POST
/intakes
Update office-use-only answers on an intake
updateIntakeOfficeAnswers body → 200401
GET
/questionnaires
List questionnaire templates
listQuestionnaires → 200401
GET
/practitioners
List account practitioners
listPractitioners → 200401

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are IntakeSummary (6 properties), Practitioner (3 properties). Each schema is shown below with its type and property counts.

Practitioner
object
3 properties
IntakeSummary
object
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

intakeq-intake-forms-api-openapi.yml Raw ↑

Other APIs IntakeQ publishes across the network.

IntakeQ Appointments API
IntakeQ Clients API
IntakeQ Files API
IntakeQ Invoices API
IntakeQ Treatment Notes API
Where this information came from

This is an independent, third-party profile of IntakeQ Intake Forms API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.