Concepts
Expanding responses
Replace the id of a linked object with the object itself, and include the fields lists leave out.
A link to another object is its id. A registration names its event as "event": "EVT-…". With expand[], the API returns the whole object in its place, in the same request.
Expanding a field
Send expand[] with the name of the field. The object you get is the same as its own retrieve operation returns.
curl
JavaScript
Python
The fields you can expand are marked « expandable » in the reference: the event of a registration and of a call for papers, the call_for_papers and the event of a paper. Repeat the parameter to expand several fields.
In lists and searches
In a list or a search, prefix the field with data., because it applies to each object of data:
curl
JavaScript
Python
Each linked object is read once per page, however many objects of the page share it.
Rules
- One level. An expanded object is never expanded further.
- The scope of the expanded object. Expanding an event also needs
events_read. Without it, the request answers 403api_key_scope_missingonexpand. - A smaller page. A list or a search with any
expand[]takes alimitof at most 20. - A field that cannot be expanded answers 400
parameter_invalidonexpand.
Fields not included by default
Some fields cost one more read per object, so lists leave them out. An event’s languages and venue are always in GET/v1/events/{id}, but in GET/v1/events only when you ask for them:
curl
JavaScript
Python
The reference marks these fields « not included in lists by default ». Ask for them only when you show them: each one adds reads to every page.