About the Parking Spot Object

Parking spots belong to a specified team and can be associated with vehicles, delivery blocks, and waypoints. They can be used as the start or end location for a route.

For more details about how different parameter types such as datetime are formatted and used in Bringg, read our Data Formatting article.

Request Parameters

Parameter	Description	Validations & Notes
`address` _string	The address of the parking spot.	Required if `lat` and `lng` are `null`.
`external_id` _string	Your external system's ID for this entity.	Optional. This must be a unique ID. An error will be returned if a duplicate is found in Bringg when creating a new parking spot.
`lat` _double	The geographical latitude of this parking spot.	Required if `address` is `null`.
`lng` _double	The geographical longitude of this parking spot.	Required if `address` is `null`.
`name` _string	The entity name in Bringg. For example, this could be the name of a customer, location, parking spot, or inventory item.	Required.
`team_external_id` _string	Your external system's ID for the associated team.	Required if `team_id` is `null`.
`team_id` _int32	Bringg's ID for the associated team.	Required if `team_external_id` is `null`.

Response & Webhook Parameters

Below is a list of the data returned in webhooks and responses to your API requests. The inclusion of specific parameters may depend on your use case, your API request, and the webhook fields you have subscribed to.

Parameter	Description
`created_at` _datetime	The date and time this entity was created.
`id` _int32	Bringg's ID for this entity.
`updated_at` _datetime	The time and date when this entity was last updated.