Create a visit request

post/v1/visit-requests

Creates a visit request and returns it. Send an Idempotency-Key header to make the request safe to retry. Available to keys belonging to office staff and caregivers. With a caregiver's or patient's key, a saved record that key cannot read back is answered with only object and id. Requires a key with write scope.

Authorization

Authorization: Bearer ak_...requiredscope: read + write

An AveeCare API key created in Settings → API Keys. This endpoint changes data, so the key needs read + write scope. About authentication

Headers

Idempotency-Key
stringmax length 255

A unique value (a UUID works well) that makes this request safe to retry for 24 hours. A retry with the same key and body returns the first result; the same key with a different body is refused with idempotency_conflict.

Request body

application/json
caregiverId
string | nullmax length 64

The caregiver asking for the visit. With a caregiver's API key this is always that caregiver (leave it out); office staff must send it.

patientId
string | nullmax length 64

The patient the caregiver would visit.

patientName
string | nullmax length 200

Patient's display name.

preferredStartDate
string · date | null

First date the caregiver could start.

preferredEndDate
string · date | null

Last date of the request.

preferredTimeOfDay
string | nullmax length 100

Time of day the caregiver prefers.

reason
string | nullmax length 20000

Why the caregiver is asking.

status
string | null

Where the request stands. A caregiver's key creates Pending requests and can only change its own pending request to Cancelled; approving and denying is for office staff.

One ofPendingApprovedDeniedCancellednull
adminResponse
string | nullmax length 20000

The office's reply. Set by office staff.

Response

201

The new visit request.

object
stringread-only

String representing the object's type. Always visit_request.

id
stringread-only

Unique identifier of the visit request.

caregiverId
string | nullmax length 64

The caregiver asking for the visit. With a caregiver's API key this is always that caregiver (leave it out); office staff must send it.

caregiverName
string | nullread-onlymax length 2000

Caregiver's display name, taken from the caregiver's record.

patientId
string | nullmax length 64

The patient the caregiver would visit.

patientName
string | nullmax length 200

Patient's display name.

preferredStartDate
string · date | null

First date the caregiver could start.

preferredEndDate
string · date | null

Last date of the request.

preferredTimeOfDay
string | nullmax length 100

Time of day the caregiver prefers.

reason
string | nullmax length 20000

Why the caregiver is asking.

status
string | null

Where the request stands. A caregiver's key creates Pending requests and can only change its own pending request to Cancelled; approving and denying is for office staff.

One ofPendingApprovedDeniedCancellednull
adminResponse
string | nullmax length 20000

The office's reply. Set by office staff.

respondedByName
string | nullread-onlymax length 2000

Who answered the request.

respondedAt
string · date-time | nullread-only

When the request was answered.

createdAt
string · date-time | nullread-only

When the visit request was created.

updatedAt
string · date-time | nullread-only

When the visit request was last changed.

Response headers

Request-IdstringUnique ID of this request. Quote it when contacting support.
RateLimit-LimitintegerRequests allowed in the current window.
RateLimit-RemainingintegerRequests left in the current window.
RateLimit-ResetintegerSeconds until the window resets.
Idempotent-ReplayedstringPresent and true when this response is the stored result of an earlier request with the same Idempotency-Key.

Errors

StatusCodeMeaning
400
n/a
The request was malformed, a value was invalid, or it contained an unknown field (invalid_request, unknown_field).
401
n/a
The API key is missing, malformed, expired or revoked (unauthorized).
403
n/a
The key is read-only (insufficient_scope), or its user's role cannot do this (forbidden).
409
n/a
The Idempotency-Key was already used with a different request, or that request is still running (idempotency_conflict).
429
n/a
Too many requests (rate_limited). Wait for Retry-After seconds.
500
n/a
Something went wrong on our side (internal_error). Retry, and quote the request ID if it persists.

Every error uses the same body. See Errors for the full list of codes.