Discussion

Declared In

Sync

The Initial Sync request performs a complete sync of your app data.
It returns all the published entries and assets of the specified stack in response.
The response also contains a sync token, which you need to store,
since this token is used to get subsequent delta updates later.

Declared In

If the result of the initial sync (or subsequent sync) contains more than 100 records,
the response would be paginated. It provides pagination token in the response. However,
you do not have to use the pagination token manually to get the next batch,
the SDK does that automatically until the sync is complete.
Pagination token can be used in case you want to fetch only selected batches.
It is especially useful if the sync process is interrupted midway (due to network issues, etc.).
In such cases, this token can be used to restart the sync process from where it was interrupted.

Declared In

You can use the sync token (that you receive after initial sync) to get the updated content next time.
The sync token fetches only the content that was added after your last sync, and the details of the content that was deleted or updated.

Declared In

You can also initialize sync with entries of only specific content types.
To do this, use sync With ContentType and specify the content type UID as its value.
However, if you do this, the subsequent syncs will only include the entries of the specified content types.

Declared In

Use the type parameter to get a specific type of content. You can pass one of the following values: ‘ASSET_PUBLISHED’, ‘ENTRY_PUBLISHED’, ‘ASSET_UNPUBLISHED’, ‘ENTRY_UNPUBLISHED’, ‘ASSET_DELETED’, ‘ENTRY_DELETED’, ‘CONTENT_TYPE_DELETED’.

Declared In

You can also initialize sync with entries of only specific locales. To do this, use sync Locale and specify the locale code as its value. However, if you do this, the subsequent syncs will only include the entries of the specified locales.