Identities
Link external customer identities to orders, bookings, and gifts
To use this capability, add octo/identities to your Octo-Capabilities header.
octo/identities is currently an internal capability (internal: true) in the API source.
All paths below are public /octo routes.
Creates a new identity.
From capability octo/identities.
Key value.
loyalty_numberReturns an Identity object.
From capability octo/identities.
Unique identifier for this resource.
3d6f0a3a-59d4-4b16-a0c5-11d2d8a4e6b7Identity identifier.
identity_customer_001Key value.
loyalty_numberPOST /octo/identities HTTP/1.1
Host: api.ventrata.com
Content-Type: application/json
Accept: */*
Content-Length: 24
{
"key": "loyalty_number"
}Returns an Identity object.
{
"id": "3d6f0a3a-59d4-4b16-a0c5-11d2d8a4e6b7",
"identityId": "identity_customer_001",
"key": "loyalty_number"
}Updates an existing identity.
Identity ID.
identity_customer_001From capability octo/identities.
Key value.
loyalty_numberReturns an Identity object.
From capability octo/identities.
Unique identifier for this resource.
3d6f0a3a-59d4-4b16-a0c5-11d2d8a4e6b7Identity identifier.
identity_customer_001Key value.
loyalty_numberPATCH /octo/identities/{identityId} HTTP/1.1
Host: api.ventrata.com
Content-Type: application/json
Accept: */*
Content-Length: 24
{
"key": "loyalty_number"
}Returns an Identity object.
{
"id": "3d6f0a3a-59d4-4b16-a0c5-11d2d8a4e6b7",
"identityId": "identity_customer_001",
"key": "loyalty_number"
}Deletes an identity.
Identity ID.
identity_customer_001OK. No response body.
Whether success is enabled.
trueMessage value.
Deleted successfully.DELETE /octo/identities/{identityId} HTTP/1.1
Host: api.ventrata.com
Accept: */*
OK. No response body.
{
"success": true,
"message": "Deleted successfully."
}200 OK with empty body.
Attach Identity to Orders, Bookings, and Gifts
With this capability enabled, you can include identityId in any booking/order/gift payload handled by the create/update flows.
Order routes:
POST /ordersPATCH /orders/{orderId}PATCH /orders/{orderId}/previewPOST /orders/{orderId}/confirm
Booking routes:
POST /bookingsPATCH /bookings/{uuid}POST /bookings/{uuid}/confirm
Gift routes:
POST /giftsPATCH /gifts/{uuid}PATCH /gifts/{uuid}/previewPOST /gifts/{uuid}/confirm
Base schemas: Bookings, Multi-Booking Cart, and Gift Vouchers.
When creating or updating an order with nested bookings and gifts arrays, each nested item can also include its own identityId.
Check-in Lookup With Identity
When used with octo/checkin, check-in lookup can match bookings by identity.
This capability extends POST /checkin/lookup from Online Check-in with an identity filter.
Request Body Additions
If identityId is not provided, check-in lookup behavior falls back to the standard octo/checkin lookup inputs.
Schema Additions (JSON)
These are additive fragments showing only fields introduced by this capability.
Booking
BookingWriteRequest
Gift
GiftCreateRequest
Order
OrderCreateRequest
OrderUpdateRequest
Last updated