Changelog
2.0.0
Updated on Tue Mar 16, 2021.
New Features
- Nested
metadata
props are now possible without limit. See examples of nested props. - No depth limit for Object relationships. The only limit is the prevention of infinite recursion.
- We now offer a Postman collection to review and demo all REST API methods.
- You can now use the
after
param for Object pagination (experimental). - We now have endpoints for
Metafields
andMedia Folders
to do CRUD operations directly.
Improvements
- Lighter codebase, faster endpoints. In some cases, endpoint response times are up to 50% faster (non-cached).
- Better endpoint structures that follow standard REST conventions such as
POST /resources
,GET /resources/:resource_id
, etc. - Consistent error responses with verbose messages.
- The Select Dropdown Metafield now includes both
key
andvalue
in the API response.
Changes
_id
has been changed toid
.type_slug
has been changed totype
.status
can now either bepublished
orany
(which returns latest Object version draft or published).query
is now the primary method for fetching and filtering Objects (Advanced Queries from v1). See Queries and Logic for examples.- Single Objects must now be fetched using
id
. To fetch byslug
, you will need to usequery
. write_key
will now be required in the request header asAuthorization Bearer
.metafields
are hidden by default.- Stricter user input requirements. No additional fields are possible in the body for
POST
andPATCH
requests. - There is a new, more secure token authentication strategy.