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 | The address of the parking spot. | Required if |
external_id | 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 | The geographical latitude of this parking spot. | Required if |
lng | The geographical longitude of this parking spot. | Required if |
name | 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 | Your external system's ID for the associated team. | Required if |
team_id | Bringg's ID for the associated team. | Required if |
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 |
---|---|
success | Indicates whether the service completed successfully.
|
message | If an error occurred, a message indicating the error is included. |
rc | If an error occurred, the return code is included. |
address | The address of the parking spot. |
id | Bringg's ID for this parking spot. |
external_id | Your external system's ID for this parking spot. |
lat | The geographical latitude of this parking spot. |
lng | The geographical longitude of this parking spot. |
name | The parking spot display name in Bringg. |
team_external_id | Your external system's ID for the associated team. |
team_id | Bringg's ID for the associated team. |