Household

Household Registry

Manage and maintain household registries.

Create/Add a new household

post

Create a new household

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/v1/_create

Create/Add new households in bulk

post

Create a new household in bulk

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/v1/bulk/_create

Update the details of a existing household

post

Update the details of a existing household

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/v1/_update

Update the details of a existing household in bulk

post

Update the details of a existing household in bulk

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/v1/bulk/_update

Soft delete the details of a existing household

post

Soft delete the details of a existing household

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/v1/_delete

Soft delete the details of an existing households in bulk

post

Soft delete the details of an existing households in bulk

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/v1/bulk/_delete

Search existing household

post

Search existing household

Query parameters
limitinteger · max: 1000Required

Pagination - limit records in response

offsetintegerRequired

Pagination - offset from which records should be returned in response

tenantIdstring · varcharRequired

Unique id for a tenant.

lastChangedSinceinteger · int64Optional

epoch of the time since when the changes on the object should be picked up. Search results from this parameter should include both newly created objects since this time as well as any modified objects since this time. This criterion is included to help polling clients to get the changes in system since a last time they synchronized with the platform.

includeDeletedbooleanOptional

Used in search APIs to specify if (soft) deleted records should be included in search results.

Body
Responses
200

Ok

application/json
post
/household/v1/_search

Add a new household member

post

Add a new member to household

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/member/v1/_create

Add new household members in bulk

post

Add new members to household in bulk

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/member/v1/bulk/_create

Update the linkage details of an existing household member

post

Update the linkage details of an existing household member

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/member/v1/_update

Update the linkage details of an existing household members in bulk

post

Update the linkage details of an existing household members in bulk

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/member/v1/bulk/_update

Soft delete the linking of existing household member household

post

Soft delete the linking of an existing household member from a household

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/member/v1/_delete

Soft delete the linking of existing household members in bulk from a household

post

Soft delete the linking of an existing households in bulk from a household

Query parameters
echoResourcebooleanOptional

Client can specify if the resource in request body needs to be sent back in the response. This is being used to limit amount of data that needs to flow back from the server to the client in low bandwidth scenarios. Server will always send the server generated id for validated requests.

Body
Responses
post
/household/member/v1/bulk/_delete

Search existing household member

post

Search existing household member

Query parameters
limitinteger · max: 1000Required

Pagination - limit records in response

offsetintegerRequired

Pagination - offset from which records should be returned in response

tenantIdstring · varcharRequired

Unique id for a tenant.

lastChangedSinceinteger · int64Optional

epoch of the time since when the changes on the object should be picked up. Search results from this parameter should include both newly created objects since this time as well as any modified objects since this time. This criterion is included to help polling clients to get the changes in system since a last time they synchronized with the platform.

includeDeletedbooleanOptional

Used in search APIs to specify if (soft) deleted records should be included in search results.

Body
Responses
200

Ok

application/json
post
/household/member/v1/_search

Last updated

Was this helpful?