Body
-
Optional custom id that can later be used instead of normal id in
insert
,update
,delete
etc. endpoints -
Legacy field. Use
location
instead. If you don't providelocation
, thelocation
will default toaddress
. -
Most accurate location description of a location. Preferably exact address in the format common for the given country. If that isn't possible, provide us with the most accurate location description possible. (eg. '{street name}, {city}')
-
Accuracy of the provided location. If not provided upon insertion, will default to
exact
.- If accuracy is missing or is set to
exact
we will display the exact location that was provided. - If accuracy is set to other value we will try to find the closest entity of provided type, if we don't find it we will display the nearest non-exact entity we can find (eg. street)
Values are
exact
,street
,municipality_part
,municipality
,cadastral_area
,nearest_non_exact_geo_entity
, or.
- If accuracy is missing or is set to
POST
/advertising/v1.0/companies/
curl \
--request POST 'http://apis.reas.cz/advertising/v1.0/companies/' \
--header "Authorization: Bearer $ACCESS_TOKEN" \
--header "Content-Type: application/json" \
--data '{"thirdPartyId":"1000025","name":"string","email":"string","tags":["string"],"address":"string","websiteUrl":"string","phoneNumbers":["string"],"location":"Jablonecká 415/4, Praha 9","locationAccuracy":"exact","ico":"string","dic":"string"}'
Request examples
{
"thirdPartyId": "1000025",
"name": "string",
"email": "string",
"tags": [
"string"
],
"address": "string",
"websiteUrl": "string",
"phoneNumbers": [
"string"
],
"location": "Jablonecká 415/4, Praha 9",
"locationAccuracy": "exact",
"ico": "string",
"dic": "string"
}
Response examples (200)
{
"success": true,
"data": {
"id": "string",
"thirdPartyId": "1000025",
"name": "string",
"tags": [
"string"
],
"email": "string",
"websiteUrl": "string",
"phoneNumbers": [
"string"
],
"profileImageUrl": "string",
"ico": "string",
"dic": "string",
"location": "string",
"locationAccuracy": "exact"
}
}