- Previous: Central Index API
- Up: Central Index API
- Next: GET /v1/advertiser/updated
What data do we store in an entity?
An entity can have some or all of the following data points (we call them objects):
Object | Description |
name | The name of the entity |
invoice_address | The registered address of the entity |
postal_address | The mailing address of the entity |
phone |
The phone numbers of the entity |
status | Whether an entity is known to be active or inactive |
geopoint | Lat/long coordinates of the Postal address |
tag | Keywords that describe the entity's business activity |
category | categories of business activity |
fax | The fax number of the entity |
employee | any known employees of the entity (e.g. Marketing Director or CEO) |
website | Entity website URLs |
video | links to any videos from the entity |
entity emails | |
description | Descriptions of the entity |
payment_type | Payments accepted by the entity |
special_offer | Any special offers promoted by the entity |
testimonial | Testimonials about the entity |
opening_times | Entity opening times |
document | For example menus or other documents |
image | photos of the entity. We store four sizes of sides up to 1024px, up to 512px, up to 256px and up to 64px |
logo | logos of the entity We store three sizes of sides up to 300px, up to 200px, and up to 100px |
advertiser | If an entity is an advertiser |
socialmedia | Social media accounts of the entity |
If you want to know what attributes each object contains please use our documentation method via the IO Docs tool
NOTE: All our assets (image, documents etc) are held in http://assets.centralindex.com
- Previous: Central Index API
- Up: Central Index API
- Next: GET /v1/advertiser/updated
Docs Navigation
- Introduction
- Getting Started
- Using IODocs
- Responses
- Creating a sample request
- Sample Libraries
- Central Index API
- What data do we store in an entity?
- GET /v1/advertiser/updated
- GET /v1/autocomplete/category
- GET /v1/autocomplete/keyword
- GET /v1/autocomplete/location
- GET /v1/entity
- GET /v1/entity/advertisers
- GET /v1/entity/advertisers/inventorycheck
- GET /v1/entity/by_supplier_id
- GET /v1/entity/search/keyword/bynearest
- GET /v1/entity/search/what
- GET /v1/entity/search/what/bylocation
- GET /v1/entity/search/what/byboundingbox
- GET /v1/entity/search/what/bynearest
- GET /v1/entity/search/who
- GET /v1/entity/search/who/bylocation
- GET /v1/entity/search/who/byboundingbox
- GET /v1/entity/search/who/bynearest
- GET /v1/location
- GET /v1/location/context
- GET /v1/lookup/category
- GET /v1/match/byphone
- GET /v1/stats/entity/by_date
- GET /v1/syndication_log/by_entity_id
- GET /v1/token/add
- GET /v1/token/report
- GET /v1/token/claim
- GET /v1/token/message
- GET /v1/tools/docs
- GET /v1/user/by_email
- PUT /v1/business
- PUT /v1/business/json
- PUT /v1/entityserve
- POST /v1/entity/advertiser/cancel
- POST /v1/entity/advertiser/create
- POST /v1/entity/advertiser/renew
- POST /v1/entity/advertiser/upsell
- POST /v1/entity/category
- POST /v1/entity/claim
- POST /entity/claim/cancel
- POST /v1/entity/claim/reseller
- POST /v1/entity/description
- POST /v1/entity/document
- POST /v1/entity/email
- POST /v1/entity/fax
- POST /v1/entity/featured_message
- POST /v1/entity/geopoint
- POST /v1/entity/image
- POST /v1/entity/image/by_url
- POST /v1/entity/list
- POST /v1/entity/logo
- POST /v1/entity/logo/by_url
- POST /v1/entity/name
- POST /v1/entity/opening_times
- POST /v1/entity/payment_type
- POST /v1/entity/phone
- POST /v1/entity/postal_address
- POST /v1/entity/socialmedia
- POST /v1/entity/special_offer
- POST /v1/entity/tag
- POST /v1/entity/testimonial
- POST /v1/entity/video/youtube
- POST /v1/entity/website
- POST /v1/syndication/cancel
- POST /v1/syndication/create
- POST /v1/signal
- POST /v1/user
- DELETE /v1/entity/category
- DELETE /v1/entity/description
- DELETE /v1/entity/image
- DELETE /v1/entity/phone
- DELETE /v1/entity/logo
- DELETE /v1/entity/website
- syndication api